# Amazon Connect service quotas
**Note**
End of support notice: On May 20, 2026, AWS will end support for Amazon Connect Voice ID. After May 20, 2026, you will no longer be able to access Voice ID on the Amazon Connect console, access Voice ID features on the Amazon Connect admin website or Contact Control Panel, or access Voice ID resources. For more information, visit [Amazon Connect Voice ID end of support](https://docs.aws.amazon.com/connect/latest/adminguide/amazonconnect-voiceid-end-of-support.html).
**All service quotas can be adjusted 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](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the *Service Quotas User Guide*.
**Topics**
+ [
## Important things to know
](#important-quota-info)
+ [
## Amazon Connect quotas
](#connect-quotas)
+ [AppIntegrations quotas](#app-integration-quotas)
+ [Connect AI agents quotas](#connect-ai-agents-quotas)
+ [Cases quotas](#cases-quotas)
+ [Contact Lens quotas](#contactlens-quotas)
+ [Customer Profiles quotas](#customer-profiles-quotas)
+ [Outbound campaigns quotas](#outbound-communications-quotas)
+ [Voice ID quotas](#voiceid-quotas)
+ [
## How contacts are counted
](#contact-counting-criteria)
+ [Plan ahead with quotas](plan-ahead-quotas.md)
+ [Feature specifications](feature-limits.md)
+ [
# Countries that call centers using Amazon Connect can call by default
](country-code-allow-list.md)
+ [
## API throttling quotas
](#api-throttling-quotas)
## Important things to know
+ You must create your instance before you can request a service quota increase.
+ We recommend you [plan for quota changes](plan-ahead-quotas.md). This will help support the lifecyle of your contact center.
+ 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](plan-ahead-quotas.md).
+ There are two types of quota adjustability: account level and resource-level.
+ Account level quotas, when adjusted, apply to all Amazon Connect instances in this account and Region. For example, the maximum transactions per second (TPS) limits for a specific API.
+ Resource level quotas, when adjusted, only apply to resources within a specific Amazon Connect instance. For example, the maximum number of users per instance. Resource level quotas cannot be adjusted at the account level.
+ The quotas apply per [AWS Region](https://docs.aws.amazon.com/servicequotas/latest/userguide/intro.html#intro_getting-started). You can have multiple Amazon Connect instances in each Region. It's possible to raise quotas for all instances in a Region.
+ Default quota values in this documentation are specifically for new accounts. Because quota defaults have been adjusted over time, the default and applied quota values for your account might be lower than the default values described in this topic.
+ Not all quotas can be adjusted.
+ You need AWS CLI version 2.13.20 or higher to view and manage resource-level quotas such as **Phone numbers per instance** for Amazon Connect.
+ 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 a current phone number to Amazon Connect](port-phone-number.md).
## Amazon Connect quotas
| Name | Default | Adjustable | Adjustability |
| --- | --- | --- | --- |
| Active email contact expiry | 14 days (Default) Customizable up to 90 days using the [Flow block in Amazon Connect: Set contact attributes](set-contact-attributes.md) flow block or [Expiry](https://docs.aws.amazon.com/connect/latest/APIReference/API_Expiry.html) API to update the connect:ContactExpiry [segment attribute](connect-attrib-list.md#attribs-segment-attributes). This determines how long an email contact can remain active (e.g., waiting in queue or assigned to an agent) before expiring and closing automatically. "No" for adjustability means that you cannot customize or increase this attribute to be greater than 90 days. | No | Resource Level |
| Active email conversation (thread) expiry | 90 days Meaning if an end customer (using their email client) or an agent (using their agent application) replies to an email as part of an ongoing conversation (thread) within 90 days, the email reply will automatically be included within that same [email conversation (thread)](email-capabilities.md#email-capabilities-howthreadsmanaged) in Amazon Connect. If they reply after 90 days, it will start a new [email conversation (thread)](email-capabilities.md#email-capabilities-howthreadsmanaged) in Amazon Connect. | No | Resource Level |
| AWS Lambda functions per instance | 50 | Yes | Resource Level |
| Agent status per instance | 50 | No | Not Adjustable |
| Amazon Connect instances per account | 2 | Yes | Account Level |
| Amazon Lex bots per instance | 70 | No | Resource Level |
| Amazon Lex V2 bot aliases per instance | 100 | Yes | Resource Level |
| Concurrent active calls per instance | 10 This includes PSTN and WebRTC calls. For more information, see [How contacts are counted](#contact-counting-criteria). | Yes | Resource Level |
| Concurrent active chats per instance | 500 This includes SMS, WhatsApp, and Apple Messages for Business. It also includes chats that are waiting. If the customer has initiated a chat and has gone silent for hours, this idle chat is counted against the quota. To avoid having idle chats count against your quota, we recommend using [persistent chats](chat-persistence.md). If this quota is exceeded, the API call fails with a quota exceeded error. | Yes | Resource Level |
| Concurrent active emails per instance | 1000 (Default) This is the total of all email contacts in an Amazon Connect instance in an active state. An email contact in an active state includes: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html) Example: 200 emails in queue \$1 10 emails assigned to 10 agents \$1 5 outbound emails being sent by an agent (either a reply or agent-initiated) = 215 Concurrent active emails in the instance This service limit should be monitored by the [Amazon Connect metrics sent to CloudWatch](monitoring-cloudwatch.md#connect-metrics-cloudwatch) using ConcurrentEmails and ConcurrentEmailsPercentage to ensure adequate scaling of your Amazon Connect instance. If this quota is exceeded by your Amazon Connect instance, Email API calls will fail with a quota exceeded error. We recommend following the Amazon Connect [ongoing operations management](plan-ahead-quotas.md#production-environment-go-live-quotas) approach of configuring alerts at 80% of quota limits to notify you when to [request a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html). | Yes | Resource Level |
| 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 | Resource Level |
| Custom Metrics per instance | 1000 | No | Resource Level |
| Data tables per instance | 100 | Yes | Resource Level |
| Primary attributes per data table | 5 | No | Not Adjustable |
| Attributes per data table | 100 | No | Not Adjustable |
| Values per data table | 1000 | Yes | Resource Level |
| Email addresses per instance | 100 email addresses (Default) Can be increased up to 500 email addresses per instance. | Yes | Resource Level |
| Email addresses per email (contact) message | 50 email addresses per email contact (message) total across To and CC. Inbound email contacts (messages) support any combination of 50 email addresses total across To and CC. Outbound email contacts (messages) support only 1 email address in To and up to 49 email addresses in CC. BCC email addresses are not supported in Amazon Connect. | No | Not Adjustable |
| Email domains per instance | 1 Amazon Connect email domain 100 custom email domains | No | Resource Level |
| Maximum individual attachments size | 20 MB | Yes | Resource Level |
| Flows per instance | 100 | Yes | Resource Level |
| Hours of operation per instance | 100 | Yes | Resource Level |
| Overrides per hours of operation | 50 | No | Not Adjustable |
| Associations to inherit recurring overrides per hours of operation | 3 | No | Not Adjustable |
| Maximum duration that a task can be scheduled in future | 6 days | No | Not Adjustable |
| Maximum number of reschedules allowed for a task scheduled for a future time | 20 | No | Not Adjustable |
| Modules per instance | 200 | Yes | Resource Level |
| 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 Support to resolve. | Yes | Resource Level |
| Predefined attributes per instance | 150 | Yes | Resource Level |
| Proficiencies per agent | 10 | Yes | Resource Level |
| Prompts per instance | 500 | Yes | Resource Level |
| Queues per instance | 100 | Yes | Resource Level |
| Maximum contacts in an agent queue per instance | 10 This quota applies to the maximum contacts you can have queued at once in a single [agent queue](concepts-queues-standard-and-agent.md). The same quota applies to every agent queue in your instance. | Yes | Resource Level |
| 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 quota of 50. This same quota also applies to manually assigned queues; each of these two types of queue have up to this limit, independent of each other. For example, it's possible to have a max of 50 queue-channel combinations for queues and another 50 queue-channel combinations for manual assignment queues. ![\[The Routing profiles page, the routing profiles queues section, voice and chat queues.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/routing-profile-queue-channel-combinations.png) | Yes | Resource Level |
| Quick connects per instance | 100 | Yes | Resource Level |
| Rate of API requests | See [Amazon Connect API throttling quotas](#connect-api-quotas). | Yes | Account Level |
| Reports per instance | 2,000 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 | Resource Level |
| Routing profiles per instance | 500 | Yes | Resource Level |
| Scheduled reports per instance | 100 | Yes | Resource Level |
| Security profiles per instance | 100 | Yes | Resource Level |
| Task templates per instance | 50 | No | Not Adjustable |
| Task template customized fields per instance | 50 | No | Not Adjustable |
| Theme detection reports generated within 30 minutes per instance | 6 | No | Resource Level |
| 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 | Resource Level |
| Users per instance | 500 The maximum number of users you can create in this instance in the current Region. All 500 users can be logged into Amazon Connect concurrently as agents and handling contacts. | Yes | Resource Level |
## Amazon Connect AppIntegrations service quotas
All AppIntegrations quotas are at the Account level.
| 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 |
| Application per region (third-party application) | 25 | No |
## Connect AI agents service quotas
All Amazon Q quotas are at the Account level.
**Note**
To request a quota adjustment, please contact [AWS Support](https://console.aws.amazon.com/support/home).
| Item | Default quotas | Adjustable |
| --- | --- | --- |
| Assistants | 5 | No |
| Knowledge bases | 10 | Yes |
| Assistant associations | 20 | No |
| Maximum size of a knowledge base | 5GB per knowledge base | Yes |
| Quick responses per knowledge base | 1,000 | Yes |
| 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. | Yes |
| Maximum size per document | 5MB | Yes |
| Number of message (email, SMS, WhatsApp) templates per knowledge base | 200 | Yes |
| Number of versions per message (email, SMS, WhatsApp) template | 20 | No |
| Number of attachments per email message template | 10 | No |
| Maximum size per attachment in an email message template | 1 MB | No |
| Maximum number of characters in an email message template | 5,000,000 | No |
| Maximum number of characters in an SMS message template | 800 | No |
| Number of assigned routing profiles per quick response or email template | 40 | No |
| RateLimit for all APIs | 10 TPS except, [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html) | Yes |
## Amazon Connect Cases service quotas
All the Cases quotas are at the Account level.
| Name | Default | Adjustable |
| --- | --- | --- |
| Cases domains per AWS account | 5 | Yes |
| Fields in a Cases domain | 500 | Yes |
| Field options per single-select field in the Cases domain | 500 | Yes |
| Layouts in a Cases domain | 100 | Yes |
| Templates in a Cases domain | 100 | Yes |
| Related items that can be attached to a case | 200 | Yes |
| Files that can be attached to a case | 50 | Yes |
| Case fields per case layout | 100 | No |
| SLAs that can be attached to a case | 10 | Yes |
| Fields in a Custom type related item | 5 | Yes |
## Contact Lens service quotas
All Contact Lens quotas are at the Account level.
| Name | Default | Adjustable |
| --- | --- | --- |
| Concurrent real-time calls with analytics | 300 | Yes |
| Concurrent post-call analytics jobs | 200 See [Derive Concurrent post-call analytics jobs based on your Amazon Connect call volume](#contactlens-concurrent-analytics-jobs). | Yes |
| Concurrent chat analytics jobs | 200 | Yes |
| Concurrent automated interaction analytics jobs | 20 | Yes |
| Concurrent post-contact agent conversation summary jobs (shared between all supported channels - voice, chat) | 10 | Yes |
| Concurrent post-contact automated interaction summary jobs (shared between all supported channels - voice, chat) | 2 | Yes |
| Concurrent after-call agent conversation summary jobs (shared between all supported channels - voice, chat) | 2 | Yes |
| External voice analytics connectors | 0 | Yes |
| Maximum active recording sessions from external voice systems per instance | 10 | Yes |
| Number of evaluation questions that can be answered with Ask AI on a single contact (for manually submitted evaluations) | 10 | Yes\$1 |
| Number of evaluation questions that can be answered automatically on a contact using generative AI (for automated submissions of evaluations) | 10 | Yes\$1 |
\$1Through a support ticket.
### Derive Concurrent post-call analytics jobs based on your Amazon Connect call volume
A post-call analytics job is kicked off after the completion of each contact that has Contact Lens conversational analytics [enabled](enable-analytics.md) on it. The time to complete a post-call analytics job can vary, but for planning purposes, you can estimate that it usually takes about 40% of the call length. If you choose 40% for your estimate, to calculate concurrent post-call analytics jobs, you would use the following formula:
`(average call duration in minutes) * (0.4) * (calls per hour) / (60)`
The following table shows some examples of what the approximate number of concurrent post call jobs would be if you assume the time to complete the analysis is 40%.
| Average call duration (in minutes) | Calls per hour\$1 | Approximate Concurrent post-call jobs |
| --- | --- | --- |
| 5 | 1000 | 33 |
| 10 | 500 | 33 |
| 10 | 1000 | 67 |
| 10 | 3000 | 200 |
\$1For the example calculations in the preceding table, we assume a fairly uniform distribution of calls during the hour. If you have more complex traffic patterns, [contact Support](https://console.aws.amazon.com/support/home) with details about your anticipated traffic pattern.
## Amazon Connect Customer Profiles service quotas
All Customer Profiles quotas are at the Account level.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html)
## Amazon Connect Outbound campaigns service quotas
All outbound campaigns quotas are at the Account level.
| Name | Default | Adjustable | Adjustability |
| --- | --- | --- | --- |
| Campaigns | 25 This is the maximum number of campaigns that an AWS account can configure. | Yes | Resource Level |
| Concurrent campaign active calls per instance | 0 The maximum number of concurrent campaign active calls you can have in this instance in the current Region. If this is exceeded, contacts will get a fast busy tone, which indicates the transmission path to the called number is not available. | Yes | Resource Level |
## Amazon Connect Voice ID service quotas
All Voice ID quotas are at the Account level.
| Item | Default quotas |
| --- | --- |
| Domains | 3 This quota applies per account. |
| Concurrent active sessions per domain | 50 See the following [table](#voiceid-concurrent-active-sessions) 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\$1 | Voice ID Concurrent active sessions |
| --- | --- |
| 1,000 | 50 |
| 5,000 | 250 |
| 10,000 | 500 |
| 20,000 | 1,000 |
| 50,000 | 2,500 |
\$1For 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 Support](https://console.aws.amazon.com/support/home) with details about your anticipated traffic pattern.
## 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](monitoring-cloudwatch.md#connect-cloudwatch-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.
1. Choose **Set a limit across all channels**.
1. Enter an exceptionally large number in the **Maximum contacts in queue** box for the contact limit.
The resulting error message displays your quota as less than the sum of the following quotas combined: **Concurrent calls per instance** \$1 **Concurrent active chats per instance** \$1 **Concurrent active tasks per instance**.
For example, in the following image from the **Edit queues** page, you add 1 to the error message, to get **Concurrent calls per instance** \$1 **Concurrent active chats per instance** \$1 **Concurrent active tasks per instance** quota = 3010.
![\[The edit queue page, Maximum contacts in queue.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/concurrent-call-quota.png)
The error message shows 3009 because you must set always set **Maximum contacts in queue** to a number that is at least 1 *less than* your combined quota (which is the default limit).
# Plan ahead with Amazon Connect quotas
Learn how to plan for and manage service quotas during key phases of your contact center lifecycle.
## Planning for production launch
Before launching your Amazon Connect contact center, request service quota increases to ensure sufficient capacity for your agents and concurrent calls. Follow these best practices:
1. **Include quotas in your migration plan**.
+ Address service quotas during the project design phase.
+ Submit quota increase requests well before final migration stages.
1. **Size your production workloads**.
+ Prepare the following data to support your quota requests:
+ Current number of agents
+ Call volume metrics
+ Average call duration
+ Be ready to provide additional metrics as needed so we can process your request.
**Note**
The data we ask for is based on the service quota. It is needed to correctly size the quotas you require.
## Ongoing operations management
Monitor your contact center's quota utilization by using Amazon CloudWatch. For detailed metrics, see [Amazon Connect metrics sent to CloudWatch](monitoring-cloudwatch.md#connect-metrics-cloudwatch).
**Best practice**: Set CloudWatch alarms to monitor service quota usage:
+ Configure alerts at 80% of quota limits.
+ Request quota increases when usage consistently exceeds this threshold.
## Managing emergency events
If you need urgent support during an emergency:
+ Open a high-severity support case through the AWS Support Center:
+ Business Support plan: Select **Production system down** (1-hour response).
+ Enterprise On-Ramp or Enterprise Support plan: Select **Business-critical system down**.
+ Enterprise Support: 15-minute response
+ Enterprise On-Ramp: 30-minute response
+ Contact your account team (such as your AWS Technical Account Manager and Solutions Architect) to ask for assistance.
During high-volume events, implement these queue management practices:
+ Use the [Get metrics](get-queue-metrics.md) flow block to communicate wait times to your customers.
+ Enable [queued callbacks](setup-queued-cb.md).
+ Balance operational best practices with service quota constraints.
For more information, see [Creating a support case](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case).
# Amazon Connect feature specifications
**Important**
You can't increase the feature specifications listed here. They are hard limits.
The following tables list the various Amazon Connect feature specifications.
**Topics**
+ [Chat feature specifications](#feature-limits-chat)
+ [
## WhatsApp business messaging feature specifications
](#whatsapp-specs)
+ [Email feature specifications](#email-feature-specs)
+ [Task feature specifications](#feature-limits-tasks)
+ [Forecasting, capacity planning, and scheduling](#forecasting-cap-planning-scheduling-specs)
+ [Integration association resource](#integration-association-resource-feature-specs)
+ [Amazon Connect Contact Lens](#contact-lens-feature-specs)
+ [Evaluation forms](#evaluationforms-feature-specs)
+ [Amazon Connect Rules](#rules-feature-specs)
| Item | Feature Specification |
| --- | --- |
| Agent activity retention | 24 months from the time the event occurred |
| Approved origin per Amazon Connect instance | 100 |
| File types supported for attachments to emails, cases, or chats | .csv, .doc, .docx, .heic, .jfif, .jpeg, .jpg, .mov, .mp4, .pdf, .png, .ppt, .pptx, .rtf, .txt, .wav, .xls, .xlsx For more information about supported file types for WhatsApp business messaging, see [WhatsApp business messaging feature specifications](#whatsapp-specs) later in this topic. |
| Maximum file size for an attachment to an email, case, or a chat | 20MB For more information about supported file sizes for WhatsApp business messaging, see [WhatsApp business messaging feature specifications](#whatsapp-specs) later in this topic. |
| Maximum timeout for an attachment scanner | 60 seconds |
| Maximum size of a real-time metrics report | 200KB |
| When the [Multi-Party Calls and Enhanced Monitoring for Voice](monitor-barge.md#monitor-barge-set-up) capability is enabled, voice supports 6 participants. Two supervisors can monitor the call. | 6 For example, you can have a group of 6 participants in the call at the same time. Two supervisors can monitor the call. The two supervisors can do two silent monitor sessions, or one silent monitor and one barge-in session. The total number of participants on a call would look like this: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/feature-limits.html) |
| When the [Multi-Party Calls and Enhanced Monitoring for Voice](monitor-barge.md#monitor-barge-set-up) capability is not enabled, voice supports 3 participants on the call, and 5 supervisors monitoring the call. | 3 There can be 3 participants in total: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/feature-limits.html) |
| Quick connects you can assign to a queue | 700 |
| Participants on a conference call | 6 The participants are the customer, agent, and others who can be agents or external third-parties. |
| Contact record retention for all channels and subtypes (voice, email, tasks, and chat, including SMS, WhatsApp, and Apple Messages for Business). | 24 months from the time the associated contact was initiated. You can choose to stream contact records to Kinesis so you can manage retention and perform advanced analysis. |
| Maximum size of the returned data in a Lambda function | Less than 32KB of UTF-8 data |
| Limit on creating and deleting instances | 100 instances can be created or deleted in 30 days Amazon Connect enforces a limit on the **total** number of instances that you can create and delete in 30 days. If you exceed this limit, you will get an error message indicating there has been an excessive number of attempts at creating or deleting instances. You must wait 30 days before you can restart creating and deleting instances in your account. For example, if you create 80 instances and delete 20 over the course of 30 days, you must wait an additional 30 days before you can create or delete any more instances. If you create and delete the same instance 100 times in 30 days, the limit also applies. |
| Searchable custom contact attributes | 50 |
| Replica instances (created by using the [ReplicateInstance](https://docs.aws.amazon.com/connect/latest/APIReference/API_ReplicateInstance.html) API) | 5 per account |
| Traffic distribution groups | 8 per replicated instance |
## Chat feature specifications
| Item | Feature Specification |
| --- | --- |
| Attachments per chat conversation | 35 |
| Active chats per agent | 10 |
| Participants on a conference chat | 6 The participants are the customer, agent, and others who can be agents. |
| Custom participants (such as a custom bot) on a contact | 1 |
| Chat contacts that a supervisor can monitor concurrently | Depends on the number of concurrent chats limit set in the supervisor's routing profile |
| People who can monitor the same agent chat at the same time regardless of whether the [Enable Multi-Party Chats and Enhanced Monitoring for Chat](monitor-barge.md#monitor-barge-set-up) capability is enabled for an instance | 5 For example, you can have a group of 5 people monitor a chat at the same time, and then a different group of 5 people monitor a different chat at the same time, and so on. The total number of participants on the chat would look like this: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/feature-limits.html) |
| Supervisors who can barge in on a chat between an agent and a customer when the [Enable Multi-Party Chats and Enhanced Monitoring for Chat](monitor-barge.md#monitor-barge-set-up) capability enabled for an instance | 1 Only 1 supervisor can be in barged in mode for a given chat. |
| Total duration per chat | Up to 7 days, including wait time [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/connect/latest/adminguide/feature-limits.html) |
| Characters per chat message | 1024 |
| Open websocket connections per chat participant | 5 |
| Chat Amazon Lex bot integration timeout | 10 seconds The maximum time within which the Amazon Lex bot must respond to the chat customer's prompt. |
| Past chat transcript file size. This applies to [persistent chat](chat-persistence.md). | 5MB |
| Past contacts that can be traversed by Amazon Connect chat. This applies to [persistent chat](chat-persistence.md). | 100 |
| Communications widgets that can be created and customized per instance | 20 |
| File types supported for attachments to cases or chats | .csv, .doc, .docx, .heic, .jfif, .jpeg, .jpg, .mov, .mp4, .pdf, .png, .ppt, .pptx, .rtf, .txt, .wav, .xls, .xlsx |
| Maximum file size for an attachment to a case or a chat | 20MB |
## WhatsApp business messaging feature specifications
The following table ists the specifications for WhatsApp business messaging
| **Media type** | **Supported file types** | **Maximum file size** |
| --- | --- | --- |
| Image | .jpeg, .jpg, .jfif, .png | 5MB |
| Video | .mp4, .3gp | 16MB |
| Document | .txt, .pdf, .ppt, .pptx, .doc, .docx, .xls, .xlsx | 20MB |
| Audio | .aac, .m4a, .mp3, .amr, .ogg | 16MB |
| Sticker | Not supported | Not supported |
## Email feature specifications
| Item | Feature Specification |
| --- | --- |
| Maximum email message body size | 5 MB |
| Email message body format | HTML (`text/html`) (Default) Plain text (`text/plain`) All email contacts (messages) sent by Amazon Connect are handled in HTML (`text/html`) format by default. Additionally, a plain text (`text/plain`) version is stored and available for all email contacts (messages) in Amazon Connect for features like the [Flow block in Amazon Connect: Get stored content](get-stored-content.md) flow block. |
| Maximum email message body plus attachments size | 25 MB |
| File attachments per email contact (message) | 10 attachments |
| Inline images per email contact (message) | No limit so long as the size of inline images received in the email message does not exceed 5 MB. |
| Inline image formats supported | `image/jpg`, `image/jpeg`, `image/png`, `image/gif`, `image/svg`, `image/webp`, `image/bmp`, `image/heif`, `image/heic` All inline images are Base64 encoded when storing email messages with Amazon Connect. |
| Email message and attachment retention | This is defined by your Amazon S3 lifecycle configuration. For more information, see [Managing your storage lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) in the *Amazon Simple Storage Service User Guide*. Contact record retention for all channels and subtypes still applies for email contact data. You can easily download and access email messages and attachments using the [Download recordings and transcripts of past conversations in Amazon Connect](download-recordings.md) feature. |
| Active email contact expiry | 14 days (Default) Customizable up to 90 days using the [Flow block in Amazon Connect: Set contact attributes](set-contact-attributes.md) flow block or [Expiry](https://docs.aws.amazon.com/connect/latest/APIReference/API_Expiry.html) API to update the connect:ContactExpiry [segment attribute](connect-attrib-list.md#attribs-segment-attributes). This determines how long an email contact can remain active (e.g., waiting in queue or assigned to an agent) before expiring and closing automatically. "No" for adjustability means that you cannot customize or increase this attribute to be greater than 90 days. |
| Email addresses per email (contact) message | 50 email addresses per email contact (message) total across To and CC. Inbound email contacts (messages) support any combination of 50 email addresses total across To and CC. Outbound email contacts (messages) support only 1 email address in To and up to 49 email addresses in CC. Only 1 from email address per email contact (message). BCC email addresses are not supported in Amazon Connect. |
| Maximum number of characters in email subject | 998 |
| Maximum length of an email address | 255 |
| Maximum length of a display name for an email address | 256 |
## Task feature specifications
| Item | Feature Specification |
| --- | --- |
| Task templates per instance | 50 |
| Task template customized fields per instance | 50 |
| Maximum duration of a task | Default is 7 days, extensible up to 30 days |
| Maximum number of transfers for a task | 11 transfers |
| Maximum number of linked tasks on an existing contact | 11 |
## Forecasting, capacity planning, and scheduling feature specifications
| Item | Feature Specification |
| --- | --- |
| Agents per schedule generation run | 800 |
| Agents per staffing group | 200 |
| Capacity plans per instance | 500 |
| Capacity scenarios per instance | 500 |
| Capacity plan user data uploads per instance | 500 |
| Capacity plan override uploads per instance | 5000 |
| Concurrent uploads per instance | 20 |
| File size per upload of agent time off data | 1GB |
| File size per upload of time off group allowance data | 1GB The .csv file can cover up to 13 months. |
| File size per upload of capacity plan user data | 1GB |
| File size per upload of capacity plan overrides | 250MB |
| File size per upload of forecast overrides | 250MB |
| File size per upload of historical actuals | 1GB |
| Historical actuals 15 or 30 minute interval aggregated file size limit | 2GB |
| Historical actuals daily interval aggregated file size limit | 2GB |
| Forecast groups per instance | 500 |
| Forecast override uploads per instance | 500 |
| Historical actuals 15 or 30 minute interval file count | 300 |
| Historical actuals daily interval file count | 300 |
| Queues per forecast group | 200 |
| Schedules per instance | 1000 |
| Shift activities per instance | 500 |
| Shift activities per shift profile | 10 |
| Shift profiles per instance | 2500 |
| Shift rotation steps per pattern | 52 |
| Shift rotation weeks per pattern | 52 |
| Shift rotations associated with a single shift profile | 1300 |
| Shift rotations per instance | 1300 |
| Staffing groups per forecast group | 100 |
| Staffing groups per instance | 1300 |
| Staffing groups per supervisor/manager | 250 |
| Supervisors/managers per staffing group | 100 |
## Integration association resource feature specifications
The following table lists feature specifications for the integration association resource. It lists how many of each type of integration association resource can be ingested.
| Item | Feature Specification |
| --- | --- |
| Attachment scanner | 1 |
| Voice ID domain | 1 |
| Amazon Pinpoint app | 1 |
| Event | 10 The event integration resource is used for task triggers. |
| Connect AI agents assistant | 1 |
| Connect AI agents knowledge base | 10 |
| Cases domain | 1 |
| Connect AI agents knowledge base | 10 |
## Amazon Connect Contact Lens feature specifications
| Item | Feature Specification |
| --- | --- |
| Custom vocabularies | 20 |
| Contact Lens rules for post-call | 500 |
| Contact Lens rules for post-chat | 500 |
| Contact Lens rules for real-time | 500 |
## Evaluation forms feature specifications
| Item | Feature Specification |
| --- | --- |
| Maximum number of evaluations per agent per month | 3000 |
| Maximum number of evaluation forms per instance Historical versions are not counted, only form names are counted. | 400 |
| Maximum number of versions per form | 50 |
| Maximum number of sections per form | 100 |
| Maximum number of questions per form | 100 |
| Maximum nesting level of sections | 2 (sections can have sub-sections, but sub-sections cannot have sub-sub-sections) |
| Definition title length | 1-128 characters |
| Section title length | 1-128 characters |
| Question title length | 1-350 characters |
| Section instructions length | up to 1024 characters |
| Number of answer options for single select questions | 2-256 answer options |
| Answer option text length for single select questions | 1-128 characters |
## Amazon Connect Rules feature specifications
The following table lists feature specifications for Amazon Connect Rules.
| Item | Feature Specification |
| --- | --- |
| Conditions in a rule | 20 |
| Rules with Natural Language condition for OnPostCallAnalysisAvailable event source | 15 |
| Rules with Natural Language condition for OnPostChatAnalysisAvailable event source | 15 |
| Rules for OnPostCallAnalysisAvailable event source | 500 |
| Rules for OnPostChatAnalysisAvailable event source | 500 |
| Rules for OnRealTimeCallAnalysisAvailable event source | 500 |
| Rules for OnRealTimeChatAnalysisAvailable event source | 500 |
| Rules for OnZendeskTicketCreate event source | 500 |
| Rules for OnZendeskTicketStatus event source | 500 |
| Rules for OnSalesforceCaseCreate event source | 500 |
| Rules for OnContactEvaluationSubmit event source | 500 |
| Rules for OnCaseUpdate event source | 500 |
| Rules for OnCaseCreate event source | 500 |
| Rules for OnMetricDataUpdate event source | 100 |
| Condition type | Number of entries or selections | Post-call | Post-chat | Real-time |
| --- | --- | --- | --- | --- |
| Evaluation - Form score | 20 | N/A | N/A | N/A |
| Evaluation- Section score | 20 | N/A | N/A | N/A |
| Evaluation- Question score | 20 | N/A | N/A | N/A |
| Evaluation - Results available | 20 | N/A | N/A | N/A |
| Words or phrases - Exact match | 100 | Yes | Yes | Yes |
| Words or phrases - Semantic match | 4 | Yes | Yes | Not supported |
| Words or phrases - Pattern match | 100 | Yes | Yes | Yes |
| Natural Language - Semantic match | 1 | Yes | Yes | No |
| Queue condition | 100 | Yes | Yes | Yes |
| Agent condition | 100 | Yes | Yes | Yes |
| Custom attributes | 5 | Yes | Yes | Yes |
| Sentiment - Time period | 5 | Yes | Yes | Yes |
| Sentiment - Entire contact | 5 | Yes | Yes | Not supported |
| Interruptions | 5 | Yes | Yes | Not supported |
| Response time | 4 hours | Not supported | Yes | Not supported |
| Non-talk time | 5 hours | Yes | Not supported | Not supported |
# Countries that call centers using Amazon Connect can call by default
The Region where your instance is created determines which countries you can call by default.
**Note**
Amazon Connect country allowlisting supports a default deny model; unless you have specifically been allowed to call countries you will be blocked when attempting to call.
For a list of all the countries available for outbound calling, see [Amazon Connect pricing](https://aws.amazon.com/connect/pricing/).
If you already have an instance, the countries that you are allowed to call may be different that those listed in the following sections because we have changed the service quotas over time.
**UK** mobile numbers with the following prefix may not be allowed by default:
+ \$1447
If you cannot dial these UK mobile numbers, you must submit a service quota increase request.
**Japan** mobile numbers with the following prefixes may not be allowed by default:
+ \$18170, 8180, and 8190
If you can not dial these Japan mobile numbers, you must submit a service quota increase request.
## How to allow calling to additional countries
Use the following instructions to allow calling to additional countries, or to limit the countries that you can call from.
1. Choose [Account and billing](https://console.aws.amazon.com/support/home#/case/create?issueType=customer-service&serviceCode=service-connect-number-management&categoryCode=country-allowlisting-for-outbound-calls) to go to the pre-populated form in the Support console. You must be signed in to your AWS account to access the form.
1. For **Service**, *Connect (Number Management)* should be selected.
1. For **Category**, *Country Allowlisting for Outbound Calls* should be selected.
1. Select the required severity.
1. Choose **Next step: Additional information**
1. On the **Additional information** page:
1. Enter the subject.
1. Under **Description**, list which countries you want to allow calling to, or limit calling from.
1. Choose **Next step: Solve now or contact us**.
1. On the **Solve now or contact us** page:
1. Choose the **Contact us** tab and select your **Preferred contact language** and your preferred contact method.
1. Choose **Submit**.
1. The Amazon Connect team will review your ticket and get back to you.
## Instances created in US East, US West, Canada (Central) and AWS GovCloud (US-West)
You can call the following countries by default:
+ United States
+ Canada
+ Mexico
+ Puerto Rico
+ United Kingdom
## Instances created in Africa (Cape Town)
You can call the following countries by default:
+ South Africa
+ United Kingdom
+ United States
## Instances created in Asia Pacific (Seoul)
You can call the following countries by default:
+ South Korea
+ United Kingdom
+ United States
## Instances created in Asia Pacific (Singapore)
You can call the following countries by default:
+ Singapore
+ Australia
+ Hong Kong
+ United States
+ United Kingdom
## Instances created in Asia Pacific (Sydney)
You can call the following countries by default:
+ Australia
+ New Zealand
+ United States
## Instances created in Asia Pacific (Tokyo)
You can call the following countries by default:
+ Japan
+ Vietnam
+ United States
## Instances created in EU (Frankfurt) and EU (London)
You can call the following countries by default:
+ United Kingdom
+ Italy
+ France
+ Ireland
+ United States
## 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](https://docs.aws.amazon.com/connect/latest/APIReference/welcome.html), all operations have a `RateLimit` of 2 requests per second and a `BurstLimit` of 5 requests per second, **with the following exceptions**:
| Operation | Rate limit | Burst limit |
| --- | --- | --- |
| For all [Evaluations actions](https://docs.aws.amazon.com/connect/latest/APIReference/evaluation-api.html) | 1 request per second | |
| \$1[GetMetricData ](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetMetricData.html) | 5 | 8 |
| \$1[GetMetricDataV2 ](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetMetricDataV2.html) | 10 | 10 |
| \$1[GetCurrentMetricData](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetCurrentMetricData.html) | 5 | 8 |
| [SearchContacts](https://docs.aws.amazon.com/connect/latest/APIReference/API_SearchContacts.html) | .5 | 1 |
| [StartContactStreaming](https://docs.aws.amazon.com/connect/latest/APIReference/API_StartContactStreaming.html) | 5 | 8 |
| [StartChatContact](https://docs.aws.amazon.com/connect/latest/APIReference/API_StartChatContact.html) | 5 | 8 |
| [CreatePersistentContactAssociation](https://docs.aws.amazon.com/connect/latest/APIReference/API_CreatePersistentContactAssociation.html) | 5 | 8 |
| [UpdateParticipantRoleConfig](https://docs.aws.amazon.com/connect/latest/APIReference/API_UpdateParticipantRoleConfig.html) | 5 | 8 |
| [StopContactStreaming](https://docs.aws.amazon.com/connect/latest/APIReference/API_StopContactStreaming.html) | 5 | 8 |
| [CreateParticipant](https://docs.aws.amazon.com/connect/latest/APIReference/API_CreateParticipant.html) | 5 | 8 |
| [GetContactAttributes](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetContactAttributes.html) | 10 | 15 |
| [UpdateContactAttributes ](https://docs.aws.amazon.com/connect/latest/APIReference/API_UpdateContactAttributes .html) | 10 | 15 |
| [DescribeContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_DescribeContact .html) | 10 | 15 |
| [StopContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_StopContact .html) | 10 | 15 |
| [UpdateContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_UpdateContact .html) | 10 | 15 |
| [ListContactReferences ](https://docs.aws.amazon.com/connect/latest/APIReference/API_ListContactReferences .html) | 10 | 15 |
| [BatchPutContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_BatchPutContact .html) | 10 | 15 |
| [TagContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_TagContact .html) | 20 | 25 |
| [UntagContact ](https://docs.aws.amazon.com/connect/latest/APIReference/API_UntagContact .html) | 20 | 25 |
| [UpdateContactRoutingData](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetContactAttributes.html) | 20 | 20 |
| [SendChatIntegrationEvent](https://docs.aws.amazon.com/connect/latest/APIReference/API_SendChatIntegrationEvent) | 17 | 26 |
| SendIntegrationEvent (this is a separate permission-only API used by AWS End User Messaging Social) | 10 | 15 |
| [CreateIntegrationAssociation](https://docs.aws.amazon.com/connect/latest/APIReference/API_CreateIntegrationAssociation.html), [DeleteIntegrationAssociation](https://docs.aws.amazon.com/connect/latest/APIReference/API_DeleteIntegrationAssociation.html) | 2 1 for the SES\$1IDENTITY IntegrationType field | 5 |
| [ListIntegrationAssociations](https://docs.aws.amazon.com/connect/latest/APIReference/API_ListIntegrationAssociations.html) | 25 | 50 |
**Important**
\$1 [GetCurrentMetricData](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetCurrentMetricData.html), [GetMetricDataV2](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetMetricDataV2.html), and [GetCurrentUserData](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetCurrentUserData.html) may incorrectly display 200 as their throttling quota in the Service Quotas console. We recommend using the default quotas specified here, or opening a ticket.
### Amazon Connect Cases API throttling quotas
| API | Default Rate Limit | Default Burst Limit | Adjustable |
| --- | --- | --- | --- |
| CreateCase, SearchCases, ListTemplates, ListLayouts, CreateRelatedItems, SearchRelatedItems, ListCaseRules, ListTagsForResource, TagResource, UntagResource, GetCaseAuditEvents, GetCaseEventConfiguration, PutCaseEventConfiguration | 2 | 10 | yes |
| GetCase | 4 | 10 | yes |
| UpdateCase, ListCasesForContact | 2 | 2 | yes |
| CreateField, ListFields, UpdateField, BatchPutFieldOptions, CreateDomain, GetDomain, ListDomains, CreateTemplate, UpdateTemplate, CreateLayout, UpdateLayout, CreateCaseRule, UpdateCaseRule, DeleteCaseRules | 2 | 5 | yes |
| BatchGetField, BatchGetCaseRule | 8 | 25 | yes |
| ListFieldOptions | 6 | 16 | yes |
| GetTemplate, GetLayout | 6 | 20 | yes |
### 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](https://docs.aws.amazon.com/contact-lens/latest/APIReference/Welcome.html), the number of requests per second is limited to the following:
+ [ListRealtimeContactAnalysisSegments](https://docs.aws.amazon.com/contact-lens/latest/APIReference/ListRealtimeContactAnalysisSegments.html): a `RateLimit` of 1 request per second, and a `BurstLimit` of 2 requests per second.
+ [ListRealtimeContactAnalysisSegmentsV2](https://docs.aws.amazon.com/connect/latest/APIReference/API_ListRealtimeContactAnalysisSegmentsV2.html): a `RateLimit` of 2 request per second, and a `BurstLimit` of 5 requests per second.
### Amazon Connect Customer Profiles API throttling quotas
| API | Default TPS throttling limits |
| --- | --- |
| ListDomains | 5 |
| GetDomain | 5 |
| CreateDomain | 1 |
| UpdateDomain | 1 |
| DeleteDomain | 1 |
| ListProfileObjectTypes | 5 |
| GetProfileObjectType | 10 |
| PutProfileObjectType | 1 |
| DeleteProfileObjectType | 1 |
| ListProfileObjectTypeTemplates | 5 |
| GetProfileObjectTypeTemplate | 5 |
| ListIntegrations | 5 |
| GetIntegration | 5 |
| PutIntegration | 1 |
| DeleteIntegration | 1 |
| ListIdentityResolutionJobs | 5 |
| GetIdentityResolutionJob | 5 |
| GetAutoMergingPreview | 1 |
| CreateEventStream | 1 |
| ListEventStreams | 5 |
| DeleteEventStream | 5 |
| GetEventStream | 5 |
| CreateCalculatedAttributeDefinition | 1 |
| GetCalculatedAttributeDefinition | 5 |
| UpdateCalculatedAttributeDefinition | 1 |
| DeleteCalculatedAttributeDefinition | 5 |
| ListCalculatedAttributeDefinitions | 5 |
| CreateIntegrationWorkflow | 5 |
| DeleteWorkflow | 5 |
| ListWorkflows | 5 |
| GetWorkflow | 5 |
| GetWorkflowSteps | 5 |
| SearchProfiles | 100 |
| ListProfileObjects | 100 |
| GetMatches | 100 |
| GetSimilarProfiles | 100 |
| ListRuleBasedMatches | 5 |
| GetCalculatedAttributeForProfile | 100 |
| ListCalculatedAttributesForProfile | 100 |
| CreateProfile | 100 |
| UpdateProfile | 100 |
| PutProfileObject | 100 |
| AddProfileKey | 100 |
| DeleteProfile | 100 |
| DeleteProfileObject | 100 |
| DeleteProfileKey | 100 |
| MergeProfiles | 100 |
| TagResource | 5 |
| UntagResource | 5 |
| ListTagsForResource | 5 |
| ListAccountIntegrations | 100 |
### Amazon Connect Outbound Campaigns Service API throttling quotas
Outbound campaigns 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 share a throttle bucket.
+ If multiple requests are sent from different instances from the same account, they also share a throttle bucket.
When you use the [Amazon Connect Outbound Campaigns Service](https://docs.aws.amazon.com/connect/latest/APIReference/Welcome.html#Welcome_Amazon_Connect_Outbound_Campaigns) API, the number of requests per second is limited to the following:
+ The following APIs have a `RateLimit` of 1 request per second, and a `BurstLimit` of 2 requests per second:
+ [CreateCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_CreateCampaign.html)
+ [DeleteCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_DeleteCampaign.html)
+ [PauseCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_PauseCampaign.html)
+ [ResumeCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_ResumeCampaign.html)
+ [StartCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_StartCampaign.html)
+ [StopCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_StopCampaign.html)
+ [UpdateCampaignDialerConfig](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_UpdateCampaignDialerConfig.html)
+ [UpdateCampaignName](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_UpdateCampaignName.html)
+ [UpdateCampaignOutboundCallConfig](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_UpdateCampaignOutboundCallConfig.html)
+ [ListTagsForResource](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_ListTagsForResource.html)
+ [TagResource](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_TagResource.html)
+ [UntagResource](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_UntagResource.html)
+ The following APIs have a `RateLimit` of 5 requests per second, and a `BurstLimit` of 10 requests per second:
+ [GetCampaignState](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_GetCampaignState.html)
+ [GetCampaignStateBatch](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_GetCampaignStateBatch.html)
+ [ListCampaigns](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_ListCampaigns.html)
+ The following APIs have a RateLimit of 10 requests per second, and a BurstLimit of 10 requests per second:
+ [PutDialRequestBatch](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-outbound-campaigns_PutDialRequestBatch.html)
+ [PutOutboundRequestBatch](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-outbound-campaigns-v2_PutOutboundRequestBatch.html)
+ [PutProfileOutboundRequestBatch](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-outbound-campaigns-v2_PutProfileOutboundRequestBatch.html)
+ For [DescribeCampaign](https://docs.aws.amazon.com/connect-outbound/latest/APIReference/API_DescribeCampaign.html) API, a `RateLimit` of 25 requests per second, and a `BurstLimit` of 35 requests per second.
+ For all other operations, a `RateLimit` of 2 requests per second, and a `BurstLimit` of 5 requests per second.
### 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](https://docs.aws.amazon.com/connect-participant/latest/APIReference/Welcome.html), the number of requests per second is limited to the following:
+ [CompleteAttachmentUpload](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_CompleteAttachmentUpload.html): a `RateLimit` of 2 requests per second, and a `BurstLimit` of 5 requests per second.
+ [CreateParticipantConnection](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_CreateParticipantConnection.html): a `RateLimit` of 6 requests per second, and a `BurstLimit` of 9 requests per second.
+ [DisconnectParticipant](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_DisconnectParticipant.html): a `RateLimit` of 3 requests per second, and a `BurstLimit` of 5 requests per second.
+ [GetAttachment](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_GetAttachment.html): a `RateLimit` of 8 requests per second, and a `BurstLimit` of 12 requests per second.
+ [GetTranscript](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_GetTranscript.html): a `RateLimit` of 8 requests per second, and a `BurstLimit` of 12 requests per second.
+ [SendEvent](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_SendEvent.html) and [SendMessage](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_SendMessage.html): a `RateLimit` of 10 requests per second, and a `BurstLimit` of 15 requests per second.
+ [StartAttachmentUpload](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_StartAttachmentUpload.html): a `RateLimit` of 2 requests per second, and a `BurstLimit` of 5 requests per second.
### 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 |
| TagResource, UnTagResource, ListTagsForResource | 2 |
### Connect AI agents Service API throttling quotas
| API | Default TPS throttling limits |
| --- | --- |
| DeleteMessageTemplate | 10 |
| DeleteMessageTemplateAttachment | 10 |
| GetMessageTemplate | 10 |
| ListMessageTemplates | 10 |
| ListMessageTemplateVersions | 10 |
| RenderMessageTemplate | 10 |
| SearchMessageTemplates | 10 |
| ActivateMessageTemplate | 3 |
| CreateMessageTemplate | 3 |
| CreateMessageTemplateAttachment | 3 |
| CreateMessageTemplateVersion | 3 |
| UpdateMessageTemplate | 3 |
| UpdateMessageTemplateMetadata | 3 |
| DeactivateMessageTemplate | 3 |