T3.medium Instance Freezing – (Stockholm )

Would suggest to take a look at the following area:

1. Memory Pressure or Resource Exhaustion o T3.medium has 4 GB RAM. If MetaTrader or other background services spike memory usage, the OS may become unresponsive. o Windows Server can be particularly sensitive to memory starvation, especially with GUI-based apps.
2. Disk I/O Bottlenecks o If your instance is using standard EBS volumes (gp2 or gp3), high IOPS demand (e.g., from logging or trading activity) might cause freezing.
3. Windows Services or Scheduled Tasks o Check for scheduled tasks (like Windows Updates or Defender scans) that might be kicking in and consuming resources.
4. RDP Session Hangs vs. Full OS Freeze o If only RDP is freezing but the instance is still running (e.g., you can ping it or access via EC2 Serial Console), it may be a session issue rather than a full crash.

Hey,

Hope you're keeping well.

Since the issue started suddenly, I’d start by checking CloudWatch metrics for CPU, memory (via the CloudWatch agent), and EBS volume I/O during the freeze periods to see if there’s a resource spike. On Windows, open EC2 Serial Console or enable EC2 Rescue to troubleshoot if the OS is hanging. If you see memory pressure or high disk latency, consider moving to a larger instance type (e.g., T3.large) or using gp3 volumes with higher IOPS. Also review Windows Event Viewer for any critical system or application errors around the time of the freeze. This will help pinpoint whether it’s an OS-level issue or an EC2 resource bottleneck.

Thanks and regards,
Taz