AWS EC2 (VPS) Setup
Private RPC users prefer to run their software (bots or sniping tools) in a virtual server which has low latency to the RPC node.
Why Do I Need a VPS/VM/Server?
You need a fast internet connection and low ping to utilize your software which use private Solana RPCs. Most users do not have low pings to the RPC nodes and have slow internet connection so they prefer using servers in datacenters.
Why AWS?
AWS has one of the best network routing and they have a variety of server configurations which is what we want for optimal performance. Also pay to go option is quite good for beginners.
1. EC2 Setup
Name your server and select OS as given below. Also create a new administrator key as .pem
Scroll down and select an instance type.
Minimum 16 vCPU and 32GB ram with 1 GB bandwith is suggested. You may prefer c5a.4xlarge or c5a.8xlarge depending on your budget.
Change nothing in Network Settings and Configure Store and click "Launch Instance"
2. Run your VPS
Now your VPS is ready to run. Remote Desktop application is used to connect your VPS desktop. You will use Public IPv4 addresses to connect your remote desktop.
A new window will pop-up. Browse your .pem key file and decrypt the hash. Now you have your administrator password. You will need it when you login your EC2 instance.
3. Connect
Run Remote Desktop software and "add PC" not workspace. A pop-up will show up and enter your credentials: PC Name: Your Public IPv4 Address User Account: "Add user account" for first usage and faster connection.
Add and connect. Congratulations. You successfully deployed your AWS EC2 Instance aka AWS VPS.
4. Elastic IP Allocation
To have a static IP, go to Network & Security -> Elastic IPs -> Allocate Elastic IP
Change nothing and click "Allocate"
A new window will show up. Click actions and select:
Select your newly created instance and Associate.
Congratulations, now you have got your static IP. Your IP address will not be changed until you release the Elastic IP.
Last updated
