Resolve Insufficient Capacity for Buenos Aires AWS Local Zone Servers

[sonikro]

Problem

We often receive 'Insufficient Capacity' errors when attempting to create t3.medium instances in the AWS Local Zone for Buenos Aires. This is critical for our South America coverage, as Buenos Aires offers optimal latency for users in Brazil and Chile.

• t3.medium is the only viable AWS instance type in this AZ
• No other instance types in that zone are suitable for our requirements
• Reserved capacity is not viable due to cost-efficiency needs

Importance

Buenos Aires is a strategic location for South American players. Ensuring reliable server creation is crucial for a consistent user experience. Frequent capacity errors degrade service reliability.

Proposed Solutions

1. Investigate workarounds with AWS to avoid Insufficient Capacity errors, without resorting to costly reserved capacity
2. Research other cloud providers with services in Buenos Aires as potential alternatives for migration

Acceptance Criteria

• Users are able to reliably create servers in Buenos Aires without capacity errors
• The solution remains cost-efficient
• If migrating to a new provider, verify latency and stability match or exceed AWS

Additional Context

We must solve this problem to prevent disruption of player experience in a key region.

• Investigate AWS capacity options
• Compare and research alternative cloud providers in Buenos Aires
• Validate latency and user experience