AWS Setup Guide

This guide will show how to setup an AWS Server.

Creating an AWS Account

1. Head to AWS.

2. Click Create an AWS Account

3. You will need to complete five pages to complete your registration. For Step 1, enter your email and password in. Your AWS account name will basically be your username, so feel free to put whatever you want for this

4. For step 2, select personal for how you plan to use AWS. Fill in your contact information. Make sure to use a real phone number as you will need it later for verification.

5. For step 3, fill in your card info. Make sure to use a valid card as they will authorize a test charge on it to see if it is a real card. This authorization will drop from your account.

6. For step 4, you will need to complete a verification challenge using your phone number

7. After entering the verification code, select the support plan you'd like to use. You can just select the basic support plan since it is free. Click complete sign up once finished.

8. If done correctly, you should see a congratulations message. Click Go to the AWS Management Console once done.

Creating an AWS Server Instance

Creating an AWS Server Instance

1. Head to the AWS Management Console. Click Sign In to the Console if you are already not logged in. Log into your AWS account using the credentials you used earlier

2. Once logged in, you will be brought to the AWS Management Console.

3. Ideally, you'll want to use a server that is located closely to your proxies. Since most proxies are located in Virginia, I will use Virginia in this guide as an example.

In the top right of the AWS Management Console, click where it says Ohio next to your username

4. Select US East (N. Virginia).

5. When done, you should see N. Virginia on the top right next to your username.

6. On the AWS Management Console, select Launch a virtual machine

7. For step 1, you will be shown a list of Amazon Machine Images (AMI). I personally like to use Microsoft Windows Server 2016 Base, however Microsoft Windows Server 2019 Base works as well

8. Select the Instance Type. Select Next: Configure Instance Details when done.

I personally like to use c5n.2xlarge for the instance type, which is 8 vCPU cores and 21 GB RAM, which is more than enough to run 1-2k tasks on bots with no issue. If you think you want higher specs, feel free to choose c5n.4xlarge or any other instance to suit your needs. Note that higher end servers will cost more hourly. c5n.2xlarge will cost 80 cents per hour when it is not a dedicated instance.

You can find a list of instance specs and their pricing through the links below.

Specs: https://aws.amazon.com/ec2/instance-types/

Pricing: https://aws.amazon.com/ec2/pricing/on-demand/

9. For Step 3, locate the field for Tenancy as shown below. From the dropdown menu, select Dedicated - Run a Dedicated instance

10. You can add storage in Step 4 if you want to, but I personally do not touch this setting. If you do not want to mess with this, click Review and Launch when done.

11. Review the configuration to make sure everything you specified is shown. Click Launch when done.

12. The following popup should appear afterwards. Click the dropdown where it says Choose an existing key pair

13. From this dropdown, select Create a new key pair

14. The Key pair type should be set to RSA by default. You can leave it on this setting. You will want to enter a file name under the Key pair name field. For this example, I will use AWS Guide, but you can enter any title you want to.

15. Once done, click Download Key Pair and save this file somewhere. This file will be used to generate your server password so do not lose it

Note: If you want to make additional servers afterwards, you can reuse the same .pem file you just generated by selecting the option to use an existing key pair. However you will still need access to this file so don't choose it if you no longer have access to it.

16. Once the file is downloaded, select Launch Instances.

17. If this is your first time registering for an AWS server, you will likely see a Launch Failed message as shown below.

This is perfectly normal. You will need to wait a few minutes before AWS successfully validates your new account and info. You will also receive an email as shown below once this validation has been completed.

Once verification is completed, click Retry Failed Tasks on the AWS page as needed and it should complete

18. Once your server is done, you will see the Launch Status page updated as shown below. Click View Instances in the bottom right.

19. You should be forwarded back to the AWS console management page as shown below.

20. Right click your server instance.

21. Select Connect.

22. On the connect to instance page that appears, click RDP Client.

23. Click Get Password.

24. Find the key pair .pem file you created earlier. Click browse to upload it.

25. Click Decrypt Password

26. Your password will display now as shown below.

27. Click Download remote desktop file.

28. Open the downloaded .rdp file.

