Is an enterprise-grade suite of services designed to accelerate moving your agentic applications from POC to Production. AgentCore enables you to deploy and operate agents securely, at scale. AgentCore services can be used together or independently and work with any framework including Strands Agents, LangGraph, CrewAI, and LlamaIndex, as well as any foundation model in or outside of Amazon Bedrock, giving you the ultimate flexibility.
It serves developers and enterprises who need
robust, secure, and scalable infrastructure to support dynamic execution paths at runtime
controls to monitor behavior
powerful tools to enhance agents, and
the flexibility to adapt as the landscape evolves.
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.
AgentCore includes foundational tools required by agents to execute real-world workflows:
AgentCore Gateway. Enable agents to seamlessly discover and securely connect to tools, data, and other agents.
AgentCore Memory. Allow agents to retain both short-term and long-term memory with high accuracy.
AgentCore Runtime. Deploy agents securely at scale. Built for dynamic agentic workload demands including the longest session runtime in the industry for asynchronous workloads.
AgentCore Identity. Enables AI agents to securely access AWS services and third-party tools on behalf of users or autonomously with pre-authorization..
AgentCore Observability. Gives developers complete visibility into agent workflows to trace, debug, and monitor AI agents' performance in production environments. With support for OpenTelemetry compatible telemetry and detailed visualizations of each step of the agent workflow, AgentCore enables developers to easily gain visibility into agent behavior and maintain quality standards at scale.
Browser tool: Provides a fast, secure, cloud-based browser runtime to enable AI agents to interact with websites at scale.
Code Interpreter: Enables AI agents to write and execute code securely in sandbox environments, enhancing their accuracy and expanding their ability to solve complex end-to-end tasks.
The Amazon Bedrock AgentCore Python SDK acts as a wrapper that:
Transforms your agent code into AgentCore's standardized protocols
Handles HTTP and MCP server infrastructure automatically
Lets you focus on your agent's core functionality
Supports two protocol types:
HTTP Protocol: Traditional request/response REST API endpoints
MCP Protocol: Model Context Protocol for tools and agent servers
The SDK automatically:
Hosts your agent on port 8080
Provides two key endpoints:
/invocations: Primary agent interaction (JSON input → JSON/SSE output)
/ping: Health check for monitoring
You can convert your existing agent function into an Amazon Bedrock AgentCore-compatible service with just four steps:
Import the Runtime App with from bedrock_agentcore.runtime import BedrockAgentCoreApp
Initialize the App in our code with app = BedrockAgentCoreApp()
Decorate the invocation function with the @app.entrypoint decorator
Let AgentCoreRuntime control the running of the agent with app.run()
You can invoke the agent using the InvokeAgentRuntime operation:
import boto3
import json
# Initialize the Bedrock AgentCore client
agent_core_client = boto3.client('bedrock-agentcore', region_name="us-east-1")
# Prepare the payload
payload = json.dumps({"prompt": prompt}).encode()
# Invoke the agent
response = agent_core_client.invoke_agent_runtime(
agentRuntimeArn=agent_arn,
runtimeSessionId=session_id,
payload=payload
)
Function Calling
The ability for AI models to invoke external functions, APIs, or tools during conversations, enabling agents to perform actions beyond text generation like database queries or API calls.
These technologies work together to create sophisticated AI systems where specialized agents can collaborate, use external tools, and be managed through unified orchestration platforms on AWS.
The session header (X-Amzn-Bedrock-AgentCore-Runtime-Session-Id) is allowed by default. However, the Authorization header must be explicitly allowed. Any other custom headers you want to forward must use the X-Amzn-Bedrock-AgentCore-Runtime-Custom- prefix and must be explicitly allowed..
The Authorization Code flow is for interactive sign-in where users authenticate through a browser. The Client Credentials flow is for machine-to-machine communication where services authenticate directly with a client ID and secret.