AWS
AWS Upgrades Bedrock AgentCore for Faster AI Agent Deployment
AWS enhances Amazon Bedrock AgentCore with increased compute power and memory efficiency to help enterprises scale AI agents quickly and affordably.
- Read time
- 4 min read
- Word count
- 971 words
- Date
- Nov 12, 2026
- Key Takeaways:
- The upgraded runtime supports up to eight virtual CPUs and 32GB of memory per session.
- New startup times are clocked at under two seconds regardless of the container image size.
- Memory consumption for multi-turn agents can drop by 68 percent through idle scaling.
- The service update is currently available across 19 different global AWS regions.
🌟 Non-members read here
AWS announced a major upgrade to the runtime layer of Amazon Bedrock AgentCore on Thursday. The update introduces significantly higher compute capacity and improved memory efficiency to streamline the deployment of AI agents. These changes focus on helping businesses scale their artificial intelligence operations more effectively while managing operational costs.
Enhanced Performance and Infrastructure Capabilities
The latest improvements to the Bedrock AgentCore runtime provide developers with substantially more power for intensive tasks. Each session now supports up to eight virtual CPUs and 32GB of memory, which is four times the capacity of the previous version. This increase allows for the execution of demanding workloads that require significant resources.
Developers can now work with container images as large as 10GB. This change is particularly beneficial for complex agent tasks such as compiling massive codebases or running local model inference. Previously, these types of operations often exceeded the limits of the isolated environment. The new hardware specifications ensure that these processes remain within a secure boundary during execution.
Speed is another critical factor in this update. Startup times for isolated sessions are now under two seconds. This is a dramatic improvement over previous versions, where initialization could take nearly a minute. Faster startups mean that developers do not have to maintain expensive pools of pre-provisioned capacity to avoid latency.
Storage and Data Isolation
AWS has also improved how agents handle data during execution. Developers can now use FUSE support to dynamically mount and save work directly to filesystems like Amazon S3. This eliminates the need for teams to build custom tools to move credentials or files between execution environments and external storage.
This integration simplifies the workflow for long-running tasks. By allowing agents to write to persistent storage, the system ensures that data is preserved even if a session ends. It creates a more seamless experience for managing tool outputs and credentials without compromising the security of the execution layer.
Impact on Complex Workloads
Industry analysts note that these updates resolve many pain points for developers building sophisticated agents. Coding agents and browser-driven workflows often outgrew earlier session sizes. With the expanded vCPU and memory limits, these agents can now load full web pages or run small models without being forced outside the secure environment.
Efficiency and Cost Management Strategies
A primary focus of this update is helping Chief Information Officers manage the financial burden of running AI at scale. AWS introduced memory reclamation features that allow the runtime to recover unused resources within minutes of an agent releasing them. This is especially helpful for agents that spend time waiting for tool calls or human responses.
For multi-turn agents that have natural pauses between user interactions, these updates can reduce memory consumption per session by as much as 68 percent. Idle agents can now scale to zero, which means businesses are not paying for compute power when an agent is inactive. This resource efficiency makes it more feasible to run hundreds of concurrent sessions across an enterprise.
Baseline Pricing Models
To support agents that must remain available at all times, AWS has introduced a baseline pricing structure. This model establishes a minimum memory allocation for each session. However, it allows workloads to burst up to four times that baseline when the agent encounters a temporary spike in demand.
This approach provides a level of cost predictability that was previously difficult to achieve. Organizations can maintain always-on sessions without paying for peak capacity upfront. They retain the flexibility to scale instantly when the workload increases, balancing the need for availability with the desire for cost control.
Accelerating Enterprise Adoption
Lowering the barriers to resource management helps speed up the rollout of AI across various business functions. When developers do not have to engineer complex logic for shutting down or restarting sessions, they can focus on the core functionality of the AI. This efficiency enables faster deployment cycles for agents handling customer service, internal logistics, or data analysis.
Risks and Implementation Considerations
While the new features offer clear advantages, experts suggest that organizations should be aware of potential trade-offs. Scaling agents to zero is a powerful cost-saving tool, but it can introduce latency when an agent needs to resume a task. This delay might not be acceptable for applications that require immediate real-time responses.
There are also governance concerns regarding long-running agents. Because it is now cheaper to keep agents idle, companies might leave many agents active indefinitely. These agents often retain permissions and access to sensitive enterprise data. Regular audits of agent access are necessary to ensure that security protocols remain strict as the number of agents grows.
Testing and Stability
Developers must also focus on the technical details of session resumption. When an agent wakes up from an idle state, it must accurately recognize its last completed action. If the resumption logic is flawed, an agent might repeat a sensitive transaction, such as a financial payment or a production database change.
Ensuring that credentials have not expired and that files are still available upon restart is a critical part of the testing phase. Saving resources is only beneficial if the agent remains reliable throughout its lifecycle. Businesses must verify that their logic accounts for these transitions to avoid operational errors.
Strategic Deployment Planning
The committed baseline pricing model requires careful estimation of memory needs. If a CIO sets the baseline too high, the organization pays for wasted capacity. If it is set too low, frequent bursts can lead to unpredictable billing. Analysts suggest that this model works best for workloads with stable and understood resource patterns.
The updated AgentCore runtime is now available in 19 AWS regions globally. This includes major hubs in North America, Europe, South America, and Asia-Pacific. Companies in regions such as Ireland, Tokyo, and N. Virginia can immediately begin utilizing these enhanced capabilities to build more robust AI solutions.
References
- Attribution: Valentin Podkamennyi, VP Insights
- Citations: AWS boosts Bedrock AgentCore runtime compute capacity to speed up AI agent development, Info World
- Mentions: Amazon Bedrock, Amazon S3
- About: Amazon Web Services