Amazon Connect API throttling is enforced per AWS account and per Region, not per user or instance. The default Connect Service API rate is 2 RPS with a burst of 5 RPS, with per-API exceptions documented (metric, contact, integration, and search APIs have higher limits). Contact Lens, Cases, Customer Profiles, Voice ID, AI Agents, Outbound Campaigns, and Participant APIs each publish their own throttling tables. Most quotas are adjustable via AWS Service Quotas requests; small increases approve in hours, larger increases can take up to three weeks. Resource-level quotas (users, queues, concurrent calls/chats) are per-instance.
Throttling is shared across all users and instances inside the same AWS account and Region; requests across instances share the same bucket.
Service Quotas Adjustment
Most quotas are adjustable via AWS Service Quotas. Small increases approve in hours; larger or worldwide increases can take up to three weeks. Open a quota-increase request before going live.
Resource vs Account Quotas
Resource-level quotas (users, queues, concurrent calls/chats/emails) apply per Connect instance. Account-level quotas (API TPS, instance count) apply across instances in a Region.
Backoff Strategy
Implement exponential backoff with jitter on 429/503 throttling responses; AWS SDKs handle this by default.
Plan Ahead
Configure CloudWatch alerts at 80% of quota limits; coordinate with AWS support before production go-live for capacity planning.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.