That is the way we attack!if you are a cyber security enthusiast just try it and enjoy!!Creating Unlimited Rotating IP Addresses with AWS....

Create the Control-Server
The control-server is a OpenVPN server that your workstation will connect to. This server always remains up. Exit-nodes are systems connected to the control-server that provides load balancing and multiple source IP addresses. Exit-nodes can scale up and down to suite your needs.
AWS (setup the control-server)
#1 — Create a separate SSH key pair
1. In the AWS console, go to
services (upper left)
2. Select EC2 under the Compute section.
3. Select Key Pairs in the nav on the left.
4. Select Create Key Pair and name it ‘ proxycannon ’.
5. Download and save the key to ~/.ssh/proxycannon.pem
#2 — Launch the control-server instance
1. Launch (1) Ubuntu Server t1-micro instance and use the
proxycannon keypair.
Recommend public AMI
ami-0f65671a86f061fcd
It is only available in us-east-2 but any Ubuntu Server 18.04 AMI should work.
2. Login to the control-server via ssh
3. Download and install (come and i give it to you)
$ cd proxycannon-ng/setup
$ chmod +x ./install.sh
$ sudo ./install.sh
#3 — Create a new IAM user, set the needed permissions, and copy over your keys. It’s quick:
1. In the AWS console, go to
services (upper left)
2. Select IAM under the Security, Identity & Compliance section
3. In IAM, select Users in the nav on the left.
4. Select Add user
5. Fill out a User name, and for access type, select programmatic access. Click
Next.
6. Select the tab/box that’s labeled Attach existing policies directly. Add the following policy: AmazonEC2FullAccess. Click
Next, than Create user
7. Copy the access key and secret for the control-server and paste it in ~/.aws/credentials
[default]
aws_access_key_id = REPLACE_WITH_YOUR_OWN
aws_secret_access_key = REPLACE_WITH_YOUR_OWN
region = us-east-2
#4 — Setup terraform
Perform the following on the control-server:
1. Copy your proxycannon.pem SSH key into ~/.ssh/proxycannon.pem
2. cd into proxycannon-ng/nodes/aws and edit the
variables.tf file updating it with the subnet_id . This is the same subnet_id that your control server is using. You can get this value from the AWS console when viewing the details of the control-server instance. Defining this subnet_id makes sure all launched exit-nodes are in the same subnet as your control server.
3. Run terraform init to download the AWS modules. (you only need to do this once)
#5 — Copy OpenVPN files to your workstation
Copy the following files from the control-server to the /etc/openvpn directory on your workstation:
~/proxycannon-client.conf
/etc/openvpn/easy-rsa/keys/ta.key
/etc/openvpn/easy-rsa/keys/ca.crt
/etc/openvpn/easy-rsa/keys/client01.crt
/etc/openvpn/easy-rsa/keys/client01.key
You can also run this script below to compress everything you need to ~/copy_me.tar.gz and then you can download that and extract to /etc/openvpn on your workstation.
Optional script to compress everything you need in to ~/copy_me.tar.gz
# Copy necessary files and compress to ~/copy_me.tar.gz
$ mkdir ~/copy_me
$ sudo cp ~/proxycannon-client.conf ~/copy_me
$ sudo cp /etc/openvpn/easy-rsa/keys/ta.key ~/copy_me
$ sudo cp /etc/openvpn/easy-rsa/keys/ca.crt ~/copy_me
$ sudo cp /etc/openvpn/easy-rsa/keys/client01.crt ~/copy_me
$ sudo cp /etc/openvpn/easy-rsa/keys/client01.key ~/copy_me
$ tar czfv ~/copy_me.tar.gz ~/copy_me
After you copied and extracted the files to /etc/openvpn on your workstation test OpenVPN connectivity from your workstation by running:
$ openvpn --config proxycannon-client.conf
Setup Completed!
From now on you’ll only need to connect to the VPN to use
proxycannon-ng .
The next section details how to add and remove exit-nodes (source IPs):
Managing exit-nodes
Scaling of exit-nodes is controlled on the control-server using terraform.
Scale up exit-nodes
To create AWS exit-nodes, do the following:
1. cd into proxycannon-ng/nodes/aws
2. Edit the count value in
variables.tf to the number of exit-nodes (source IPs) you’d like
3. run terraform apply to launch the instances.
Scale down exit-nodes
If you want to stop all exit-nodes run terraform destroy .
OR
Scaling down exit-nodes can be done by reducing the count value in variables.tf and running
terraform apply again. Terraform will automatically remove X number of exit-node instances.