Skip to content

Unable to launch baseline Lightsail instance in ap-northeast-1 (Quota set to 0 vCPUs on new account)

0

Hello AWS Community and Support Engineers,

I am seeking guidance on how to allocate a baseline compute quota (2 vCPUs) for Amazon Lightsail in Asia Pacific (Tokyo - ap-northeast-1) for a new account.

Current Situation

  • My account quota for Lightsail instances in ap-northeast-1 is currently set to 0 vCPUs.
  • I submitted a minimal quota increase request for 2 vCPUs to run a single entry-level instance.
  • Support/Service Quota review indicated that the account must first demonstrate ~90% utilization on existing limits in primary US regions (us-east-1) before non-US capacity can be granted.

Why US Regions Cannot Be Used (Hard Constraints)

  1. Geographic IP Restrictions: The public market-data and WebSocket API endpoints consumed by my application actively block US IP addresses (returning HTTP 403 / 451 location-restricted errors).
  2. Latency Sensitivity: The ingestion pipeline requires sub-5ms network proximity in the Tokyo region. Operating cross-region from us-east-1 introduces a ~180ms latency penalty, resulting in persistent connection drops and stream timeouts.

Because the workload physically cannot connect from US infrastructure, I am unable to generate utilization history in US regions.

Steps Taken

  • Opened a Service Quota request for 2 vCPUs in ap-northeast-1.
  • Reopened support correspondence explaining the latency and endpoint restriction constraints.
  • Account has a verified payment method, active promotional credits, and billing alerts configured.

Is there a standard process for new accounts with region-specific architectural requirements to request baseline 2 vCPU allocation in Tokyo (ap-northeast-1), or can an AWS representative help review this case? Reference Support Case ID: [***************]

Thank you for your time and assistance.

Edit: Removed case ID — Sage A.

2 Answers
0

For new AWS accounts, initial service quotas in certain regions may be set conservatively, and quota increases typically require demonstrating usage patterns in your account. However, I understand you have legitimate technical requirements that necessitate operating specifically in the Asia Pacific (Tokyo) region.

When you encounter capacity or quota limitations for Lightsail instances, here are some approaches to consider:

Immediate Technical Options:

  1. If you haven't already, try selecting different Availability Zones within the ap-northeast-1 region when creating your instance, as each AZ maintains different capacity levels
  2. Consider starting with the smallest available instance plan that meets your minimum requirements
  3. If creating multiple instances, reduce the number in your initial request

For Your Quota Request: Since you have an active support case, the best path forward is to continue working through the AWS Support Center at https://console.aws.amazon.com/support/. Add detailed correspondence explaining your specific technical constraints—the geographic IP restrictions and latency requirements you've described are legitimate architectural considerations that should be documented in your case.

When providing additional information to your support case, focus on:

  • The specific technical requirements that make Tokyo the only viable region
  • Documentation or evidence of the IP-based restrictions from your data provider
  • Your intended use case and why it cannot be prototyped elsewhere
  • Any business context that demonstrates this is a genuine operational need

Additionally, review your AWS Support plan options, as higher-tier support plans can provide faster response times and more direct assistance with quota-related requests for new accounts with specific regional requirements.

The support team handling your case will have the ability to evaluate your specific circumstances and work with the appropriate internal teams to address region-specific quota needs for legitimate use cases.
Sources
Resolve insufficient instance capacity errors in Lightsail - Amazon Lightsail

answered a month ago

AWS
EXPERT

reviewed a month ago

AWS
SUPPORT ENGINEER

reviewed a month ago

  • Hi Lucky, Thank you for the clear guidance and for acknowledging the regional architectural constraints. I have updated my open support case with complete technical documentation, including:

    The official terms of service and developer documentation from our third-party market data provider designating US IP ranges as restricted jurisdictions. The exact HTTP 451 / 403 edge response errors returned when attempting to establish API and WebSocket connections from US cloud regions. The technical requirement for a single, baseline entry-level instance (2 vCPUs) in ap-northeast-1. Because the regional quota in Tokyo is currently hard-set to 0 vCPUs, launching across different Availability Zones is blocked until baseline capacity is provisioned at the service level. So I will await the service team's review on the support ticket. I appreciate your time and recommendations!

0

Hi,

I've checked on your case and shared your request with our teams. Continue to monitor your case for their updates. I apologize for any concern this has caused.

- Sage A.

AWS
EXPERT

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.