Amazon Connect service quotas - Amazon Connect

Amazon Connect service quotas

All service quotas can be adjusted/increased unless otherwise noted.

Your AWS account has default quotas, formerly referred to as limits, for each AWS service.

To request a quota increase, see Requesting a quota increase in the Service Quotas User Guide. If the quota is not yet available in Service Quotas, use the Amazon Connect service quotas increase form. You must be signed in to your AWS account to access the form.

Important things to know

  • You must create your instance before you can request a service quota increase.

  • We review each request for a quota increase. For smaller increase requests, we can approve in hours. Larger increase requests take time to review, process, approve, and deploy. Depending on your specific implementation, your resource, and the size of quota that you want, a request can take up to 3 weeks. An extra-large worldwide increase can potentially take months. If you're increasing your quotas as part of a larger project, keep this information in mind and plan accordingly.

  • Use the same form to submit a request to port your US phone number from your current carrier to Amazon Connect. For more information about porting phone numbers, see Port your current phone number to Amazon Connect.

  • The quotas apply per AWS Region. You can have multiple Amazon Connect instances in each Region. It's possible to raise quotas for all instances in a Region.

  • This documentation describes the default quotas for new accounts. Because the quotas have been adjusted over time, the default values for your account might be different than the default values described here.

Amazon Connect quotas

Name Default Adjustable

AWS Lambda functions per instance

50

No

Agent status per instance

50

No

Amazon Connect instances per account

2

Yes

Amazon Lex bots per instance

70

No

Amazon Lex V2 bot aliases per instance

100

Yes

Concurrent active calls per instance

10

For more information, see How contacts are counted.

Yes

Concurrent active chats per instance

100

This includes chats that are waiting.

If this quota is exceeded, the API call fails with a quota exceeded error.

Yes

Concurrent active tasks per instance

2500 concurrent active tasks

All tasks that have not yet ended are considered active and are counted as concurrent tasks: tasks that are being routed in flows, waiting in a queue for an agent, being handled by agents, or being run in After Contact Work (ACW).

Yes

Flows per instance

100

Yes

Hours of operation per instance

100

Yes

Maximum duration that a task can be scheduled in future

6 days

No

Modules per instance

200

No

Phone numbers per instance

5

It's possible to get an error message that "You've reached the limit of Phone Numbers," even if it's the first time you've claimed a phone number. All the issues that cause this error message require help from AWS Support to resolve.

Yes

Prompts per instance

500

Yes

Queues per instance

50

Yes

Queues per routing profile per instance

50

This quota refers to number of queue/channel combinations per routing profile. For example, in the following image there are two queues, but there are three queue-channel combinations: Escalation queue Voice, Escalation queue Chat, and BasicQueue Voice. This counts three towards the service limit of 50.


                                    The Routing profiles page, the routing profiles queues
                                        section, voice and chat queues.
Yes

Quick connects per instance

100

Yes

Rate of API requests

See Amazon Connect API throttling quotas.

Yes

Reports per instance

2000

Personal saved reports count towards the reports per instance. For example, if one of your supervisors saves a report every day, it will count towards your overall number of saved reports per instance.

As a best practice, we recommend you implement policies so reports don't pile up.

Yes

Routing profiles per instance

100

Yes

Scheduled reports per instance

50

No

Security profiles per instance

100

Yes

Task templates per instance

50

No

Task template customized fields per instance

50

No

Theme detection reports generated within 30 minutes per instance

6

Yes

User hierarchy groups per instance

500

This quota applies to the total number of hierarchy groups you have, across all levels. There is no feature limit for how many hierarchy groups you can have for each level. For example, one level could have 500 hierarchy groups, which would reach the quota for your instance.

Yes

Users per instance

500

Yes

Amazon Connect AppIntegrations service quotas

Name Default Adjustable

Data integration associations per data integration

10

Yes

Data integrations per Region

10

Yes

Event integration associations per event integration

10

Yes

Event integrations per Region

10

Yes

Amazon Connect Cases service quotas

Name Default Adjustable

Cases domains per AWS account

5

Yes

Fields in a Cases domain

