Amazon Connect · Rate Limits

Amazon Connect Rate Limits

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.

22 Limits Throttle: 429
CloudContact CenterCustomer EngagementRate Limiting

Limits

Connect Service API (default) account/region
requests_per_second · second
2
Default RateLimit for most operations; BurstLimit 5. Exceptions documented per API.
GetMetricData account/region
requests_per_second · second
5
BurstLimit 8.
GetMetricDataV2 account/region
requests_per_second · second
10
BurstLimit 10.
GetCurrentMetricData account/region
requests_per_second · second
5
BurstLimit 8.
SearchContacts account/region
requests_per_second · second
0.5
BurstLimit 1.
Contact attribute / lifecycle APIs account/region
requests_per_second · second
10
GetContactAttributes, UpdateContactAttributes, DescribeContact, StopContact, UpdateContact, ListContactReferences, BatchPutContact - BurstLimit 15.
Tag / Untag / UpdateContactRoutingData account/region
requests_per_second · second
20
TagContact / UntagContact BurstLimit 25; UpdateContactRoutingData BurstLimit 20.
Evaluations actions account/region
requests_per_second · second
1
Connect AI Agents (default) account
requests_per_second · second
10
10 TPS default with per-API exceptions.
Customer Profiles (write) account
requests_per_second · second
100
SearchProfiles, ListProfileObjects, CreateProfile, UpdateProfile, MergeProfiles, etc. = 100 TPS. Domain CRUD APIs = 1-5 TPS.
Concurrent active calls per instance instance
concurrent_requests
10
PSTN + WebRTC; adjustable.
Concurrent active chats per instance instance
concurrent_requests
500
Includes SMS, WhatsApp, Apple Messages for Business; idle chats count - use persistent chat to avoid this.
Concurrent active emails per instance instance
concurrent_requests
1000
Adjustable.
Concurrent active tasks per instance instance
concurrent_requests
2500
Adjustable.
Users per instance instance
count
500
Adjustable.
Phone numbers per instance instance
count
5
Adjustable.
Connect Cases - GetCase account
requests_per_second · second
4
BurstLimit 10.
Connect Cases - default account
requests_per_second · second
2
BurstLimit 10 for create/list APIs; 2 for update.
Voice ID - EvaluateSession account
requests_per_second · second
60
Outbound Campaigns - default account/region
requests_per_second · second
2
BurstLimit 5; campaign-mutation APIs limited to 1 RPS / Burst 2; DescribeCampaign 25/35.
Participant Service - SendEvent / SendMessage instance
requests_per_second · second
10
BurstLimit 15.
Contact Lens - ListRealtimeContactAnalysisSegmentsV2 account
requests_per_second · second
2
BurstLimit 5.

Policies

Per-Account/Region Throttle Bucket
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.

Sources