AWS bedrock-agentcore documentation change
Summary
Increased default service quotas: active sessions from 1k/500 to 5k/2.5k, API rate from 25 to 200 TPS, session creation from 100 to 400 TPM
Security assessment
Scalability improvements don't address security vulnerabilities or introduce security features
Diff
diff --git a/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md b/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md index 9d0faba30..066f98f04 100644 --- a//bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md +++ b//bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md @@ -66 +66 @@ 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 Service Quotas +Active session workloads per account | 5,000 in US East (N. Virginia) and US West (Oregon), and 2,500 in other AWS Regions. | Yes | Can be increased via Service Quotas @@ -98 +98 @@ Limit | Value | Adjustable | Notes -InvokeAgentRuntime API rate, per agent, per account | 25 TPS | Yes | Transactions per second +InvokeAgentRuntime API rate, per agent, per account | 200 TPS | Yes | Transactions per second @@ -102 +102 @@ InvokeAgentRuntimeCommandShell API rate, per agent, per account | 25 TPS | Yes -New sessions created rate, per endpoint (container deployment) | 100 TPM | Yes | Transactions per minute +New sessions created rate, per endpoint (container deployment) | 400 TPM | Yes | Transactions per minute