100

Yes

Field options per single-select field in the Cases domain

100

Yes

Layouts in a Cases domain

50

Yes

Templates in a Cases domain

50

Yes

Related items that can be attached to a case

100

Yes

Case fields per case layout

30

Yes

Contact Lens service quotas

Name Default Adjustable

Concurrent real-time calls with analytics

50

100 for US East (N. Virginia)

Yes

Concurrent post-call analytics jobs

200

See Derive Concurrent post-call analytics jobs based on your Amazon Connect call volume.

Yes

Concurrent post-chat analytics jobs

200

Yes

Derive Concurrent post-call analytics jobs based on your Amazon Connect call volume

A post-contact (call or chat) analytics job is kicked off after the completion of each contact with Contact Lens enabled. The time to complete a post-contact analytics job is about 40% of the call length. To calculate concurrent post-call analytics jobs, use the following formula:

(average call duration in minutes) * (0.4) * (calls per hour) / (60)

The following table shows some examples.

Average call duration (in minutes) Calls per hour* Approximate Concurrent post-call jobs

5

1000

33

10

500

33

10

1000

67

10

3000

200

*For the calculations in the preceding table, we assume a fairly uniform distribution of calls during the hour. If you have more complex traffic patterns, contact AWS Support with details about your anticipated traffic pattern.

Amazon Connect Customer Profiles service quotas

Name Default Adjustable

Amazon Connect Customer Profiles domains count

100

Yes

Keys per object type

10

Yes

Maximum expiration in days

1,096 (3 years)

This is the expiration of objects and profiles.

Yes

Maximum number of integrations

50

Yes

Maximum size of all objects for a profile

50MB

Yes

Object and profile maximum size

250KB

No

Object types per domain

100

Yes

Objects per profile

1000

This is the maximum number of objects that can be attached to a profile.

Yes

Maximum number of Identity Resolution Jobs each week for a domain

3

No

Maximum number of consolidation rules in an Identity Resolution Job

10

No

Maximum number of attributes in each consolidation rule

20

No

Outbound campaigns quotas

Name Default Adjustable

Amazon Connect campaigns

25

Yes

Amazon Connect Voice ID service quotas

Item Default quotas

Domains

3

This quota applies per account.

Concurrent active sessions per domain

50

See the following table for information about how to derive your Concurrent active sessions quota based on your Amazon Connect call volume.

Maximum number of fraudsters per watchlist

500

Maximum number of watchlists per domain

3, including the default watchlist of a domain

Maximum number of speakers per domain

100,000

Active Batch Speaker Enrollment Jobs per domain

1

Active Batch Fraudster Registration Jobs per domain

1

Speakers per Batch Speaker Enrollment Job

10,000

Fraudsters per Batch Fraudster Registration Job

500

Derive Concurrent active sessions based on your Amazon Connect call volume

Use the information in the following table to derive your quota for Voice ID Concurrent active sessions per domain. Base your quota on the number of voice calls handled by your Amazon Connect contact center where Voice ID is enabled.

Amazon Connect Voice Contacts (Calls)/Hour* Voice ID Concurrent active sessions

1,000

50

5,000

250

10,000

500

20,000

1,000

50,000

2,500

*For the calculations in the preceding table, we assume a fairly uniform distribution of calls during the hour. If you have more complex traffic patterns, contact AWS Support with details about your anticipated traffic pattern.

Amazon Connect Wisdom service quotas

Item Default quotas Adjustable

Assistants

5

No

Knowledge bases

10

Maximum size of a knowledge base

5GB per knowledge base

Content per knowledge base

5,000

Examples of content are frequently asked questions (FAQs), wikis, articles, and step-by-step instructions for handling different customer issues.

Maximum size per document

1MB

RateLimit for all APIs

50TPS

How contacts are counted

The following contacts are counted in Concurrent active calls per instance:

  • Handled by a flow

  • Waiting in queue

  • Handled by an agent

  • Outbound call

The following contacts are not counted:

  • Callbacks waiting in a callback queue are not counted until the callback is offered to an available agent.

  • External transfers