29. The Remote Desktop Connection program will open up. Select Connect.

30. For your password, enter the password previously extracted in the AWS dashboard in step 26

31. Click Yes on the certificate pop up.

32. You will be logged onto your AWS server now. As a note, if you get an error stating that your server cannot be connected to, double check to see if the server is still initializing in AWS. You can see this on the dashboard under Status check. If it is initializing, then wait a few moments before it was done. When you see the status check change to 2/2 checks passed, then it usually means it's ready to go.

33. Within your AWS server, you'll first want to head to Server Manager. You can find this by going to Windows start menu and searching Server Manager or find it in the start menu already.

34. Select Local Server on the left side.

35. Select IE Enhanced Security Configuration.

36. Change both of these settings to off.

Your AWS server is now ready to go. Feel free to download Google Chrome and any of your bots afterwards.

Shutting Down and Terminating Server Instances

AWS servers do incur an hourly charge, so you will want to shut it down when you are done running for a drop. Do not leave your server running 24/7 or you will incur heavy charges.

You have the option to either shut down or terminate your server. Shutting down/stopping your server will stop the server from running, but will have your bots and all data stored on it still for the next time you want to use your server.

Terminating the server instance will result in the server being deleted entirely. You should do this if you want to set up your bots again later on and repeating all steps from this guide again.

Stopping an instance will stop hourly charges from being accumulated on your account. You will be charged a few cents a month to have a server stopped, but for the convenience this is my personal recommendation for not having to set up a server entirely every time you run it. Terminating the server instance will stop charges entirely.

Follow the steps below to stop a server instance.

1. There are two options to stop an instance. For the first option you can simply go to the windows start menu and proceed to shut it down how you would your own home computer.

2. To shut it down from the AWS console, simply go to the EC2 Dashboard and under your instances, select the instance by clicking on the checkbox to the left, and then click Instance state

3. Click Stop instance.

4. Click Stop and the instance should be stopped.

5. You will receive a successful message when done.

Note that the instance state should say stopped when fully completed. It will say Stopping as shown above until it is completed.

Terminating Server Instance

If you want to terminate the instance (fully delete the server), then you can only do this from the AWS EC2 dashboard.

1. On the EC2 dashboard, select the server instance you want to terminate and then click Instance state.

2. Select Terminate instance.

3. Click Terminate to finalize deletion.

4. You will see a successful message at the top.

5. It will take a few minutes to finalize server deletion. The server will show up on your dashboard for a few minutes after, but you will see a message on there indicating it has been terminated.

Setting Up An Elastic IP

When you turn an AWS server off, you are likely to receive a new IP address the next time you turn your server on. This can be a nuisance if you use proxies that are IP Auth instead of user:pass, or have to redownload the .rdp file every time.

You can use what’s known as an elastic IP, to have the IP of the server stay the same regardless of the server being turned off or not.

More information on elastic IPs can be found here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html

1. On the AWS console, click on Elastic IPs under Network & Security.

2. Select Allocate Elastic IP address

3. On the Allocate Elastic IP address, you can just leave everything default and just click Allocate at the bottom of the page.

4. If done successfully, you will see a successful allocation message.

5. Click the IP address field by ticking the checkbox on the left side. Then Click Actions on the top of the page.

6. Click Associate Elastic IP addresses.

7. On the next page that appears, click Instance.

8. Choose the instance you want to associate this elastic IP with.

9. Click Associate once done.

10. You will see the successful association message if done correctly.

You should also see it on the Instance page that an elastic IP is associated with it.

Deleting or Removing an Elastic IP

1. If you want to delete an elastic IP or move it to another server instance for any reason, simply go back to the Elastic IPs section in your dashboard.

2. Click the Elastic IP you want to modify and then click actions on the top.

3. Click disassociate to remove the elastic IP from that instance.

4. If you want to assign it to another instance, follow the steps again in adding an elastic IP to your server above. If you want to delete the IP, click the elastic IP address you want to delete and click actions again as done in step 2.

5. Click Release Elastic IP addresses.

6. Click Release to finalize deletion.

Notes:

