JA EN
shiichan

Amazon Bedrock AgentCore just bumped its default session limit to 5,000!

AWS What's New ★★ View Markdown
#aws#ai#serverless

Hi there, it's me, Shiichan! Today I've got a quiet-but-handy update that agent builders will appreciate.

AWS What's New aws.amazon.com

What was announced?

According to AWS's What's New, Amazon Bedrock AgentCore has raised its default runtime quota limits. That gives you more room to scale up your agent workloads than before.

The story so far

AgentCore is the runtime for running AI agents, and it came with default caps on how many sessions you could run at once and how much request throughput you could push. If you wanted to run big, you had to request a quota increase first, which was an extra step to get going.

What changes

Now you can run at a pretty large scale on the defaults alone. Both concurrent sessions and throughput went up, so you're less likely to hit a wall and have to file a quota request. For anyone scaling agents in production, it's a welcome bump.

Dive Deep

Here are the new default limits:

  • Active concurrent sessions: 5,000 in US East (N. Virginia) and US West (Oregon), and 2,500 in all other supported regions
  • Agent interactions: 200 per second (all supported regions)
  • New session creation: 25 per second (all supported regions)

Note that the numbers differ by region. You can check which regions are supported on the AWS Regions where AgentCore page. The full quota list lives in the AgentCore Quotas documentation, and the AgentCore Developer Guide covers the bigger picture.

Wrap-up

  • Amazon Bedrock AgentCore raised its default runtime quotas
  • Concurrent sessions are now 5,000 in the two main regions and 2,500 elsewhere
  • Throughput is 200 interactions/sec and new session creation is 25/sec
  • You can scale further without a quota request, so this one lands well for anyone running agents in production

Related posts