If the quota for Concurrent active calls per instance is exceeded, contacts get a reorder tone (also known as a fast busy tone), which indicates that there is no available transmission path to the called number.

You can calculate your configured quota using CloudWatch metrics. For instructions, see Use CloudWatch metrics to calculate concurrent call quota.

If you're only taking calls you can also determine your Concurrent active calls per instance quota by doing the following:

  1. Navigate to the Edit a queue page: choose Routing, Queues, and choose a queue.

  2. Choose Set a limit across all channels.

  3. Enter an exceptionally large number in the Maximum contacts in queue box for the contact limit.

The resulting error message displays your quota as Concurrent active calls per instance - 1.

For example, in the following image from the Edit queues page, you add 1 to the error message, to get Concurrent active calls per instance quota = 10.


                The edit queue page, Maximum contacts in queue set to 1000, a message that
                    max contacts is 9.

The error message shows 9 because you must set always set Maximum contacts in queue to a number that is at least 1 less than your Concurrent active calls per instance quota (which is the default limit).

API throttling quotas

Amazon Connect API throttling quotas

Amazon Connect throttling quotas are by account, and per Region, not by user and not by instance. For example:

  • If different users from the same account make requests, they are sharing a throttle bucket.

  • If multiple requests are sent from different instances from the same account, they are also sharing a throttle bucket.

When you use the Amazon Connect Service API , the number of requests per second is limited to the following:

Amazon Connect Participant Service API throttling quotas

For the Amazon Connect Participant Service, the quotas are by instance.

When you use the Amazon Connect Participant Service API, the number of requests per second is limited to the following:

  • CreateParticipantConnection: a RateLimit of 6 requests per second, and a BurstLimit of 9 requests per second.

  • DisconnectParticipant: a RateLimit of 3 requests per second, and a BurstLimit of 5 requests per second.

  • GetTranscript: a RateLimit of 8 requests per second, and a BurstLimit of 12 requests per second.

  • SendEvent and SendMessage: a RateLimit of 10 requests per second, and a BurstLimit of 15 requests per second.

  • StartAttachmentUpload: a RateLimit of 2 requests per second, and a BurstLimit of 5 requests per second.

  • CompleteAttachmentUpload: a RateLimit of 2 requests per second, and a BurstLimit of 5 requests per second.

  • GetAttachment: a RateLimit of 8 requests per second, and a BurstLimit of 12 requests per second.

Amazon Connect Contact Lens Service API throttling quotas

Amazon Connect Contact Lens throttling quotas are by account, not by user and not by instance. For example:

  • If different users from the same account make requests, they are sharing a throttle bucket.

  • If multiple requests are sent from different instances from the same account, they are also sharing a throttle bucket.

When you use the Amazon Connect Contact Lens API, the number of requests per second is limited to the following:

Amazon Connect Cases API throttling quotas

API Default TPS throttling limits

CreateCase, SearchCases, UpdateCase, AssociateContact, ListTemplates, CreateRelatedItem, SearchRelatedItems

10

CreateField, ListFields, CreateDomain, GetDomain,CreateTemplate, BatchPutFieldOptions, CreateLayout, UpdateLayout, UpdateTemplate, UpdateField

5

BatchGetField

25

GetCase

15

GetTemplate, GetLayout

20

ListFieldOptions

15

Amazon Connect Voice ID Service API throttling quotas

API Default TPS throttling limits

EvaluateSession

60

Domain APIs: CreateDomain, DescribeDomain, UpdateDomain, DeleteDomain, ListDomains

Batch APIs: StartSpeakerEnrollmentJob, DescribeSpeakerEnrollmentJob, ListSpeakerEnrollmentJobs, StartFraudsterRegistrationJob, DescribeFraudsterRegistrationJob, ListFraudsterRegistrationJobs

2

ListSpeakers

5

DescribeSpeaker, OptOutSpeaker, DeleteSpeaker, DescribeFraudster, DeleteFraudster

10

CreateIntegrationAssociation, DeleteIntegrationAssociation, ListIntegrationAssociation

2

TagResource, UnTagResource, ListTagsForResource

2