AWS bedrock-agentcore documentation change
Summary
Added release note about increased default service quotas for AgentCore Runtime
Security assessment
Notes quota increases without security implications or new security features
Diff
diff --git a/bedrock-agentcore/latest/devguide/release-notes.md b/bedrock-agentcore/latest/devguide/release-notes.md index dfe790c0f..451e437f2 100644 --- a//bedrock-agentcore/latest/devguide/release-notes.md +++ b//bedrock-agentcore/latest/devguide/release-notes.md @@ -14,0 +15,4 @@ We recommend subscribing to the RSS feed so updates to these notes are delivered +### Runtime: Increased Default Service Quotas + +AgentCore Runtime default service quotas have been increased to support higher-scale workloads. Active session workloads per account are now 5,000 in US East (N. Virginia) and US West (Oregon), and 2,500 in other AWS Regions (previously 1,000 and 500 respectively). The InvokeAgentRuntime API rate has increased from 25 TPS to 200 TPS per agent, per account. The new session creation rate for container deployments has increased from 100 TPM to 400 TPM per endpoint. The new session creation rate for direct code deployments remains at 25 TPS per endpoint. These updated defaults apply automatically to all accounts. See [Service quotas and limits](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.html). +