A Step-by-Step Beginner Guide to Launch, Secure, and Access Your Cloud Server
Running your trading applications on a cloud server provides better uptime, consistent connectivity, and improved execution reliability. This guide explains how to create and configure a Windows Trading Server on AWS, assign a static IP, and securely connect using Remote Desktop.
Step 1 — Log in to the AWS Console
- Sign up for an AWS account if you don’t have one
- Open the AWS Console: https://console.aws.amazon.com/
- From the top-right region selector, choose: Asia Pacific (Mumbai)
- From the top-left menu, navigate to: Services → Compute → EC2
Step 2 — Create a Firewall Rule (Security Group) for RDP
By default, AWS blocks inbound traffic. You must allow RDP (Remote Desktop Protocol) access so you can connect to your cloud server.
This step is required only once. If you already created an RDP security group, you can skip.
Create Security Group
- Go to:
EC2 → Network & Security → Security Groups - In the top-right corner, click Create security group and enter details as below
- Go to:
- Security Group Name: Allow RDP
- Description: Allow RDP
- Configure Inbound Rules
Type: RDP
Source: Anywhere-IPv4 - Leave Outbound Rules as default:
Type: All Traffic
Destination: Anywhere-IPv4 - Click Create Security Group
Step 3 — Launch a New Windows Server Instance
- Go to:
EC2 → Instances → Launch Instance - Configure the instance:
- Name: Choose a unique name (Example:
MyAlgo)
This helps identify your server if you create multiple instances. Application and OS Image:
Search for: Windows Trading Server 2022
From Community AMIs, select the AMI with: Owner ID: 032956577252- Instance Type: Select t3.small
- Key Pair: Choose Proceed without key pair
- Network Settings: Select Existing Security Group → Allow RDP
- Storage: Set 30 GB → gp3
Advanced Details
- Termination Protection: Enable
- Credit Specification: Select Standard (Important)
Leave all other settings as default.
Click Launch Instance
Step 4 — Allocate and Associate a Static IP (Elastic IP)
AWS static IP is called an Elastic IP.
You must allocate one IP per server.
Allocate Elastic IP
- Go to: EC2 → Network & Security → Elastic IPs → Allocate Elastic IP
- Select:
- Public IPv4 Pool: Amazon pool
- Network Border Group: ap-south-1
- Add Tag:
- Key: Name
- Value: Same server name (Example:
MyAlgo)
- Click Allocate
Associate Elastic IP with Instance
- Select the newly created Elastic IP
- Click Actions → Associate Elastic IP
- Resource Type: Instance
- Instance: Select your server
- Click Associate
Verify Association
Go to: EC2 → Instances → Select your Instance
Check:
- Public IP
- Elastic IP
Both should show the same address.
Step 5 — Connect to the Server Using Remote Desktop (RDP)
- On your computer, open Remote Desktop
You can:
- Search for Remote Desktop
- Or press Win + R and type:
mstsc.exe
- Enter the Elastic IP address in the Computer field.
- Click Connect
- When prompted:
- Tick Don’t ask me again
- Enter
UserName : Administrator
Password : #admin@2022# - Tick Remember me
- Click OK
- If security prompt appears:
- Tick Don’t ask again
- Click Yes
After Login
If Windows asks: “Do you want to allow your PC to be discoverable?”
Click No
Important — Change the Default Password
- Open Control Panel
- Navigate to: User Accounts → User Accounts → Manage Another Account
- Select the account → Click Change Password
- Enter:
- Current Password
- New Password (Minimum 8 characters, Latin letters)
- Confirm Password
- Click Change Password
⚠️ Important:
If you forget the password, you will not be able to access the server.
Now exit the RDP session using the ExitRDP icon pinned to the taskbar.
Reconnect again using the new password to verify.
Step 6 — Install Trading Software
Your cloud server is now ready.
You can:
- Install your Trading API software
- Configure automation
- Set up required trading tools
Cost Awareness
You can check the estimated monthly cost of running a t3.small instance for 175 hours/month from the AWS pricing page.
⚠️ Warning
Running a server 24×7 can result in a high bill.
Recommended Practice
- Power ON: Around 8:00 AM (working days) (From AWS Console)
- Shutdown: Around 4:00 PM without fail
After powering on:
- Connect using Remote Desktop
- Run your trading applications
Very Important Usage Notes
Properly Exit RDP Session
Always exit using:
ExitRDP.exe (Pinned on Taskbar)
Do NOT:
- Click X on the RDP window
- Allow session disconnect due to internet failure
Otherwise:
- User session becomes Disconnected
- Your trading applications may stop running
Security Considerations
- Server is optimized for API trading
- Windows Defender may be disabled by default
- Do NOT store sensitive data
- Avoid downloading untrusted software
Troubleshooting RDP Connection Issues
If you cannot connect:
- Check your internet connection
- Verify the server is powered ON in AWS Console
- Ensure RDP port (3389) is allowed in Security Group
- Confirm:
- Correct Public / Elastic IP
- Correct Username
- Correct Password