March 19, 2025. FOMC day. My EA was managing six GBPUSD positions on my home PC — trailing stops, breakeven logic, the works. At 6:40 PM, twenty minutes before the statement, my neighborhood lost power. PC dead. Router dead. I sat in the dark refreshing my broker's mobile app over cellular data, watching those six positions drift with no EA to manage them. Power came back 40 minutes later. The account was down $640 on an $8,000 balance — two positions had run straight through levels where the EA would have taken profit. The strategy didn't fail. My infrastructure did. The next morning I moved everything to the cloud, and this mt5 vps cloud setup aws google cloud guide is the exact playbook: which instance, which region, what it costs, and the mistakes that almost killed my EA twice after I "fixed" things.
Every position the cloud EA takes is still sized in the DarkWolf MT5 Signal Calculator first — the VPS keeps the EA alive, the calculator keeps it honest.
How I Run MT5 on AWS and Google Cloud
MT5 is a Windows program, so the job is simple: rent a small Windows server near your broker, install MT5, and never turn it off. On AWS that's an EC2 instance running Windows Server; on Google Cloud it's a Compute Engine VM with Windows. I started on AWS with a t3.small (2 vCPU, 2 GB RAM) in the London region — about $17/month on-demand — because my broker's servers sit in London and ping from that instance is 3ms.
Setup takes about an hour the first time. Launch the instance, connect with Remote Desktop, install Chrome (to download MT5), install your broker's MT5, log in, attach your EAs, enable AutoTrading, then lock down Windows: pause updates during market hours, disable sleep, set MT5 to start on login. I also install a lightweight uptime monitor that pings me on Telegram if the instance stops responding — $0 extra, fifteen minutes of setup, and it's caught two outages before my broker's app did.
Google Cloud's equivalent is an e2-small instance, similar price, and their europe-west2 (London) region gives the same 3–5ms ping to UK-based brokers. I keep a warm standby there — a stopped instance with MT5 pre-installed that I can boot in 90 seconds if AWS has a bad day. Belt and suspenders. The general VPS setup guide covers the specialist forex-VPS providers if you'd rather not touch cloud consoles at all.
$100,000 Account: VPS vs Home PC, One Month
I ran a controlled comparison in April 2025: the same EA, same inputs, on the $100,000 prop account — first two weeks from my home PC (as before), then two weeks from the London EC2 instance. The EA trades EURUSD and GBPUSD, roughly 40 trades a month.
| Metric | Home PC (2 weeks) | AWS London VPS (2 weeks) |
|---|---|---|
| Trades taken | 19 | 21 |
| Disconnects | 3 (one 6-hour overnight) | 0 |
| Avg ping to broker | 240 ms | 3 ms |
| Avg slippage | 1.9 pips | 0.4 pips |
| Net P/L | +$1,020 | +$2,310 |
The VPS fortnight took two more trades (the EA didn't miss signals during the 6-hour outage), slipped 1.5 pips less per trade, and netted $1,290 more. The VPS cost $8.50 for those two weeks. That is not a close decision.
Sizing the VPS-Run Trades in the Calculator
Moving to a VPS doesn't change the risk math — but it should change one input. With 3ms ping and no disconnects, my realized slippage dropped, so I stopped padding stops the way I did on the home PC.
| Input Field | What it means | Sample value |
|---|---|---|
| Account balance | Prop account equity | $100,000 |
| Risk percent | Per-trade risk | 0.5% |
| Stop loss (pips) | EA stop + VPS-era slippage only | 21 pips (20 + 1) |
| Take profit (pips) | EA target | 40 pips |
Output: 2.38 lots at $500 risk. On the home PC I used 24 pips in the stop field (20 + 4 padding); the VPS let me reclaim those 3 pips, which means slightly larger size for the same dollar risk. Small edges compound — that's the whole game.
Three VPS Mistakes That Nearly Killed My EA
Mistake one: Windows Update. Three weeks into the AWS setup, the instance rebooted at 2 AM for updates — mid-session, four positions open, no stops on two of them (EA-managed). I woke up to a $310 hole. Fix: set active hours to cover the full trading week, pause updates for 7 days at a time, and schedule a manual reboot every Sunday when markets are closed. Never let Windows choose the moment.
Mistake two: the wrong region. My first instance was in us-east-1 (Virginia) because it was the default — ping to my London broker was 95ms, barely better than home. I rebuilt in eu-west-2 (London): 3ms. Region is the single highest-leverage choice in this whole setup. Pick the cloud region closest to your broker's trade server, not closest to you. Your broker's server status page usually names the city.
Mistake three: a t2.micro to "save money." $8/month, 1 vCPU, burstable CPU credits. It ran fine for a week, then the credits ran out during a news spike and the instance throttled to 10% CPU — MT5 froze for 90 seconds while my EA held open gold positions. I "saved" $9 and risked the account. The t3.small's $17/month is the floor I'd recommend to anyone. The mobile monitoring setup is how I watch the instance from my phone now, so a throttled box can never surprise me again.
What Actually Runs on the Cloud Instance
A lot of traders overthink this. The instance runs exactly three things: Windows, one MT5 terminal, and your EAs. No browser tabs, no Discord, no YouTube — every background process is CPU you're renting. My t3.small idles at 8% CPU with MT5 and two EAs running; Chrome with three tabs pushes it to 40%.
| Option | Approx. cost | Setup effort | Best for |
|---|---|---|---|
| AWS EC2 (t3.small, London) | ~$17/month | ~1 hour first time | Full control, multi-terminal |
| Google Cloud (e2-small, London) | ~$16/month | ~1 hour first time | Standby/backup instance |
| Specialist forex VPS | $20–35/month | 15 minutes (MT5 pre-installed) | Zero cloud-console hassle |
I chose AWS as primary because I wanted snapshots — one-click full backups of the instance before any change. When an EA update goes wrong at midnight, I restore the snapshot instead of debugging. That feature alone has saved two trading sessions this year. See AWS EC2 and Google Cloud Compute Engine for current pricing — it shifts, so check before you commit.
The Uptime and Latency Math
Two formulas run my infrastructure decisions. Uptime tells me what I'm actually buying; the latency comparison tells me whether a provider change is worth the migration hassle.
| Variable | Meaning | Example value |
|---|---|---|
| Downtime hours | Hours terminal was unreachable/month | 0 (VPS) vs 9.5 (home PC) |
| Uptime % | 720-hour month basis | 100% vs 98.7% |
| Slip saved/trade | Home-PC slippage minus VPS slippage | 1.5 pips |
| Yearly slip savings | 480 trades × 1.5 pips × $10 | $7,200/year |
Read that last row again: $7,200 a year in slippage savings against ~$200 in VPS costs. The 98.7% vs 100% uptime gap looks small until you remember the 1.3% always strikes during the trades that matter most — news, breakouts, the exact moments your EA earns its keep. The one-click trading setup pairs well here: with the EA on a VPS, I use one-click on my local terminal purely for manual interventions.
Cloud VPS FAQs
AWS or Google Cloud — which is better for MT5?
Functionally identical for MT5: both give you a Windows VM you RDP into. I run primary on AWS (snapshots, habit) and standby on Google Cloud. Pick whichever console annoys you less, and put the instance in the region closest to your broker's server — that choice matters more than the provider.
What instance size do I actually need?
2 vCPU and 2 GB RAM is the floor — AWS t3.small or Google e2-small. One MT5 terminal with a few EAs idles under 10% CPU there. Don't go smaller: burstable micro instances throttle under news-spike load, exactly when you need the machine most.
Can I run MT5 on a Linux cloud instance?
Not natively — MT5 is Windows-only. Stick to a Windows Server instance. Wine workarounds exist but add failure modes to the one machine that must never fail. The $17/month for Windows licensing peace of mind is worth it.
How much does running MT5 in the cloud really cost?
About $16–20/month for the instance plus a few dollars for storage and data transfer — call it $25 all-in. Against one avoided outage or the slippage savings above, it pays for itself many times over. Reserved instances cut it further if you commit for a year.
Do I still need my home PC for trading?
Only as a window, not as infrastructure. I RDP into the VPS from my laptop for checks and use the DarkWolf MT5 Signal Calculator in a browser tab for sizing. The home PC can sleep, update, or die — the EA keeps trading either way. That separation is the entire point.