Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

UAE - me-central-1: ecs:CreateCluster and ec2:RunInstances persistently throttled ("operational issue") on newly opted-in region

-2

I opted into UAE (me-central-1) on a new-ish account and can't launch compute there.

  • ecs:CreateCluster → ThrottlingException: "Rate exceeded" (every call, 24h+, even single calls after long idle).
  • ec2:RunInstances → RequestLimitExceeded: "throttled due to an operational issue. Throttling will be removed once the issue is resolved."
  • ECR push → "KMS exception: AccessDenied".

Other services (VPC, ALB, ACM, S3, IAM, RDS subnet group) provision fine in the region. The same ECS/EC2 calls work instantly in us-east-1 and ap-south-1. Already pre-created AWSServiceRoleForECS — no change.

Is there an operational issue / provisioning delay for newly opted-in me-central-1, and how do I get these throttles lifted (ETA)?

Thank you

Topics
ComputeContainersSecurity, Identity, & Compliance
Tags
Service QuotasAmazon EC2AWS Key Management ServiceAmazon Elastic Container Service
Language
English

asked a month ago81 views

2 Answers
1

Hello.

The me-central-1 region has currently lost most of its data center functionality due to a bombing.
As this is impacting AWS services, I recommend using a different region.
https://health.aws.amazon.com/health/status?eventID=arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5

EXPERT

answered a month ago

-1

Based on the symptoms you're describing, this appears to be an account-level provisioning or quota issue specific to the me-central-1 region rather than typical API throttling behavior. The persistent throttling on every single call—even after long idle periods—is not consistent with normal token bucket throttling, which would allow at least some requests to succeed.

For newly opted-in regions, there can sometimes be delays in fully provisioning all service capabilities for an account. The fact that some services (VPC, ALB, ACM, S3, IAM, RDS) work fine while ECS and EC2 operations are completely blocked, combined with the KMS AccessDenied error for ECR, suggests incomplete service initialization or missing backend permissions for your account in that region.

The "operational issue" message in the EC2 throttling error is particularly telling—this typically indicates a backend service issue rather than you exceeding normal API limits.

To resolve this, you should open a support case through the AWS Support Center. When you do, include:

  • The specific region (me-central-1)
  • When you opted into the region
  • The exact error messages you're receiving
  • That the same operations work in other regions
  • That you've already created the AWSServiceRoleForECS

The support team can investigate whether there's an incomplete provisioning process for your account in that region and can work with the backend teams to resolve any service-level blocks. They'll also be able to provide an estimated timeline for resolution.

In the meantime, you might also want to review your AWS Support plan options, as higher-tier plans offer faster response times for operational issues like this.
Sources
Request throttling for the Amazon ECS API - Amazon Elastic Container Service
Handling throttling issues - Amazon Elastic Container Service

answered a month ago

AWS
EXPERT

reviewed 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.

Relevant content