AWS bedrock-agentcore documentation change
Summary
Updated quota increase instructions from support tickets to Service Quotas console and added links to quota increase documentation
Security assessment
The changes involve procedural updates for requesting service quota increases but do not address security vulnerabilities or document security features.
Diff
diff --git a/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md b/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md index bdc5391fb..de3ea9cb2 100644 --- a//bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md +++ b//bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md @@ -40 +40 @@ When working with AgentCore Runtime, you need to be aware of the service limits -The following table describes the resource allocation limits for AgentCore Runtime: +The following table describes the resource allocation limits for AgentCore Runtime. You can request increases for some quotas using the Service Quotas console. @@ -44,4 +44,4 @@ Resource allocation limits Limit | Default Value | Adjustable | Notes -Active session workloads per account | 1,000 in US East (N. Virginia) and US West (Oregon), and 500 in other AWS Regions. | Yes | Can be increased via support ticket -Total agents per account | 1,000 | Yes | Can be increased via support ticket -Versions per agent | 1,000 | Yes | Inactive versions deleted after 45 days -Endpoints (aliases) per agent | 10 | Yes | Can be increased via support ticket +Active session workloads per account | 1,000 in US East (N. Virginia) and US West (Oregon), and 500 in other AWS Regions. | Yes | Can be increased via Service Quotas +Total agents per account | 1,000 | Yes | Can be increased via Service Quotas +Versions per agent | 1,000 | Yes | Can be increased via Service Quotas +Endpoints (aliases) per agent | 10 | Yes | Can be increased via Service Quotas @@ -52,0 +53,2 @@ Maximum hardware allocation per session | 2vCPU/8GB | No | The maximum memory/CP +For more information about service quotas and how to request increases, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_. + @@ -55 +57 @@ Maximum hardware allocation per session | 2vCPU/8GB | No | The maximum memory/CP -The following table describes the invocation limits for AgentCore Runtime: +The following table describes the invocation limits for AgentCore Runtime. You can request increases for some quotas using the Service Quotas console. @@ -66,0 +69,2 @@ WebSocket frame size | 32 KB | No | Maximum size for individual WebSocket frames +For more information about service quotas and how to request increases, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_. + @@ -69 +73 @@ WebSocket frame size | 32 KB | No | Maximum size for individual WebSocket frames -The following table describes the rate limits for AgentCore Runtime after which you will be throttled: +The following table describes the rate limits for AgentCore Runtime after which you will be throttled. You can request increases for some quotas using the Service Quotas console. @@ -90,0 +95,2 @@ ListAgentRuntimeVersions API rate | 5 TPS | Yes | Transactions per second +For more information about service quotas and how to request increases, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_. +