Make sure you have an elastic IP address associated with an instance at all times. If you don't, you will incur additional charges.

Cloning an AWS Instance

Cloning an AWS instance can be helpful when you get the insufficient capacity message when trying to turn on your server. This can happen usually when servers are under heavy load (such as during a hyped shoe drop) or AWS is conducting maintenance on certain zones.

1. Head to your EC2 dashboard and find your instances.

2. Click the instance you want to clone by clicking the checkbox to the left.

3. Right click the instance and then click Image and templates, followed by Create image.

4. Simply fill in an image name and then click create image on the bottom right.

5. Click AMIs under Images.

6. You will see the AMI image you just created. Note that it can take up to 10-15 minutes for it to complete. There will be a spinning circle where the checkbox is located when it is still pending. The status message will also say pending as shown below.

7. Once it is completed, the status message will change to available. After it shows this, click the image by ticking the checkbox on. Then, click Launch in the top left.

8. Launch the server instance you want to use as you were before. The creation process is the same as when we first created the AWS server. Please follow the first portion of this guide to create the instance if needed.

As a note, the user credentials will be identical to the existing server you cloned, so you will need to use the same password to access the server. You will not be able to get the password from AWS directly, as you will be shown this error message only.

9. Head back to your EC2 dashboard under your instances. You should now see the server instance running. Once it is done initializing, connect to the server how you normally would.

10. Once connected, you should see what you had identically to the server you cloned.

AWS Pricing

AWS EC2 servers are based on hourly rates. You can find pricing for AWS EC2 servers here: https://aws.amazon.com/ec2/pricing/on-demand/.

Note that if you use a dedicated server option, it will increase the hourly rate of the server. You can find additional dedicated server rates below, which will vary depending on the server type you choose.

https://aws.amazon.com/ec2/dedicated-hosts/pricing/

AWS Credits

AWS Credits can be purchased on eBay by simply searching for AWS credits and buying at a price you like. You can check if a seller is legit by simply checking their reviews. Some will auto deliver the code to you after purchasing, while others may have to manually send the credit to you. Make sure to check the description of the listing to see how it will be delivered.

As a note, you don't need to have credits applied to your account prior to using AWS. All you need to do is have credits applied to your account before the end of the month. AWS will only charge you after the month ends, so you have plenty of time to apply credits.

Many people use AWS credits to cover the costs of using their servers. The advantage of using AWS credits to pay for AWS services used during a month is that credits can be purchased for cheaper value that will cover AWS billing costs. For example, if you purchase $100 AWS Credit for $50, then you can cover up to $100 in your monthly AWS bill with that credit.

AWS credits are a lot more expensive to obtain now however, since Amazon caught onto a lot of the abuse with credits that was happening and changed how EDU credits with their servers worked. You can purchase AWS credits from some providers still however, that can come in various prices, such as $50 for $100 AWS Credit.

To apply AWS credits to your account, first head to the Billing and Cost Management Console.

On the left side, click Credits.

Click Redeem credit on the top right.

Enter the code for the AWS credit you have into the promotion code field. Enter the security check captcha then click redeem credit on the bottom right once done.

You should now see the credit appear in your billing management console.

AWS Credits generally have what’s known as an event code. An event code can be something like EDU-ENG-FY2020-IC-Q2-4-AWSEDUCATE-PROMO-100USD. Each of these event codes will have a certain number of activations allowed before AWS will restrict you from adding more. For example, if you had three of the same event codes, but AWS only allows you to have two of that event code active at a time, then you will not be able to apply the third event code to your account until you use up at least one of that same event code. This will reset at the end of each billing period, which for AWS is the first day of each month generally.

Be careful not to stack too many AWS credits in one month. In some cases, Amazon can remove all of your active AWS credits if they think you are abusing credits.

Viewing Monthly Bill

To view your monthly bill, first go to the Billing and Cost Management Console.

You will see a brief overview of charges for the month based on your server usage.

If you want to dive deeper into specific charges, you can click Bills on the left side to see specific charges.

You can view charges on a monthly basis from here. For additional information, please reference this help guide from AWS: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/invoice.html.