Since these are the rules set by amazon and there are a few technical aspects on how to use their dashboard and features that may confuse you, hell they confused me at first and I’m a developer, this is some best practices on how you can utilize this feature and also keep costs down. First I’ll explain the costs of the IP’s. Something that while looking it over on amazon can get a bit confusing because every aspect of their cloud uses different features.
To run a vps as a BrowSEO-able proxy you need a couple of things:
This is your set of keys needed you use aws api. It contains 2 keys an access key and a secret key you need both to use the aws feature it is highly recommended not to create the default ones allocated by amazon and to use newly created one. They are free so you don’t have to worry about the payments for each one. Also this will enable you to have your own set of read and wright keys and also a set of read only keys for your outsourcer so you can give them access to the panel with their own set of keys and also be able to monitor their usage and shut them down whenever you want without it affecting your usage. Also not using your default set and using a IAM role is the safest way to use the aws features.
Security groups are a set of inbound and outbound traffic rules allowed through your vps it is a type of firewall set by aws. so a security group will contain an IP with a port. Without a security group you cannot create a vps. You can have as many security groups as you want and but you can only attach 5 groups to a single vps. Port 80 is used for http/https access and 22 is for ssh access this is used for installing the proxy server application. When creating a vps if you already have a group with these two ports open for your computers IP in the region you are creating the vps select this rule there is no need to create a new one. When you want to add access for other users like you outsources or your team to be able to access these IP’s create a new security group for them and add there IP to the vps either with the edit groups button on the right of the vps you want to grant them access to or through the edit all groups option on the top navigation. Doing this will allow you to easily remove their access or change their access with their own separate group instead of having to edit your own every time and when there done just delete that group and you don’t have to be worried about your IP getting hijacked. You will also be able to keep things neat like this knowing what crew is using what vps. you can edit the name for a group once it is created as well with the edit groups option.
Price for groups are free that’s great so no worry’s there.
VPS instance types. Not much needed for explanation there pretty sure your all familiar with what that is and with aws it’s the same.
Costs will vary so I will post here the different regions and there cost per hour. Also keep in mind that once an hour has started you will pay for the hour whether you used 1 minute or 30.
if you are free tier eligible you will get 750 hours of free vps usage for the micro vps. This 750 hour spans across all regions and all instances this is not per instance or per region you get 750 hours. If you are not free tier eligible or your over your 750 hours, the costs are as follows
If you want to check if anything else has changed since I wrote this you can check here https://aws.amazon.com/ec2/pricing/
This is the password to get into the server via ssh stored in an encrypted file, There also free so it’s all good.
Each vps requires a minimum of an 8gig block of Elastic Block Storage otherwise known as in the aws world EBS.
The storage is used to store the proxy app, and to store the ubuntu os. This storage type is standard which indicates that it is magnetic storage in all regions other than Sou Paulo the price ranges from 0.028-0.03 per gig per month. in Sau Paulo it is 0.048 per gig per month.
for more info on this or to double check you can view this at https://aws.amazon.com/ebs/pricing/
An Elastic ip is amazon’s way of saying a static ip. Once you allocate yourself an elastic IP this IP belongs to you and will never change until you delete it and create a new one. You are allowed up to 5 Elastic IP’s per region. Once you create one you can attach it to any running VPS in the same region that doesn’t already have an elastic ip attached to it. If you delete a vps this will not delete your elastic ip. Elastic ip will only be deleted once you specifically delete it. Elastic ips are free to use as long as they are attached to a vps and that vps is running. If the vps is stopped or if it is just on reserve, you pay $0.005 per Elastic IP per hour.
The admin panel has a specific usage flow Simon already showed you guys how to use on YouTube.
When you create a new vps what you are doing is using your IAM keys to access the aws api for your account. Attaching a security group to it for its firewall access. and allocating 8gig of EBS to be able to store the proxy scripts, app and the ubuntu OS. We also create a new pem file and allocated to the instance if there is no pem file available locally for the selected region. In the background what is going on is the admin panel asks the aws api to create the selected amount of vps’s selected in the selected regions with the firewall rules of the security groups selected. We then wait for the first server to fully boot (which takes longer then starting it from the panel once everything is all set up). Then we ssh into your server with the pem file as the password. Run some terminal commands to install the necessary files and reboot the instance. Once this is done successful you are free to use the vps as a BrowSEO-able proxy as long as its running. If anything goes wrong during installation you can select the vps and reinstall the proxy scripts if that doesn’t help delete it and create a new one. Once this process is finished you are free to stop and start the instance and the scripts will already be available and accessible within seconds from the admin panel.
Once you stop a vps unless an elastic ip is attached to that vps the ip will be released once you restart the vps a new ip will be allocated to it.
You can allocate up to 5 security groups to an instance. Each security group can hold as many ips as you would like to add to it. You can edit this from the edit groups option on the left of the vps or from edit all groups at the top navigation in the panel window.
You can create up to 5 elastic ips per region and associate it with an vps in the same region once you do this that vps will run with that ip until you either delete the ip or delete the vps.
Now that you understand the cost per instance. What aws features are needed to run instances here is the best way to use them to make your life easier and keep the aws costs down.
This is the first thing I want to talk about as it is the most confusing but very important to use the service optimally. Each security group defines the access a user has to use that vps as a proxy. As the admin of the panel you only need 1 group in each region easily created by ticking the new permission option and adding your ip there. This will give you access as the admin to ports 80 and 22. 22 is the port you need for the ssh tunneling automation that is run when you create a vps and 80 for http/https when browsing the web. When you want to add access after a vps is created you can do this with the edit groups settings.
When creating a new instance, you need to ask yourself if you need a new one or if just restarting one you already have is enough. Since you are paying per storage even if it’s only penny’s. Restarting and stopping an instance instead of creating and terminating already created on.