Amazon Bedrock AgentCore is in preview release and is subject to change.
Quotas for Amazon Bedrock AgentCore
Your AWS account has default quotas, formerly referred to as limits, for each AWS service. Unless otherwise noted, each quota is Region-specific. You can request increases for some quotas, and other quotas cannot be increased.
To view the quotas for AgentCore, open the Service Quotas console
To request a quota increase, contact AWS support.
Topics
AgentCore Runtime Service Quotas
When working with AgentCore Runtime, you need to be aware of the service limits that apply to your account. These limits help ensure service stability and availability for all users.
Resource allocation limits
The following table describes the resource allocation limits for AgentCore Runtime:
| Limit | Default Value | Adjustable | Notes |
|---|---|---|---|
| Active Session workloads per account | 500 in US East (N. Virginia) and Asia Pacific (Sydney), and 250 in Europe (Frankfurt) and US West (Oregon). | Yes | Can be increased via support ticket |
| Total agents per account | 1000 | Yes | Can be increased via support ticket |
| Versions per agent | 1000 | Yes | Inactive versions deleted after 45 days |
| Endpoints (aliases) per agent | 10 | Yes | Can be increased via support ticket |
| Maximum size for a Docker image in an AgentCore Runtime | 1 GB | No | |
| Hardware configuration per session | 2vCPU/8GB | No | The maximum memory/CPU usage and configuration per account |
Invocation limits
The following table describes the invocation limits for AgentCore Runtime:
| Limit | Value | Adjustable | Notes |
|---|---|---|---|
| Request timeout | 15 minutes | No | Maximum time for synchronous requests |
| Max payload size | 100 MB | No | Maximum size for request/response payloads |
| Streaming max duration | 60 mins | No | Maximum time for streaming connections |
| Async job max duration | 8 hours | No | Maximum execution time for asynchronous jobs |
| Invocations per second | 100 per endpoint | Yes | Rate limit for API calls |
Lifetime session lifecycle parameters
The following table describes the lifetime session lifecycle parameters for AgentCore Runtime:
| Phase | Timeout | Adjustable | Notes |
|---|---|---|---|
| Session Termination | 15 minutes of inactivity | No | Execution Environment is terminated. Customer will get a new Execution environment for the Session |
| Max Session Duration | 8 hrs | No |
AgentCore Memory Service Quotas
| Limit | Value |
|---|---|
| Number of AgentCore Memory resources per AWS Region in an AWS account. | 50 |
| Max Number of memory strategies per AgentCore Memory instance | 6 |
| Minimum EventExpirationDuration days in CreateEvent operation | 7 |
| Maximum EventExpirationDuration days in CreateEvent operation | 365 |
| Prompt Size (AppendToPrompt) for Custom Memory Strategy (Extraction/Consolidation) | 30 KB |
| Max Number of messages per CreateEvent operation | 100 |
| Max message size in CreateEvent operation | 9 KB |
| Max event size in CreateEvent operation | 10 MB |
| Max TPS for CreateEvent (per account) | 5 |
| Max TPS for CreateEvent (per combination of account, actor, session) | 0.25 |
| Max TPS for RetrieveMemoryRecords (per account) | 5 |
| Max TPS for all other AgentCore Memory APIs | 20 |
AgentCore Identity Service Quotas
When working with AgentCore Runtime, you need to be aware of the service limits that apply to your account. These limits help ensure service stability and availability for all users.
| Limit | Value | Adjustable | Notes |
|---|---|---|---|
| API keys stored per AWS account per AWS Region | 50 | Yes | Can be increased via Support ticket |
| OAuth client credentials stored per AWS account per AWS Region | 50 | Yes | Can be increased via Support ticket |
AgentCore Gateway Service Quotas
This section provides information about Amazon Bedrock AgentCore Gateway endpoints and service limits.
Endpoints
Amazon Bedrock AgentCore Gateway provides AWS Region-specific endpoints for management operations and runtime access.
The Amazon Bedrock AgentCore Gateway control plane endpoints use the following format, where you can replace <region>
with any of the AWS Regions listed in AWS Regions.
bedrock-agentcore-control.<region>.amazonaws.com
The AgentCore Gateway URLs for runtime access have the following format:
https://{gateway-Id}.gateway.bedrock-agentcore.{Region}.amazonaws.com
Where:
-
{gateway-Id} is the unique identifier for your gateway
-
{Region} is the AWS Region where your gateway is deployed
Gateway ARNs have the following format:
arn:${Partition}:bedrock-agentcore:${Region}:${Account}:gateway/${gateway-Id}
The AgentCore service principal is: bedrock-agentcore.amazonaws.com
Service quotas
Amazon Bedrock AgentCore Gateway has the following service quotas. You can request increases for some quotas using the Service Quotas console.
| Quota | Default value | Adjustable | Notes |
|---|---|---|---|
| Number of gateways per account | 100 | Yes | |
| Number of targets per gateway | 10 | Yes | |
| Number of tools per target | 200 | Yes | |
| Timeout for a gateway invocation | 55 seconds | Yes | Aligns with Lambda function timeout |
| Maximum inline schema size | 1 MB | Yes | |
| Maximum S3 payload schema size | 2 MB | Yes | |
| Tool name character limit | 256 characters | Yes | |
| CreateGateway API rate | 5 TPM | Yes | Transactions per minute |
| UpdateGateway API rate | 5 TPM | Yes | Transactions per minute |
| GetGateway API rate | 5 TPS | Yes | Transactions per second |
| ListGateways API rate | 5 TPS | Yes | Transactions per second |
| DeleteGateway API rate | 5 TPM | Yes | Transactions per minute |
| CreateGatewayTarget API rate | 5 TPM | Yes | Transactions per minute |
| UpdateGatewayTarget API rate | 5 TPM | Yes | Transactions per minute |
| GetGatewayTarget API rate | 5 TPS | Yes | Transactions per second |
| ListGatewayTargets API rate | 5 TPS | Yes | Transactions per second |
| DeleteGatewayTarget API rate | 5 TPM | Yes | Transactions per minute |
| CallTool/ListTool/SearchTool API rate at gateway level | 5 TPS | Yes | Transactions per second |
| CallTool/ListTool/SearchTool API rate at account level | 5 TPS | Yes | Transactions per second |
| Maximum CallTool/ListTool/SearchTool payload size | 6 MB | Yes |
For more information about service quotas and how to request increases, see Requesting a quota increase in the Service Quotas User Guide.
AgentCore Browser Service Quotas
The Browser tool has the following service quotas and considerations that apply to your account.
| Quota | Default Value | Adjustable | Notes |
|---|---|---|---|
| Session duration | 15 minutes | Yes | Can be extended up to 8 hours |
| Concurrent active sessions per account | 500 | Yes | Can be increased via support ticket |
| Total Browser tool configurations per account | 100 | Yes | Can be increased via support ticket |
| CDP stream and live view stream per session | 1 each | No | Allows a single agent and end user to interact with the browser |
| Hardware configuration per session | 1vCPU/4GB | No | The maximum memory/CPU usage and configuration per account |
AgentCore Code Interpreter Service Quotas
The Code Interpreter tool has the following service quotas and considerations that apply to your account.
| Quota | Default Value | Adjustable | Notes |
|---|---|---|---|
| Execution time | 15 minutes | Yes | Can be extended up to 8 hours |
| Concurrent active sessions per account | 500 | Yes | Can be increased via support ticket |
| Total Code Interpreter tool configurations per account | 100 | Yes | Can be increased via support ticket |
| Hardware configuration per session | 2vCPU/8GB | No | The maximum memory/CPU usage and configuration per account |
