Bedrock AgentCore SDK
Deploy your local AI agent to Bedrock AgentCore with zero infrastructure
Documentation ◆ Samples ◆ Discord ◆ Boto3 Python SDK ◆ Runtime Python SDK
Overview
Amazon Bedrock AgentCore enables you to deploy and operate highly effective agents securely, at scale using any framework and model. With Amazon Bedrock AgentCore, developers can accelerate AI agents into production with the scale, reliability, and security, critical to real-world deployment. AgentCore provides tools and capabilities to make agents more effective and capable, purpose-built infrastructure to securely scale agents, and controls to operate trustworthy agents. Amazon Bedrock AgentCore services are composable and work with popular open-source frameworks and any model, so you don’t have to choose between open-source flexibility and enterprise-grade security and reliability.
🚀 From Local Development to Bedrock AgentCore
from bedrock_agentcore import BedrockAgentCoreApp
app = BedrockAgentCoreApp()
from strands import Agent # or bring your agent.
@app.entrypoint
async def handler(request):
prompt = request.get("prompt")
agent = Agent()
async for event in agent.stream_async(prompt):
yield (event)
app.run()
What you get with Bedrock AgentCore:
- ✅ Keep your agent logic - Works with Strands, LangGraph, CrewAI, Autogen, or custom frameworks
- ✅ Zero infrastructure management - No servers, containers, or scaling concerns
- ✅ Enterprise-grade platform - Built-in auth, memory, observability, security
- ✅ Production-ready deployment - Reliable, scalable, compliant hosting
Amazon Bedrock AgentCore services
- 🚀 Runtime - Secure and session isolated compute: Get started
- 🧠 Memory - Persistent knowledge across sessions: Get started
- 🔗 Gateway - Transform APIs into MCP tools: Get started
- 💻 Code Interpreter - Secure sandboxed execution: Get started
- 🌐 Browser - Cloud-based web automation: Get started
- 📊 Observability - OpenTelemetry tracing: Get started
- 🔐 Identity - AWS & third-party auth: Get started
AG-UI Protocol Support
Deploy agents using the AG-UI protocol with zero boilerplate. A single entrypoint handler is served over both SSE (POST /invocations) and WebSocket (/ws).
from bedrock_agentcore.runtime import serve_ag_ui
# Framework agent with a .run() method — one line
serve_ag_ui(agui_agent)
Or write a custom agent with the decorator form:
from bedrock_agentcore.runtime import AGUIApp
from ag_ui.core import RunAgentInput, RunStartedEvent, RunFinishedEvent
app = AGUIApp()
@app.entrypoint
async def my_agent(input_data: RunAgentInput):
yield RunStartedEvent(thread_id=input_data.thread_id, run_id=input_data.run_id)
# ... your agent logic, yield AG-UI events ...
yield RunFinishedEvent(thread_id=input_data.thread_id, run_id=input_data.run_id)
app.run()
Install with: pip install "bedrock-agentcore[ag-ui]"
See the AG-UI protocol contract for full details.
🏗️ Deployment
AgentCore CLI (Recommended)
The fastest way to deploy your agent to Bedrock AgentCore. Install via npm:
npm i -g @aws/agentcore
Then create and deploy your agent:
agentcore create --name MyAgent --defaults
cd MyAgent
agentcore deploy
The CLI handles packaging, infrastructure provisioning, and deployment automatically. See the AgentCore CLI documentation for full details.
AWS CDK (Advanced)
The AgentCore CLI generates AWS CDK under the hood. For full infrastructure-as-code control, customize the generated CDK project directly or refer to the L1 CDK documentation.
A2A Protocol Support
Serve your agent using the A2A (Agent-to-Agent) protocol on Bedrock AgentCore Runtime. Works with any framework that provides an a2a-sdk AgentExecutor (Strands, LangGraph, Google ADK, or custom).
pip install "bedrock-agentcore[a2a]"
from strands import Agent
from strands.a2a import StrandsA2AExecutor
from bedrock_agentcore.runtime import serve_a2a
agent = Agent(model="us.anthropic.claude-sonnet-4-20250514", system_prompt="You are a helpful assistant.")
serve_a2a(StrandsA2AExecutor(agent))
See A2A Protocol Examples for LangGraph, Google ADK, and advanced usage.
📝 License & Contributing
- License: Apache 2.0 - see LICENSE.txt
- Contributing: See CONTRIBUTING.md
- Security: Report vulnerabilities via SECURITY.md
2 maintainers
Metadata
2 maintainers
Release files for bedrock-agentcore 1.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bedrock_agentcore-1.11.0.tar.gz | 712.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bedrock_agentcore-1.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 982.3 kB
Release files / bedrock_agentcore-1.11.0.tar.gz
| Download URL | bedrock_agentcore-1.11.0.tar.gz |
|---|---|
| Size | 712.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a17d10f746061d650fa3d1ccfa664b8080871cb631ff36c5156a2e09cbfe8f90
|
|
BLAKE2b-256 checksum How to use checksums |
e99ccdfcb0b0518aa3857c750a1ce839ca03fb27a67254622d7f7842ba3e149c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2026.
Transparency logRelease files / bedrock_agentcore-1.11.0-py3-none-any.whl
| Download URL | bedrock_agentcore-1.11.0-py3-none-any.whl |
|---|---|
| Size | 269.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4ba7528f5dd167dffc307eafc47262aff89029f0fa9bc80106f19dfd6fc010f
|
|
BLAKE2b-256 checksum How to use checksums |
a751333fa1d928c99bb3a49f09f34f42d8a9c9845f3d0a15fd3af934c1834ca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2026.
Transparency log
