# Amazon Bedrock AgentCore Developer Guide

- [Overview](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.md)
- [Supported AWS Regions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-regions.md)
- [Get started with AgentCore](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-get-started-cli.md)
- [Understand the available interfaces for using AgentCore](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/develop-agents.md)
- [AgentCore MCP Server: Vibe coding with your coding assistant](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/mcp-getting-started.md)
- [AgentCore CLI reference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-cli-reference.md)
- [AgentCore Python SDK reference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-python-sdk-reference.md)
- [AgentCore TypeScript SDK reference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-typescript-sdk-reference.md)
- [Tagging resources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/tagging.md)
- [Quotas](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/bedrock-agentcore-limits.md)
- [Release notes](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.md)

## [AgentCore harness](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness.md)

- [Get started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-get-started.md): You can use the harness through the AgentCore CLI or directly with AWS SDKs such as boto3.
- [Models and instructions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-models.md): Define a harness once with defaults for model, system prompt, tools, memory, and execution limits.
- [Tools](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-tools.md): Tools are declarative.
- [Lifecycle hooks](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-lifecycle-hooks.md): Lifecycle hooks send an event to an AWS Lambda function, Amazon SNS topic, or Amazon EventBridge event bus at a defined point in the harness agent loop.
- [Skills](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-skills.md): Agent Skills are bundles of markdown and scripts that give the agent domain knowledge on demand.
- [Memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-memory.md): When memory is enabled, the harness persists conversation state in AgentCore Memory.
- [Environment and filesystem](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-environment.md): Every harness session runs in an isolated microVM with its own filesystem and shell.
- [Interactive shells](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-command-shell.md): The InvokeAgentRuntimeCommandShell operation opens a persistent, interactive terminal inside a running AgentCore harness session over WebSocket.
- [Observability and cost controls](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-operations.md): This page covers monitoring your harness, controlling execution costs, and managing resource tags.
- [Versioning and endpoints](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-versioning.md): Amazon Bedrock AgentCore implements automatic versioning for AgentCore harnesses and lets you manage different configurations using endpoints.
- [Export to code](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-export.md): Export harness to code takes a managed harness configuration and generates the equivalent agent as editable Python source code using the Strands framework.
- [Security](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-security.md): The harness gives you the same security primitives as the rest of AgentCore, wired in by configuration.
- [Harness vs. Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/harness-vs-runtime.md): AgentCore harness and AgentCore Runtime solve different parts of the same problem.


## [AgentCore Runtime: Host agent or tools](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.md)

### [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-compute-how-it-works.md)

AgentCore Runtime offers two compute types for hosting your agents: microVMs and Instances.

- [microVMs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-how-it-works.md): The Amazon Bedrock AgentCore Runtime handles scaling, session management, security isolation, and infrastructure management, allowing you to focus on building intelligent agent experiences rather than operational complexity.
- [Instances](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-how-it-works.md): When you host an agent on the Instances compute type, Amazon Bedrock AgentCore Runtime runs your agent on Amazon EC2 managed instances that it provisions and operates inside your own AWS account — so you get the hardware selection and pricing benefits of Amazon EC2 without managing instance lifecycle, operating system and runtime patching, scaling, or teardown.

### [Understand the AgentCore Runtime service contract](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-service-contract.md)

The AgentCore Runtime service contract defines the standardized communication protocol that your agent application must implement to integrate with the Amazon Bedrock agent hosting infrastructure.

- [HTTP protocol contract](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-http-protocol-contract.md): Understand the requirements for implementing the HTTP protocol in your agent application.
- [MCP protocol contract](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp-protocol-contract.md): Understand the requirements for implementing the Model Context Protocol (MCP) so that agents can call tools and agent servers.
- [A2A protocol contract](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-a2a-protocol-contract.md): The A2A protocol contract defines the requirements for implementing agent-to-agent communication in Amazon Bedrock AgentCore Runtime.
- [AG-UI protocol contract](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-agui-protocol-contract.md): The AG-UI protocol contract defines the requirements for implementing agent-to-user interface communication in Amazon Bedrock AgentCore Runtime.
- [IAM Permissions for AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.md): The following are IAM permissions you need to create an agent in an AgentCore Runtime and the execution role permissions that an agent needs to run in an AgentCore Runtime.

### [Get started with AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-getting-started.md)

You can use the following tutorials to get started with Amazon Bedrock AgentCore Runtime.

- [Get started with AgentCore CLI](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-cli.md): This quickstart gets you from zero to a running agent in a few minutes using the AgentCore CLI.
- [Get started with AgentCore CLI (TypeScript)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-cli-typescript.md): This tutorial shows you how to use the AgentCore CLI to create, deploy, and invoke a TypeScript agent on Amazon Bedrock AgentCore Runtime.
- [Get started without the AgentCore CLI](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/getting-started-custom.md): You can create a AgentCore Runtime agent without the AgentCore CLI.

### [Get started with Instances](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-getting-started.md)

These tutorials walk through hosting an agent on the Instances compute type.

- [Using the console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-get-started-console.md): This tutorial walks through hosting an agent on the Instances compute type using the AWS Management Console.
- [Using the AWS CLI or SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-get-started-cli.md): This tutorial walks through hosting an agent on the Instances compute type with the AWS Command Line Interface (AWS CLI) and SDKs.

### [Get started with direct code deployment](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-code-deploy.md)

Direct code deployment enables you to bring your agent to Amazon Bedrock AgentCore Runtime simply by packaging agent code and its dependencies in a .zip file archive.

- [Direct code deployment for Python](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-code-deploy-python.md): Direct code deployment enables you to bring your Python-based agent to Amazon Bedrock AgentCore Runtime simply by packaging agent code and its dependencies in a .zip file archive.
- [Direct code deployment for Node.js](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-code-deploy-node.md): Direct code deployment enables you to bring your Node.js-based agent to Amazon Bedrock AgentCore Runtime simply by packaging agent code and its dependencies in a .zip file archive.
- [Supported runtimes and deprecation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-code-deploy-supported-runtimes.md): The following table lists the supported AgentCore Runtime direct code deploy language runtimes and projected deprecation dates.
- [Troubleshooting](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-code-deploy-common-issues.md): Common issues and solutions when getting started with Amazon Bedrock AgentCore direct code deployment.
- [Get started with bidirectional streaming using WebSocket](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-websocket.md): Amazon Bedrock AgentCore Runtime lets you deploy agents that support WebSocket streaming for real-time bidirectional communication.
- [Optimize your agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-v2-optimize.md): Amazon Bedrock AgentCore Runtime V2 starts your agent by restoring a snapshot.
- [Use any agent framework](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/using-any-agent-framework.md): You can use open source AI frameworks to create an agent or tool.
- [Use any foundation model](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/using-any-model.md): You can use any foundation model with AgentCore Runtime The following are examples for Amazon Bedrock, Open AI, Gemini and Fireworks AI:
- [Deploy MCP servers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.md): Amazon Bedrock AgentCore Runtime lets you deploy and run Model Context Protocol (MCP) servers in the AgentCore Runtime.
- [Stateful MCP features](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/mcp-stateful-features.md): The Model Context Protocol (MCP) provides a standardized way for AI applications to interact with external data and capabilities.
- [Deploy A2A servers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-a2a.md): Amazon Bedrock AgentCore Runtime lets you deploy and run Agent-to-Agent (A2A) servers in the AgentCore Runtime.
- [Deploy AG-UI servers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-agui.md): Amazon Bedrock AgentCore Runtime lets you deploy and run Agent User Interface (AG-UI) servers in the AgentCore Runtime.

### [Use isolated sessions for agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-sessions.md)

Amazon Bedrock AgentCore Runtime lets you isolate each user session and safely reuse context across multiple invocations in a user session.

- [Configure lifecycle settings](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md): The LifecycleConfiguration input parameter to CreateAgentRuntime lets you manage the lifecycle of runtime sessions and resources in Amazon Bedrock AgentCore Runtime.
- [Stop a running session](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-stop-session.md): The StopRuntimeSession operation lets you immediately terminate active agent AgentCore Runtime sessions for proper resource cleanup and session lifecycle management.
- [File system configurations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-filesystem-configurations.md): AgentCore Runtime supports persistent file systems through the filesystemConfigurations parameter.
- [Handle asynchronous and long running agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-long-run.md): Amazon Bedrock AgentCore Runtime can handle asynchronous processing and long running agents.
- [Stream agent responses](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/response-streaming.md): The following Strands Agents example shows how an AgentCore Runtime agent can stream a response back to a client.

### [Bidirectional streaming](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-bidirectional-streaming.md)

Amazon Bedrock AgentCore Runtime supports bidirectional streaming, enabling real-time, two-way communication between clients and agents.

- [Bidirectional streaming with WebSocket](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-bidirectional-streaming-websocket.md): To get started with WebSocket streaming, see Get started with bidirectional streaming using WebSocket.

### [Bidirectional streaming with WebRTC](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-webrtc.md)

With Amazon Bedrock AgentCore Runtime, you can use WebRTC (Web Real-Time Communication) to enable real-time media streaming between clients and agents.

- [Tutorial: WebRTC with KVS TURN](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-webrtc-get-started-kvs.md): In this tutorial, you build a WebRTC voice connection between a browser client and an agent running on AgentCore Runtime, using Amazon Kinesis Video Streams (KVS) managed TURN for media relaying.
- [Code examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-bidirectional-streaming-examples.md): The following sample applications demonstrate bidirectional streaming on Amazon Bedrock AgentCore Runtime.
- [Pass custom headers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-header-allowlist.md): Custom headers let you pass contextual information from your application directly to your agent code without cluttering the main request payload.
- [Authenticate and authorize with Inbound Auth and Outbound Auth](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-oauth.md): This section shows you how to implement authentication and authorization for your agent runtime using OAuth and JWT bearer tokens with AgentCore Identity .
- [AgentCore Runtime versioning and endpoints](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agent-runtime-versioning.md): Amazon Bedrock AgentCore implements automatic versioning for AgentCore Runtimes and lets you manage different configurations using endpoints.
- [Invoke an agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-invoke-agent.md): The InvokeAgentRuntime operation lets you send requests to specific AgentCore Runtime endpoints identified by their Amazon Resource Name (ARN) and receive streaming responses containing the agent’s output.

### [Shell execution](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-shell-execution.md)

Amazon Bedrock AgentCore Runtime lets you run shell commands inside a running agent’s session.

- [Execute shell commands](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-execute-command.md): The InvokeAgentRuntimeCommand operation lets you execute shell commands directly inside a running AgentCore Runtime session and stream the output back over HTTP/2.
- [Interactive Shells (Terminals)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-get-started-command-shell.md): The InvokeAgentRuntimeCommandShell operation opens a persistent, interactive terminal session inside a running AgentCore Runtime session over WebSocket.
- [Observe agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-observability.md): For information about the AgentCore Runtime observability metrics, see Add observability to your Amazon Bedrock AgentCore resources.
- [Security best practices](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-security-best-practices.md): This topic consolidates security best practices for Amazon Bedrock AgentCore Runtime.
- [Troubleshoot](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-troubleshooting.md): This troubleshooting topic helps you identify and resolve common issues when working with AgentCore Runtime.


## [AgentCore Memory: Add memory to your agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.md)

### [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/how-it-works.md)

AgentCore Memory provides a set of APIs that let your AI agents seamlessly store, retrieve, and utilize both short-term and long-term memory.

- [Memory terminology](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-terminology.md)
- [Memory types](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-types.md): AgentCore Memory offers two types of memory that work together to create intelligent, context-aware AI agents:

### [Memory strategies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-strategies.md)

In AgentCore Memory, you can add memory strategies to your memory resource.

### [Built-in strategies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/built-in-strategies.md)

AgentCore Memory provides built-in strategies to create memories.

### [Semantic memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/semantic-memory-strategy.md)

The semantic memory strategy is designed to identify and extract key pieces of factual information and contextual knowledge from conversational data.

- [System prompt for semantic memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-system-prompt.md): The semantic strategy includes instructions and output schemas in the default prompts for the extraction and consolidation steps.

### [User preference memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/user-preference-memory-strategy.md)

The UserPreferenceMemoryStrategy is designed to automatically identify and extract user preferences, choices, and styles from conversational data.

- [System prompt for user preference memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-user-prompt.md): The user preference strategy includes instructions and output schemas in the default prompts for the extraction and consolidation steps.

### [Summary strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/summary-strategy.md)

The SummaryStrategy is responsible for generating condensed, real-time summaries of conversations within a single session.

- [System prompt for summary strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-summary-prompt.md): The semantic strategy includes instructions and an output schema in the default system prompt for a single consolidation step.

### [Episodic memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/episodic-memory-strategy.md)

Episodic memory captures meaningful slices of user and system interactions so applications can recall context in a way that feels focused and relevant.

- [System prompt for episodic memory strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-episodic-prompt.md): The episodic memory strategy includes instructions and output schemas in the default prompts for episode extraction, episode consolidation, and reflection generation.
- [Customize a strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-custom-strategy.md): For advanced or domain-specific use cases, you can create a built-in with overrides strategy to gain fine-grained control over the long-term memory process.
- [Self-managed strategies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-self-managed-strategies.md): A self-managed strategy in Amazon Bedrock AgentCore Memory gives you complete control over your memory extraction and consolidation pipelines.
- [Memory organization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-organization.md): You can set how short-term and long-term memories are organized in an AgentCore Memory.
- [Memory record streaming](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-record-streaming.md): Memory record streaming in Amazon Bedrock AgentCore Memory delivers real-time notifications when memory records are created, updated, or deleted.
- [Cross-account memory access](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-cross-account-access.md): Amazon Bedrock AgentCore Memory supports cross-account access, enabling you to build multi-account architectures where memory resources and consuming agents span multiple AWS accounts.
- [Compare long-term memory with Retrieval-Augmented Generation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-ltm-rag.md): Long-term memory in Amazon Bedrock AgentCore Memory serves as persistent storage for session-specific context, enabling agents to maintain continuity and personalization across interactions.
- [Get started with AgentCore Memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-get-started.md): Amazon Bedrock AgentCore Memory lets you create and manage AgentCore Memory resources that store conversation context for your AI agents.

### [Create an AgentCore Memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-create-a-memory-store.md)

You can create an AgentCore Memory with the AgentCore CLI, the AWS console, or with the CreateMemory AWS SDK operation.

- [Encrypt your Amazon Bedrock AgentCore Memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/storage-encryption.md): When creating an AgentCore Memory, it is important to make sure your data is safe and secure.

### [Use short-term memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/using-memory-short-term.md)

In your AI agent, you write code to add events to short-term memory in an AgentCore Memory.

- [Create an event](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/short-term-create-event.md): Events are the fundamental units of short-term from which structured informations are extracted into long-term memory in AgentCore Memory.
- [Get an event](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/short-term-get-event.md): The GetEvent API retrieves a specific raw event by its identifier from short-term memory in AgentCore Memory.
- [List events](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/short-term-list-events.md): The ListEvents operation is valuable for applications that need to reconstruct conversation histories, analyze interaction patterns, or implement memory-based features like conversation summarization and context awareness.
- [Delete an event](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/short-term-delete-event.md): The DeleteEvent operation removes individual events from your AgentCore Memory.

### [Use long-term memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-memory-long-term.md)

Long-term memory is enabled by adding one or more memory strategies to a memory resource.

- [Enable long-term memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-enabling-long-term-memory.md): You can enable long-term memory in two ways: by adding strategies when you first create an AgentCore Memory , or by updating an existing resource to include them.
- [Specify memory organization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/specify-long-term-memory-organization.md): When you create an AgentCore Memory, use a namespace to specify where the long-term memories for a memory strategy are logically grouped.
- [Configure built-in strategies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-configuring-built-in-strategies.md): AgentCore Memory provides pre-configured, built-in memory strategies for common use cases.
- [Configure a custom strategy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-configuring-custom-strategies.md): For advanced use cases, built-in with overrides strategies give you fine-grained control over the memory extraction process.
- [Direct long-term memory ingestion](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-ingest-data.md): Use IngestData to submit content directly for long-term memory extraction, without persisting it as a short-term memory event.
- [Save and retrieve insights](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-saving-and-retrieving-insights.md): Once you have configured an AgentCore Memory with at least one long-term memory strategy and the strategy is ACTIVE, the service will automatically begin processing conversational data to extract and store insights.
- [Retrieve memory records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-retrieve-records.md): You can retrieve extracted memories using the RetrieveMemoryRecords API.
- [List memory records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-list-memory-records.md): The ListMemoryRecords operation lets you retrieve memory records from a specific namespace or under a particular namespace path hierarchy without performing a semantic search.
- [Long Term Memory Metadata](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-memory-metadata.md): Metadata filtering in Amazon Bedrock AgentCore Memory lets you add structured attributes to your long-term memory records.
- [Delete memory records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-delete-memory-records.md): The DeleteMemoryRecord API removes individual memory records from your AgentCore Memory, giving you control over what information persists in your application’s memory.
- [Redrive failed ingestions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/long-term-redrive.md): Extraction from short-term memory to long-term memory is usually automatic.

### [AgentCore Memory examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-examples.md)

You can use AgentCore Memory with a variety of SDKS and agent frameworks.

- [Customer support AI agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-customer-scenario.md): In this section you learn how to build a customer support AI agent that uses AgentCore Memory to provide personalized assistance by maintaining conversation history and extracting long-term insights about user preferences.
- [Integrate with LangChain or LangGraph](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-integrate-lang.md): LangChain and LangGraph are powerful open-source frameworks for developing agents through a graph-based architecture.
- [AWS SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/aws-sdk-memory.md): Use the AWS SDK to directly interact with AgentCore Memory fine-grained control over memory operations.
- [Amazon Bedrock AgentCore SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-sdk-memory.md): Use the Amazon Bedrock AgentCore Python SDK for a higher-level abstraction that simplifies memory operations and provides convenient methods for common use cases.
- [Strands Agents SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/strands-sdk-memory.md): Use the Strands Agents SDK for seamless integration with agent frameworks, providing automatic memory management and retrieval within conversational agents.
- [Amazon Bedrock capacity for built-in with overrides strategies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/bedrock-capacity.md): When configuring built-in with overrides strategies with CreateMemory or UpdateMemory , you must provide an IAM execution role ( memoryExecutionRoleArn ).
- [Observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-observability.md): You can monitor usage metrics for your memory in CloudWatch metrics.
- [Best practices](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/best-practices.md): We recommend these best practices for using AgentCore Memory effectively in your AI agent applications.

### [Advanced topics](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-advanced.md)

This chapter describes how to front Amazon Bedrock AgentCore Memory with an AgentCore Gateway to add OAuth authentication for end users and fine-grained access control (FGAC).

### [Access through a gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-connector.md)

By default, an application calls the Amazon Bedrock AgentCore Memory data plane directly, and each request is authenticated with AWS Signature Version 4 (SigV4).

- [Set up the connector](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-setup.md): To front a Memory resource with a gateway, you create a gateway with an inbound authorizer, then add a target that uses the agentcore-memory connector.
- [Create a Memory connector using the console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-connector-console.md): You can create a gateway and its agentcore-memory connector target in the AWS Management Console.
- [Authenticate end users with OAuth](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-oauth.md): The Amazon Bedrock AgentCore Memory data plane authenticates callers with AWS Signature Version 4 (SigV4) only.

### [Fine-grained access control](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-fgac.md)

With fine-grained access control (FGAC) for Amazon Bedrock AgentCore Memory, you can bind Memory access to an OAuth-authenticated caller’s identity.

- [Policy examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-fgac-policy-examples.md): This page provides Cedar policy patterns that are specific to Amazon Bedrock AgentCore Memory — isolating a caller to their own actor, their own namespace, and a chosen set of Memory operations.
- [Restrict direct access](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory-gateway-restrict-access.md): The fine-grained access control policies on your gateway govern requests that arrive through the gateway.


## [AgentCore Gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.md)

- [Get started with AgentCore Gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-quick-start.md): In this quick start guide you’ll learn how to set up a gateway and integrate it into your agents using the AgentCore CLI.
- [Core concepts](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-core-concepts.md): Amazon Bedrock AgentCore Gateway provides a standardized, secure entry point for agentic traffic, letting AI agents discover and interact with tools, other agents, and large language models (LLMs).
- [AgentCore Gateway features](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-features.md): Amazon Bedrock AgentCore Gateway provides features that you can optionally enable for your gateway.

### [Supported gateway targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-supported-targets.md)

Targets define the capabilities that your gateway will host.

### [MCP targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-targets-mcp.md)

MCP targets operate in aggregation mode — the gateway acts as an MCP server whose capabilities combine those of all its MCP targets.

- [Lambda functions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-add-target-lambda.md): Lambda targets allow you to connect your gateway to AWS Lambda functions that implement your tools.
- [API Gateway stages](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-api-gateway.md): An API Gateway REST API target connects your gateway to a stage of your REST API.
- [OpenAPI schemas](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-schema-openapi.md): OpenAPI (formerly known as Swagger) is a widely used standard for describing RESTful APIs.
- [Smithy models](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-building-smithy-targets.md): Smithy is a language for defining services and software development kits (SDKs).
- [MCP servers targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.md): MCP servers provide local tools, data access, or custom functions for your interactions with models and agents in Bedrock AgentCore.
- [Integration provider templates](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-integrations.md): Amazon Bedrock AgentCore lets you add open source templates from the following integration providers as targets in your gateway:

### [Built-in connectors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connectors.md)

Amazon Bedrock AgentCore lets you add the following built-in connectors as targets in your gateway:

- [Managed Knowledge Bases](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-managed-kb.md): Amazon Bedrock Managed Knowledge Bases provides fully managed retrieval-augmented generation (RAG): Amazon Bedrock handles the vector store, data ingestion, and retrieval optimization, so there is no retrieval infrastructure for you to provision or operate.
- [Web Search Tool](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-web-search-tool.md): AI agents are transforming how organizations interact with information, but they face a fundamental limitation: their knowledge is frozen at training time.
- [Connector versions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-versions.md): Built-in connectors on Amazon Bedrock AgentCore Gateway use semantic versioning (MAJOR.MINOR.PATCH).
- [Understand gateway tool naming](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-tool-naming.md): The name of a tool in your gateway is dependent on the name of the target through which the tool can be accessed.

### [HTTP targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-targets-http.md)

For HTTP targets, the gateway sends traffic directly to the target without aggregation or protocol translation.

- [AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-http-runtime.md): You can add an Amazon Bedrock AgentCore Runtime agent as a gateway target.
- [HTTP passthrough](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-http-passthrough.md): You can add an HTTP passthrough target to route traffic through the gateway to any HTTP endpoint.

### [Inference targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-targets-inference.md)

You can add inference targets to your gateway to route LLM traffic to model providers.

- [Connector](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-inference-connector.md): Inference connector targets provide preconfigured setup for supported model providers.
- [Provider](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-inference-provider.md): Inference provider targets give you explicit control over the endpoint, model mappings, and operations for a model provider.

### [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-prerequisites.md)

To interact with the AgentCore Gateway service, you’ll need to complete the following prerequisites:

- [Set up dependencies and credentials](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-setup-tools-credentials.md): The AgentCore Gateway service involves the following main processes:
- [Set up permissions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-prerequisites-permissions.md): To use Amazon Bedrock AgentCore Gateway and its capabilities, you’ll need to consider the following permissions:
- [Set up inbound authorization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-inbound-auth.md): Before you create your gateway, you must set up inbound authorization.
- [Set up outbound authorization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-outbound-auth.md): Outbound authorization lets Amazon Bedrock AgentCore gateways securely access gateway targets on behalf of users that were authenticated and authorized during inbound authorization.

### [Set up a gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-building.md)

Amazon Bedrock AgentCore Gateway provides a unified connectivity layer between agents and the tools and resources they need to interact with.

### [Create a gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-create.md)

This guide walks you through the process of creating and configuring an Amazon Bedrock AgentCore Gateway.

- [Create a gateway (console)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-create-console.md): To create a gateway using the console
- [Create a gateway (CLI)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-create-cli.md): You can use the AgentCore CLI to create gateways with simplified commands.
- [Create a gateway (API)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-create-api.md): To create a AgentCore gateway using the API, make a CreateGateway request with one of the AgentCore control plane endpoints.

### [Add targets to a gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-building-adding-targets.md)

After creating a gateway, you can add targets, which define the tools that your gateway will host.

- [Add a target using the AWS Management Console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-add-target-console.md): In the AWS Management Console, you can add gateway targets when you create the gateway.
- [Add a target using the CLI](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-add-target-cli.md): You can use the AgentCore CLI to add targets to an existing gateway with simplified commands.

### [Add a target using the API](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-add-target-api.md)

To add a target using the API, make a CreateGatewayTarget request with one of the AgentCore control plane endpoints and define a target configuration that matches the target type.

- [Specify authorization type and credentials](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-building-adding-targets-authorization.md): In the CreateGatewayTarget request body, you specify the credential provider configuration in the credentialProviderConfigurations array.
- [Define the target configuration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-add-target-api-target-config.md): The target configuration depends on the target type that you’re adding to the gateway.

### [Use a gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using.md)

After setting up your gateway with targets , you can configure your application or agent to use the gateway through the Model Context Protocol (MCP) .

### [Gateway authorization and authentication](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-auth.md)

To invoke your gateway and gateway target, you’ll need to make sure that the following credentials that you set up while fulfilling the prerequisites are recognized during gateway invocation:

- [Example: AgentCore CLI default gateway authorization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-auth-ex-starter.md): If you used the AgentCore CLI to create a gateway and a Lambda target, the CLI configures JWT-based inbound authorization and IAM-based outbound authorization for you automatically.
- [Example: Authorization code grant](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-auth-ex-3lo.md): If you set up your gateway target with an authorization code grant (for more information, see OAuth authorization ), the defaultReturnUrl that you specified when creating the gateway will be the link that the user’s browser redirects to after authentication.
- [List gateway tools](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-list.md): To list all available tools that an AgentCore gateway provides, make a POST request to the gateway’s MCP endpoint and specify tools/list as the method in the request body:
- [Call a gateway tool](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-call.md): To call a specific tool, make a POST request to the gateway’s MCP endpoint.
- [List gateway prompts](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-prompts-list.md): To list all available prompts that an AgentCore gateway provides, make a POST request to the gateway’s MCP endpoint and specify prompts/list as the method in the request body:
- [Get a gateway prompt](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-prompts-get.md): To get a specific prompt, make a POST request to the gateway’s MCP endpoint and specify prompts/get as the method in the request body, name of the prompt, and the arguments:
- [List gateway resources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-resources-list.md): To list all available resources that an AgentCore gateway provides, make a POST request to the gateway’s MCP endpoint and specify resources/list as the method in the request body:
- [Read a gateway resource](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-resources-read.md): To read a specific resource, make a POST request to the gateway’s MCP endpoint and specify resources/read as the method in the request body and the URI of the resource:
- [List gateway resource templates](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-resources-templates-list.md): To list all available resource templates that an AgentCore gateway provides, make a POST request to the gateway’s MCP endpoint and specify resources/templates/list as the method in the request body:
- [Elicitation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-mcp-elicitation.md): Elicitation is an MCP feature that allows an MCP server to request additional information from the client during a tool call.
- [Progress notifications](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-mcp-progress.md): Progress notifications allow MCP server targets to report incremental progress on long-running tool calls.
- [Logging messages](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-mcp-logging.md): MCP server targets can send log messages to clients during tool execution using the notifications/message method.
- [Sampling](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-mcp-sampling.md): Sampling is an MCP feature that allows an MCP server to request an LLM completion from the client during a tool call.
- [Search for a gateway tool](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-mcp-semantic-search.md): If you enabled semantic search for your gateway when you created it, you can call the x_amz_bedrock_agentcore_search tool to search for tools in your gateway with a natural language query.
- [Connect an agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-agent-integration.md): After creating and testing your gateway, you can create and connect AI agents to your gateway.

### [Gateway rules](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rules.md)

Gateway rules let you control traffic routing and override target configurations on your gateway without redeploying targets.

- [Propagation and observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rules-propagation.md): When the gateway resolves a configuration bundle through rules, it propagates the bundle to downstream services through OpenTelemetry (OTel) baggage headers.
- [Session stickiness](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rules-session-stickiness.md): When you use weighted rules for A/B testing or canary deployments, you want each session to receive a consistent experience across multiple requests.
- [API examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rules-examples.md): The following examples show how to manage gateway rules using the AWS CLI and AWS Python SDK (Boto3).
- [Fine-grained access control](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-fine-grained-access-control.md): Amazon Bedrock AgentCore Gateway provides fine-grained access control capabilities that allow you to control which users and agents can access specific tools and resources.

### [Debug and assess your gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-building-debug.md)

You can use different tools to help debug your gateway before putting it into a production environment, including built-in AWS and AgentCore Gateway tools, as well as external tools such as the MCP inspector.

- [Turn on debugging messages](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-debug-messages.md): While your gateway is in development, you can turn on debugging messages to return details on target configuration issues, including lambda function errors, egress authorizer errors, target specification parameter validation errors.
- [Use the MCP Inspector](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using-inspector.md): The MCP Inspector, available through the Model Context Protocol (MCP) , is a developer tool that helps you test and debug MCP servers by through an interactive interface.

### [Log AgentCore Gateway API calls with CloudTrail](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-cloudtrail.md)

Amazon Bedrock AgentCore Gateway is integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in Gateway.

- [Gateway event types](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-event-types.md): This section provides information about the types of events that Amazon Bedrock AgentCore Gateway logs to CloudTrail.
- [Enable data event logging for gateway resources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/enabling-cloudtrail-data-event-logging.md): You can use CloudTrail data events to get information about Amazon Bedrock AgentCore Gateway requests.
- [Understanding AgentCore Gateway CloudTrail events](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/understanding-gateway-cloudtrail-log-entries.md): A trail is a configuration that enables delivery of events as log files to an Amazon S3 bucket that you specify.

### [Advanced topics](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-advanced.md)

This chapter covers some advanced topics and additional information that can help supplement your knowledge of gateways and how you can use them effectively in your applications.

- [MCP sessions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-sessions.md): MCP sessions enable stateful interactions between clients and your AgentCore gateway.
- [Response streaming](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-mcp-streaming.md): MCP response streaming enables your AgentCore gateway to deliver real-time Server-Sent Events (SSE) to clients during tool execution.
- [Customize your gateway's encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-encryption.md): By default, Gateway encrypts your data at rest using a service-managed AWS Key Management Service key.
- [Custom domain names](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-custom-domains.md): By default, Gateway endpoints are provided with an AWS-managed domain name in the format <gateway-id>.gateway.bedrock-agentcore.<region>.amazonaws.com .

### [Gateway interceptors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors.md)

Configuring interceptors on your gateway allows you to run custom code during each invocation of your gateway.

- [Permissions for interceptors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors-permissions.md): When configuring interceptors, your gateway service role must have the lambda:InvokeFunction IAM permissions to invoke the Lambda functions that serve as interceptors.
- [Types of interceptors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors-types.md): There are two types of interceptors that you can configure on your gateway: REQUEST interceptors and RESPONSE interceptors.
- [Configuration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors-configuration.md): Interceptors can be configured with an input parameter called passRequestHeaders
- [Examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors-examples.md): The following examples show Python AWS Lambda functions for common interceptor use cases.

### [Rate limits](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits.md)

With rate limits, you control how much traffic individual callers, targets, or tools can consume on your gateway.

- [Dimensions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits-dimensions.md): Dimension keys determine how the gateway groups traffic into rate limit buckets.
- [Metrics](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits-metrics.md): Rate limit entries specify one or more metrics that define what is being measured and the time window for enforcement.
- [Enforcement](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits-enforcement.md): This topic describes how the gateway evaluates and enforces rate limits at runtime, including interaction with other gateway features, throttled response formats, and observability.
- [API examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits-examples.md): The following examples show how to manage rate limits using the AWS CLI and AWS Python SDK (Boto3).
- [Best practices](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-rate-limits-best-practices.md): This topic provides guidance on designing, deploying, and operating rate limits effectively on your gateway.
- [AWS WAF integration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-waf.md): You can use AWS WAF with Amazon Bedrock AgentCore Gateway to protect your gateway from web exploits, bot traffic, and volumetric attacks.
- [Header propagation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-headers.md)
- [Performance optimization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-advanced-performance.md): To optimize the performance of your Gateway implementations, consider the following best practices:


## [AgentCore Identity: Provide identity management for agent applications](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity.md)

### [Overview](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-overview.md)

In the rapidly evolving landscape of AI agents, organizations need robust identity management solutions that can handle the unique challenges associated with non-human identities.

- [Features](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/key-features-and-benefits.md): AgentCore Identity offers a set of features designed to address the unique challenges of workload identity management and credential security:
- [Terminology](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-terminology.md): AgentCore Identity uses specific terminology to describe the components, processes, and relationships involved in workload identity management and credential handling.
- [Example use cases](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-use-cases.md): Amazon Bedrock AgentCore Identity supports a wide range of use cases across different industries and application types.

### [Get started with AgentCore Identity](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-getting-started.md)

If you’re building AI agents that need to access external services like Google Drive, Slack, or GitHub, Amazon Bedrock AgentCore Identity provides the secure authentication infrastructure you need.

- [Build your first agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-getting-started-cognito.md): This getting started tutorial walks you through building a complete authenticated agent from the ground up using Amazon Bedrock AgentCore Identity and will help you get started with implementing identity features in your agent applications.
- [Google Drive integration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-getting-started-google.md): This getting started tutorial walks you through the essential steps to start using Amazon Bedrock AgentCore Identity for your AI agents.

### [Using the console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-how-to.md)

The AgentCore Identity console provides a centralized interface for managing your agent authentication configurations.

### [Configure an OAuth client](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-oauth-client.md)

An OAuth client enables your agent to securely access external services on behalf of users without requiring them to share their credentials directly.

- [Add OAuth client using included provider](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-add-oauth-client-included.md): Built-in providers offer streamlined setup for popular services including Google, GitHub, Slack, and Salesforce.
- [Add OAuth client using custom provider](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-add-oauth-client-custom.md): Custom providers enable you to connect to any OAuth2-compatible resource server beyond the built-in provider options.
- [Update OAuth client](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-update-oauth-client.md): You can modify the configuration settings for your existing OAuth client.
- [Delete OAuth client](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-delete-oauth-client.md): When you no longer need an OAuth client, you can delete it from your account.

### [Configure an API key](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-api-key.md)

API keys provide key-based authentication for services that require direct key access with secure storage capabilities.

- [Add API key](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-add-api-key.md): API keys provide key-based authentication for services that require direct key access with secure storage capabilities.
- [Update API key](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-update-api-key.md): You can update an existing API key to replace the key value when your external service provider rotates credentials.
- [Delete API key](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-delete-api-key.md): When you no longer need an API key, you can delete it from your account.

### [Manage agent identities](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-manage-agent-ids.md)

Agent identities in AgentCore Identity are implemented as workload identities with specialized attributes that enable agent-specific capabilities.

- [Understanding identities](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/understanding-agent-identities.md): Workload identities represent the digital identity of your agents within the AWS environment.
- [Agent identity directory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agent-identity-directory.md): The agent identity directory is a centralized collection of all workload identities within your AWS account.
- [Create identities](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/creating-agent-identities.md): You can create agent identities using several methods, including the AWS CLI and the AgentCore SDK, depending on your workflow and integration requirements.
- [Inbound JWT authorization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/inbound-jwt-authorizer.md): The inbound authorizer authenticates and authorizes incoming OAuth 2.0 API requests to AgentCore Runtime and AgentCore Gateway.

### [Manage credential providers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-outbound-credential-provider.md)

Credential management is a core feature of Amazon Bedrock AgentCore Identity that addresses the complex challenge of securely storing, retrieving, and managing credentials across multiple trust domains and authentication systems.

### [Supported authentication patterns](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/common-use-cases.md)

AgentCore Identity supports two primary authentication patterns that address different agent use cases.

- [On-behalf-of token exchange](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/on-behalf-of-token-exchange.md): Amazon Bedrock AgentCore Identity supports On-Behalf-Of (OBO) token exchange, enabling agents and other workloads—such as MCP servers—to exchange an inbound user access token for a new, scoped access token that targets a downstream resource server.

### [Client authentication methods](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/client-auth-methods.md)

Client authentication method controls how the OAuth client authenticates with the authorization server’s token endpoint when requesting access tokens.

- [Private Key JWT](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/private-key-jwt.md): With Private Key JWT, AgentCore Identity authenticates to a downstream identity provider’s token endpoint using a signed JWT client assertion, per RFC 7523, Section 2.2, instead of a client secret.
- [Configure credential provider](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/resource-providers.md): Resource credential providers in AgentCore Identity act as intelligent intermediaries that manage the complex relationships between agents, identity providers, and resource servers.

### [Obtain credentials](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/obtain-credentials.md)

AgentCore Identity uses a workload access token to authorize agent access to credentials stored in the vault, and this token contains both the identity of the agent and the identity of the end user on whose behalf the agent is working.

- [Get workload access token](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/get-workload-access-token.md): Understanding what workload access tokens are, how to obtain them, and the security aspects of working with them is essential for building secure agent applications.
- [Obtain access token](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-authentication.md): AgentCore Identity enables developers to obtain OAuth tokens for either user-delegated access or machine-to-machine authentication based on the configured OAuth 2.0 credential providers.
- [OAuth 2.0 authorization URL session binding](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/oauth2-authorization-url-session-binding.md): AgentCore Identity provides OAuth 2.0 access token retrievals for your agent applications to access third-party application vendors or resources protected by identity providers / authorization servers.
- [Scope credential access](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/scope-credential-provider-access.md): You can use IAM policies to control which workload identities have access to specific credential providers.
- [Obtain API key](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/obtain-api-key.md): Once you have stored your API keys in the AgentCore Identity vault, you can retrieve them directly in your agent using the AgentCore SDK and the @requires_api_key annotation.

### [Provider setup](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idps.md)

Amazon Bedrock AgentCore Identity provides managed OAuth 2.0 supported providers for both inbound and outbound authentication.

- [Amazon Cognito](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-cognito.md): Amazon Cognito can be configured as an identity provider for accessing AgentCore Gateway and Runtime, or an AgentCore Identity credential provider for outbound resource access.
- [Auth0 by Okta](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-auth0.md): Auth0 can be configured as an identity provider for accessing AgentCore Gateway and Runtime, or an AgentCore Identity credential provider for outbound resource access.
- [Atlassian](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-atlassian.md): Atlassian can be configured as an AgentCore Identity credential provider for outbound resource access.
- [CyberArk](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-cyberark.md): CyberArk can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Dropbox](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-dropbox.md): Dropbox can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Facebook](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-facebook.md): Facebook can be configured as an AgentCore Identity credential provider for outbound resource access.
- [FusionAuth](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-fusionauth.md): FusionAuth can be configured as an outbound resource credential provider for AgentCore Identity.
- [GitHub](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-github.md): GitHub can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Google](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-google.md): Google can be configured as an AgentCore Identity credential provider for outbound resource access.
- [HubSpot](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-hubspot.md): HubSpot can be configured as an AgentCore Identity credential provider for outbound resource access.
- [LinkedIn](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-linkedin.md): LinkedIn can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Microsoft](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-microsoft.md): Microsoft Entra ID can be configured as an identity provider for accessing AgentCore Gateway and Runtime, or an AgentCore Identity credential provider for outbound resource access.
- [Notion](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-notion.md): Notion can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Okta](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-okta.md): Okta can be configured as an identity provider for accessing AgentCore Gateway and Runtime, or an AgentCore Identity credential provider for outbound resource access.
- [OneLogin](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-onelogin.md): OneLogin can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Ping Identity](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-pingidentity.md): Ping Identity’s PingOne platform can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Reddit](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-reddit.md): Reddit can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Salesforce](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-salesforce.md): Salesforce can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Slack](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-slack.md): Slack can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Spotify](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-spotify.md): Spotify can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Twitch](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-twitch.md): Twitch can be configured as an AgentCore Identity credential provider for outbound resource access.
- [X](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-x.md): X can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Yandex](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-yandex.md): Yandex can be configured as an AgentCore Identity credential provider for outbound resource access.
- [Zoom](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-idp-zoom.md): Zoom can be configured as an AgentCore Identity credential provider for outbound resource access.

### [Configure a consent portal](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-consent-portal.md)

A consent portal is a hosted, AWS-managed portal that authenticates your end users to an OpenID Connect (OIDC) identity provider (IdP) and gathers their consent before your agent accesses a downstream resource on their behalf.

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-consent-portal-prerequisites.md): Before you create a consent portal, create the OAuth2 credential provider whose ARN you supply in idpConfig.credentialProviderArn, configure the gateway that the portal serves, and create the execution role that the portal assumes.
- [Execution role](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-consent-portal-execution-role.md): A consent portal assumes an IAM role that you pass as executionRoleArn when you create the portal.
- [Create with the console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-create-consent-portal-console.md): You can create a consent portal from the AgentCore console.
- [Create with the AWS CLI](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-create-consent-portal.md): You create a consent portal with the create-consent-portal command.
- [Configure a consent portal target](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-configure-consent-portal-target.md): The consent portal’s Connections page lists the resources that an end user can grant your agent consent to access.
- [Update a consent portal](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-update-consent-portal.md): You can update an existing consent portal from the AgentCore console or with the AWS CLI.
- [Delete a consent portal](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-delete-consent-portal.md): When you no longer need a consent portal, you can delete it from the AgentCore console or with the AWS CLI.
- [Private identity providers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-private-idp.md): Amazon Bedrock AgentCore Identity supports connecting to OAuth 2.0 identity providers (IdPs) hosted inside your AWS VPC, such as self-hosted Keycloak, PingFederate, or other OIDC-compliant authorization servers, without exposing them to the public internet.

### [Data protection](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-data-protection.md)

The AWS shared responsibility model applies to data protection in Amazon Bedrock AgentCore Identity.

- [Data encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-data-encryption.md): Data encryption typically falls into two categories: encryption at rest and encryption in transit.
- [Set customer managed key policy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/kms-key-policy-configuration.md)
- [Configure with API operations or an AWS SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/api-configuration-encryption.md): Set your key configuration in a SetTokenVaultCMK API request.
- [Configure KMS key for Token Vault on Console](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/console-configuration-encryption.md): The KMS key configuration determines how your token vault encrypts data at rest.
- [Identity resource tagging](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-tagging.md): Amazon Bedrock AgentCore Identity supports comprehensive tagging capabilities across its resource hierarchy to enable better resource management, cost allocation, access control, and operational visibility.


## [AgentCore payments: Enable secure microtransaction payments for AI agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments.md)

- [Core concepts](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-concepts.md)
- [Quick start](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-getting-started.md): This tutorial walks you through setting up AgentCore payments and processing your first microtransaction.
- [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-how-it-works.md): Amazon Bedrock AgentCore payments offers payment connection, wallet management, payment limits, payment processing, and payment observability.

### [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-prerequisites.md)

Complete the prerequisites on this page before you use AgentCore payments.

- [IAM roles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-iam-roles.md)
- [Marketplace subscription](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-marketplace-subscription.md): To use Coinbase as a payment provider with AgentCore payments, you must subscribe to the Coinbase Wallets for AgentCore Payments listing in AWS Marketplace.
- [Create a Payment Manager and Connector](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-create-manager.md): A Payment Manager is the top-level resource that coordinates payment operations for your AWS account.

### [Processing payments](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-processing.md)

After you complete the control plane setup, use the following workflows to create instruments, sessions, and process payments.

- [Create an instrument](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-create-instrument.md): A payment instrument represents an embedded crypto wallet that an agent uses to pay merchants on behalf of a user.
- [Fund wallet and grant permissions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-fund-wallet.md): After you create a payment instrument, the end user must fund the wallet with USD Coin (USDC) and grant the agent permission to sign transactions.
- [Create a session](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-create-session.md): A payment session is a time-bounded payment context that optionally enforces a spending budget.
- [Connecting to Bazaar](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-connect-bazaar.md): AgentCore Gateway lets you connect to paid MCP servers and API endpoints.

### [Process Payment](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-process-payment.md)

To process a payment, you need two resources:

- [Framework integrations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-framework-integrations.md): AgentCore payments integrates with popular agent frameworks to provide automated payment processing.
- [Observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-observability.md): AgentCore payments supports observability through Amazon CloudWatch, so you can monitor and troubleshoot your payment integration.
- [Payments security](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-security-best-practices.md): The following best practices can help you prevent security incidents when using Amazon Bedrock AgentCore payments.
- [Encryption at rest](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-encryption.md): Amazon Bedrock AgentCore payments encrypts all customer data at rest by default.
- [Browser Tool integration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-browser.md): There are two ways your agent can access x402 paid content: via the Browser Tool or via standard HTTP calls.
- [Troubleshooting](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-troubleshooting.md): This section provides solutions to common errors when using AWS Amazon Bedrock AgentCore payments.


## [AgentCore Code Interpreter: Execute code and analyze data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-tool.md)

- [Pre-installed libraries](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-preinstalled-libraries.md): The AgentCore Code Interpreter comes with pre-installed libraries for both Python and Node.js.

### [Get started with AgentCore Code Interpreter](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-getting-started.md)

AgentCore Code Interpreter enables your agents to execute Python code in a secure, managed environment.

- [Using AgentCore Code Interpreter via AWS Strands](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-using-strands.md): The following sections show you how to use the Amazon Bedrock AgentCore Code Interpreter with the Strands SDK.
- [Using AgentCore Code Interpreter directly](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-using-directly.md): The following sections show you how to use the Amazon Bedrock AgentCore Code Interpreter directly without an agent framework.
- [Run code from agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-building-agents.md): You can build agents that use the Code Interpreter tool to execute code and analyze data.
- [Write files to a session](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-file-operations.md): You can use the Code Interpreter to read and write files in the sandbox environment.
- [Using Terminal Commands with an execution role](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-s3-integration.md): You can create a custom Code Interpreter tool with an execution role to upload/download files from Amazon S3.

### [Resource and session management](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-resource-session-management.md)

The following topics show how the Amazon Bedrock AgentCore Code Interpreter works and how you can create the resources and manage sessions.

### [Resource management](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-resource-management.md)

The AgentCore Code Interpreter provides two types of resources:

- [Creating an AgentCore Code Interpreter](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-create.md): You can create a Code Interpreter using the Amazon Bedrock AgentCore console, AWS CLI, or AWS SDK.
- [Listing AgentCore Code Interpreter tools](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-list.md): You can view a list of all your Code Interpreter tools to manage and monitor them.
- [Deleting an AgentCore Code Interpreter](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-delete.md): When you no longer need a Code Interpreter, you can delete it to free up resources and avoid unnecessary charges.

### [Session management](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-session-characteristics.md)

The AgentCore Code Interpreter sessions have the following characteristics:

- [Starting a AgentCore Code Interpreter session](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-start-session.md): After creating a Code Interpreter, you can start a session to execute code.
- [Executing code](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-execute-code.md): Once you have started a Code Interpreter session, you can execute code in the session.
- [Runtime selection](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-runtime-selection.md): For a language, you can optionally specify a particular runtime.
- [Stopping a AgentCore Code Interpreter session](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-stop-session.md): When you are finished using a Code Interpreter session, you should stop it to release resources and avoid unnecessary charges.
- [File system configurations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-filesystem-configurations.md): AgentCore Code Interpreter supports mounting your own file systems into code interpreter sessions through the filesystemConfigurations parameter.
- [API Reference Examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-api-reference-examples.md): This section provides reference examples for common Code Interpreter operations using different approaches.
- [Observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-observability.md): The AgentCore Code Interpreter provides the following observability features:
- [Root Certificate Authority](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-root-ca-certificates.md): By default, Amazon Bedrock AgentCore Code Interpreter sessions trust only publicly recognized certificate authorities.
- [Troubleshoot AgentCore Code Interpreter](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-troubleshooting.md): This section provides solutions to common issues you might encounter when using the Amazon Bedrock AgentCore Code Interpreter.


## [AgentCore Browser: interact with web applications](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-tool.md)

### [Get started with AgentCore Browser](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-quickstart.md)

AgentCore Browser enables your agents to interact with web pages through a managed Chrome browser.

- [Nova Act](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-quickstart-nova-act.md): You can build a browser agent using Nova Act to automate web interactions:
- [Playwright](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-quickstart-playwright.md): You can use the Playwright automation framework with the Browser Tool:

### [Fundamentals](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-resource-session-management.md)

The following topics show how the Amazon Bedrock AgentCore Browser works and how you can create the resources and manage sessions.

- [Using Browser Tool](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-using-tool.md)
- [Managing Browser Sessions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-managing-sessions.md)

### [Observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-observability.md)

The Amazon Bedrock AgentCore Browser provides built-in observability features including live view, session recording, session replay, and CloudWatch metrics.

- [Live View](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-dcv-integration.md): Amazon Bedrock AgentCore’s Live View is powered by AWS DCV.
- [Session Recording and Replay](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-session-recording.md): Browser session recording and replay provides comprehensive observability for debugging, auditing, or training purposes.
- [CloudWatch Metrics](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-metrics.md): You can view the following metrics in Amazon CloudWatch:

### [Features](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-features.md)

Amazon Bedrock AgentCore Browser provides advanced features including CAPTCHA reduction, browser extensions, session profiles, proxy configuration, and OS-level interaction.

- [CAPTCHA Reduction](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-web-bot-auth.md)
- [Browser Extensions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-extensions.md): Browser Extensions allow you to install custom extensions into browser sessions at session creation time.
- [Browser Profiles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-profiles.md): Browser profiles enable you to persist and reuse browser profile data across multiple browser sessions.
- [Browser Proxies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-proxies.md): Amazon Bedrock AgentCore Browser supports routing browser traffic through your own external proxy servers.
- [Browser Enterprise Policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-enterprise-policies.md): Enterprise policies allow you to control browser behavior using the Chromium enterprise policy mechanism.
- [Root Certificate Authority](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-root-ca-certificates.md): By default, Amazon Bedrock AgentCore Browser sessions trust only publicly recognized certificate authorities.
- [Browser OS action](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-invoke.md): The InvokeBrowser API provides direct operating system-level control over Amazon Bedrock AgentCore Browser sessions.
- [File system configurations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-filesystem-configurations.md): AgentCore Browser supports mounting your own file systems into browser sessions through the filesystemConfigurations parameter.
- [Troubleshoot AgentCore Browser](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/browser-tool-troubleshooting.md): This section provides solutions to common issues you might encounter when using the Amazon Bedrock AgentCore Browser.


## [AgentCore Observability: Observe your agents and resources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability.md)

- [Get started with AgentCore Observability](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-get-started.md): Amazon Bedrock AgentCore Observability helps you trace, debug, and monitor agent performance in production environments.
- [Add observability to your agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-configure.md): Amazon Bedrock AgentCore provides a number of built-in metrics to monitor the performance of resources for the AgentCore runtime, memory, gateway, built-in tools, and identity resource types.
- [Observability concepts](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-telemetry.md): This section defines the concepts of sessions, traces and spans as they relate to monitoring and observability of agents.

### [AgentCore generated observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-service-provided.md)

For agents running in the AgentCore runtime, AgentCore automatically generates a set of session metrics which you can view in the Amazon CloudWatch Logs generative AI observability page.

- [Runtime observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-runtime-metrics.md): The runtime metrics provided by AgentCore give you visibility into your agent execution activity levels, processing latency, resource utilization, and error rates.
- [Memory observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-memory-metrics.md): For the AgentCore memory resource type, AgentCore outputs metrics to Amazon CloudWatch by default.
- [Payments observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-payments-metrics.md): AgentCore payments automatically generates spans and metrics for every data plane API call.
- [Gateway observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-gateway-metrics.md): The following sections describe the gateway metrics, logs, and spans output by AgentCore to Amazon CloudWatch.
- [Built-in tools observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-tool-metrics.md)
- [Identity observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-identity-metrics.md): This document described observability data emitted by the Bedrock AgentCore Identity Service.
- [Policy in AgentCore observability data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-policy-metrics.md): For policy and policy engine resource types, Amazon Bedrock AgentCore publishes invocation metrics to CloudWatch by default.
- [View metrics for your agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-view.md): After implementing observability in your agent, you can view the collected metrics and traces in both the CloudWatch console generative AI observability page and in CloudWatch Logs.
- [Cross-account monitoring](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/observability-cross-account.md): You can use Amazon CloudWatch cross-account observability to monitor Amazon Bedrock AgentCore resources across multiple AWS accounts from a single monitoring account.


## [Policy in AgentCore: Control Agent Interactions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy.md)

- [Getting started with Policy in AgentCore](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-getting-started.md): In this tutorial, you’ll learn how to set up Policy in AgentCore and integrate it with a Amazon Bedrock AgentCore Gateway using the AgentCore CLI.
- [Core concepts](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-core-concepts.md): Before using Policy in Amazon Bedrock AgentCore, it’s important to understand the key concepts and components that work together to provide policy-based governance for your AI agents.
- [AgentCore Gateway and Policy in AgentCore IAM Permissions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-permissions.md): This guide provides the required IAM permissions for using Amazon Bedrock AgentCore Gateway with Policy in AgentCore for fine-grained authorization control using Cedar policies.
- [Create a policy engine](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-create-engine.md): A policy engine is a collection of policies that evaluates and authorizes agent tool calls.

### [Create a policy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-create-policies.md)

Policy in Amazon Bedrock AgentCore uses Cedar as its authorization language to control access to tools and resources.

- [Understanding Cedar policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-understanding-cedar.md): Policy in AgentCore uses Cedar policies to control access to AgentCore Gateway tools.
- [Policy scope](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-scope.md): The scope defines what the policy applies to.
- [Policy conditions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-conditions.md): Conditions add fine-grained logic to policies using when and unless clauses:
- [Authorization flow](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-authorization-flow.md): Amazon Bedrock AgentCore Gateway evaluates Cedar policies against incoming requests.
- [Time-based policy support](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-time-based.md): Policy in AgentCore supports time-based restrictions in Cedar policies through the context.system.now datetime value.
- [Schema constraints](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-schema-constraints.md): Policies for Amazon Bedrock AgentCore Gateway must validate against a specific Cedar schema that is automatically generated from the Gateway’s MCP tool manifest.
- [Limitations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-limitations-section.md): Cedar policies and the current Amazon Bedrock AgentCore Gateway implementation have certain limitations that affect policy authoring and functionality.
- [Common policy patterns](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-common-patterns.md): These examples demonstrate frequently used Cedar policy patterns.
- [Getting started with guardrails](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-guardrails-getting-started.md): Guardrails let you add content filtering policies to your agent’s gateway.
- [Guardrails in policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-guardrails-in-policies.md): This section explains how to define Bedrock Guardrails in policy.

### [Temporal policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-temporal.md)

Policy in Amazon Bedrock AgentCore supports temporal policies: policies whose decisions depend on the history of an agent’s actions within a session, not on the current request alone.

- [Policy sessions and identity propagation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-session-based-temporal.md): With temporal policies, you can define rules based on past events that have occurred within a session, not just the current request.
- [Authoring temporal policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-temporal-authoring.md): You author a temporal policy in the Dogwood policy language and add it to a policy engine, the same way you create any other policy for Policy in AgentCore.
- [Writing policies in natural language](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-natural-language.md): Policy in AgentCore will automatically select the optimal region within your geography to process your inference requests made through Policy authoring service.

### [Validate and test policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-validate-policies.md)

Before deploying policies to production, Policy in AgentCore provides validation capabilities to catch errors and identify potential issues.

- [Test a policy in LOG_ONLY mode](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-test-a-policy.md): Using the policy-level enforcement mode, you can toggle between ACTIVE and LOG_ONLY to answer the question: "What would this policy do to my traffic if it was applied?" Per policy LOG_ONLY mode lets you test a policy on real traffic without affecting authorization decisions.
- [Validation and analysis overview](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-validation-overview.md)
- [Policy generation: per-policy validation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-generation-validation.md): When using the policy authoring service to generate policies from natural language, validation and analysis occur per individual policy during generation.
- [Policy create and update: per-policy engine validation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-create-update-validation.md): When creating or updating policies directly (not through generation), validation and analysis takes into account the new policy as well as its interactions with all preexisting policies in the policy engine.

### [Use policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-use-policies.md)

This section explains how to create and manage Cedar policies.

- [Add policies to the Policy Engine](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/add-policies-to-engine.md): You can create one or more policies in your policy engine to control how agents interact with your enterprise tools and data through Amazon Bedrock AgentCore Gateway.
- [Create gateway with Policy Engine](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/create-gateway-with-policy.md): This section provides examples of creating a gateway with a policy engine associated for policy enforcement.
- [Update existing gateway with Policy Engine](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/update-gateway-with-policy.md): Associate a policy engine with an existing gateway:
- [Policy enforcement modes](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-enforcement-modes.md): Enforcement mode defines how the gateway applies policy decisions.
- [Use an AgentCore Gateway with Policy in AgentCore](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/use-gateway-with-policy.md): Follow the gateway authorization and authentication guide to obtain the credentials needed for gateway access.
- [Manage Policies and Policy Engines](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/manage-policies-engines.md): Use these operations to manage your Policy Engines and policies.
- [Errors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-use-errors.md): Policy in AgentCore operations can return the following types of errors:
- [Example policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/example-policies.md): This section provides comprehensive examples of Cedar authorization policies for an insurance management system.

### [Advanced topics](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-advanced.md)

This chapter covers some advanced topics and additional information that can help supplement your knowledge of Policy in AgentCore and how you can use it effectively in your applications.

- [Customize your policy engine's encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-encryption.md): Policy in AgentCore provides encryption by default to protect sensitive customer data at rest using AWS owned encryption keys.


## [AgentCore Evaluations: Evaluate agent performance](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations.md)

### [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/how-it-works-evaluations.md)

Amazon Bedrock AgentCore Evaluations provides capabilities to assess the performance of AI agents.

- [Evaluation terminology](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations-terminology.md): Understanding key concepts and terminology is essential for effectively using AgentCore Evaluations.
- [Evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluators.md): Evaluators are the core components that assess your agent’s performance across different dimensions.
- [Evaluation types](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations-types.md): AgentCore Evaluations provides three evaluation types, which differ in when and how the evaluation is performed:
- [Telemetry setup](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-telemetry.md): Your agent emits spans that Amazon Bedrock AgentCore Evaluations uses to reconstruct each session.

### [Supported frameworks](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks.md)

Amazon Bedrock AgentCore Evaluations evaluates agents built with several agent frameworks.

- [Strands Agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-strands.md): This page explains how to instrument a Strands Agents agent, how spans are identified, and how evaluation fields are extracted.
- [LangGraph](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-langgraph.md): This page explains how to instrument a LangGraph agent, how spans are identified, and how evaluation fields are extracted.
- [OpenAI Agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-openai-agents.md): This page explains how to instrument an OpenAI Agents agent, how spans are identified, and how evaluation fields are extracted.
- [Vercel AI SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-vercel-ai.md): This page explains how to instrument a Vercel AI SDK agent, how spans are identified, and how evaluation fields are extracted.
- [LlamaIndex](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-llamaindex.md): This page explains how to instrument a LlamaIndex agent, how spans are identified, and how evaluation fields are extracted.
- [Google ADK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-google-adk.md): This page explains how to instrument a Google Agent Development Kit (ADK) agent, how spans are identified, and how evaluation fields are extracted.
- [Claude Agent SDK](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-claude-agent-sdk.md): This page explains how to instrument a Claude Agent SDK agent, how spans are identified, and how evaluation fields are extracted.
- [Generic framework support](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/supported-frameworks-generic.md): Amazon Bedrock AgentCore Evaluations reads telemetry through two open standards: the OpenTelemetry generative AI semantic conventions and the OpenInference semantic conventions.

### [Built-in evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/built-in-evaluators-overview.md)

Built-in evaluators in AgentCore Evaluations provide pre-configured evaluators for assessing your agents.

- [Cross region inference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations-cross-region-inference.md): AgentCore Evaluations will automatically select the optimal region within your geography to process your inference requests.
- [Skill evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/skill-evaluators.md): A skill is a reusable SKILL.md instruction file that an agent loads at runtime to help with a task.
- [Prompt templates](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/prompt-templates-builtin.md): Each prompt template contains at least one placeholder, which is replaced with actual trace information before it is sent to the judge model.
- [Third-party evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/third-party-evaluators.md): AgentCore Evaluations offers evaluators from the DeepEval and AutoEval open source libraries.

### [Custom evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/custom-evaluators.md)

Custom evaluators in AgentCore Evaluations allow you to define your own evaluator model, evaluation instruction and scoring schemas.

- [Create evaluator](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/create-evaluator.md): The CreateEvaluator API creates a new custom evaluator that defines how to assess specific aspects of your agent’s behavior.
- [List evaluators](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/list-evaluators.md): The ListEvaluators API returns a paginated list of all custom evaluators in your account and Region, including both your custom evaluators and built-in evaluators.
- [Update evaluator](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/update-evaluator.md): The UpdateEvaluator API modifies an existing custom evaluator’s configuration, description, or evaluation level.
- [Get evaluator](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/get-evaluator.md): The GetEvaluator API retrieves complete details of a specific custom or built-in evaluator including its configuration, status, and lock state.
- [Delete evaluator](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/delete-evaluator.md): The DeleteEvaluator API permanently removes a custom evaluator and all its configuration data.
- [Custom code-based evaluator](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-based-evaluators.md): Custom code-based evaluators let you use your own AWS Lambda function to programmatically evaluate agent performance, instead of using an LLM as a judge.

### [Online evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/online-evaluations.md)

An online evaluation configuration is a resource that defines how your agent is evaluated, including which evaluators to apply, which data sources to monitor, and evaluation parameters.

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations-prerequisites.md): Before you begin using Amazon Bedrock AgentCore Evaluations, ensure you have the necessary AWS permissions and service roles configured.
- [Create and deploy your agent](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/create-deploy-agent.md): If you have an agent already up and running in AgentCore Runtime, you can skip the following steps
- [Create online evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/create-online-evaluations.md): The CreateOnlineEvaluationConfig API creates a new online evaluation configuration that continuously monitors your agent’s performance using live traffic.
- [Get online evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/get-online-evaluations.md): The GetOnlineEvaluationConfig API retrieves the complete details and current status of an existing online evaluation configuration.
- [List online evaluations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/list-online-evaluations.md): The ListOnlineEvaluationConfigs API retrieves a paginated list of all online evaluation configurations in your account and Region.
- [Update online evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/update-online-evaluations.md): The UpdateOnlineEvaluationConfig API modifies an existing online evaluation configuration, allowing you to change evaluators, data sources, execution settings, and other parameters.
- [Delete online evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/delete-online-evaluations.md): The DeleteOnlineEvaluationConfig API permanently removes an online evaluation configuration and stops all associated evaluation processing.
- [Results and output](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/results-and-output.md): Online evaluation results are automatically saved to Amazon CloudWatch.

### [On-demand evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/on-demand-evaluations.md)

On-demand evaluation provides a flexible way to evaluate specific agent interactions by directly analyzing a chosen set of spans.

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ondemand-evaluations-prereqs.md): Before you run on-demand evaluations, make sure the following are in place.
- [Getting started with on-demand evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/getting-started-on-demand.md): Follow these steps to set up and run your first on-demand evaluation.
- [Ground truth evaluations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ground-truth-evaluations.md): Ground truth is the known correct answer or expected behavior for a given input — the "gold standard" you compare actual results against.

### [Batch evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations.md)

Batch evaluation runs evaluators against multiple agent sessions in a single job with server-side orchestration.

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-prereqs.md): Before you can run batch evaluations, make sure the following are in place.
- [Getting started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-getting-started.md): This walkthrough takes you from a deployed agent to batch evaluation results using an Acme Store customer support agent.
- [Start batch evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-start.md): Start a batch evaluation to run evaluators against multiple agent sessions.
- [Get batch evaluation results](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-get.md): Retrieve the status and results of a batch evaluation job.
- [List batch evaluations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-list.md): List all batch evaluation jobs in your account.
- [Stop batch evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-stop.md): Stop a running batch evaluation job.
- [Delete batch evaluation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-delete.md): Delete a batch evaluation job and its associated metadata.
- [Understanding results and output](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-results.md): Batch evaluation results come in two layers: aggregate summaries in the API response, and per-session detail in CloudWatch Logs.
- [Batch evaluation encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/batch-evaluations-encryption.md): When you specify a kmsKeyArn on a batch evaluation, the service encrypts all output artifacts stored in S3 using S3 server-side encryption with KMS (SSE-KMS).

### [Dataset evaluation (Preview)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/dataset-evaluations.md)

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-prereqs.md): Before you can manage datasets, make sure the following are in place.
- [Getting started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-getting-started.md): This topic provides an end-to-end workflow for creating, populating, and publishing a dataset.
- [Dataset schema](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/dataset-evaluations-schema.md): A dataset contains one or more scenarios.
- [Manage datasets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-manage.md): This topic covers creating, retrieving, listing, updating, and deleting datasets.
- [Manage examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-examples.md): After a dataset reaches ACTIVE status, you can add, update, delete, and list examples in the Draft.
- [Manage versions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-versions.md): Use CreateDatasetVersion to publish the current Draft as an immutable numbered version.
- [Dataset encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/datasets-encryption.md): When you specify a kmsKeyArn on a dataset, the service encrypts all stored examples using S3 server-side encryption with KMS (SSE-KMS).
- [On-demand dataset runner](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/dataset-evaluations-on-demand.md): The OnDemandEvaluationDatasetRunner orchestrates the entire evaluation lifecycle client-side: invoke the agent, wait for telemetry ingestion, collect spans from CloudWatch, and call the Evaluate API, all in a single run() call.
- [Batch dataset runner](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/dataset-evaluations-batch.md): The BatchEvaluationRunner delegates span collection and evaluation entirely to the service via the StartBatchEvaluation and GetBatchEvaluation APIs.

### [Simulation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/simulation.md)

Simulation lets you evaluate your agent against dynamic, multi-turn conversations generated by LLM-backed actors.

- [User simulation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/user-simulation.md): User simulation uses an LLM-backed actor to play the role of an end user interacting with your agent.

### [Diagnose with AI assistant](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/diagnose-evaluation-issues.md)

If your AgentCore Evaluation configuration isn’t producing results — or if you’re seeing errors like LogEventMissingException, AgentSpanMappingException, or empty evaluation scores — you can use the AgentCore Evaluation Diagnostic Skill to troubleshoot the issue yourself.

- [Skill source](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/diagnose-evaluation-skill-source.md): The following is the full source of the AgentCore Evaluation Diagnostic Skill.
- [Data encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/evaluations-encryption.md)


## [AgentCore optimization](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/optimization.md)

- [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/optimization-how-it-works.md): AgentCore optimization connects evaluation findings to validated improvements through a repeatable cycle.
- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/optimization-prereqs.md): Before using AgentCore optimization features, make sure the following are in place.

### [Configuration bundles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles.md)

A configuration bundle is a versioned, immutable snapshot of your agent’s dynamic configuration — system prompts, model IDs, tool descriptions, and any other key-value pairs your agent reads at runtime.

- [Getting started](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-getting-started.md): This walkthrough takes you from zero to a versioned configuration bundle that your agent reads at runtime.
- [Create a bundle](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-create.md): Create a configuration bundle to store a versioned snapshot of your agent’s dynamic configuration.
- [Update a bundle](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-update.md): Update a configuration bundle to create a new immutable version with changed configuration.
- [Get a bundle](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-get.md): Retrieve a configuration bundle to inspect its metadata or read the full configuration content of a specific version.
- [List bundles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-list.md): List configuration bundles in your account, or list versions of a specific bundle.
- [Delete a bundle](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-delete.md): Delete a configuration bundle and all of its versions.
- [Use at runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-runtime.md): Your agent reads configuration from a bundle at runtime to apply dynamic settings without redeploying code.
- [Configuration bundle encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/configuration-bundles-encryption.md): When you specify a kmsKeyArn on a configuration bundle, the service encrypts the component configurations (system prompts, tool descriptions, and other configuration content) using envelope encryption.

### [Recommendations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/optimization-recommendations.md)

Recommendations use AI to generate optimized agent configurations from real session traces.

- [System prompt recommendation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-system-prompt.md): Start a recommendation to generate an optimized system prompt for your agent.
- [Tool description recommendation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-tool-description.md): Start a recommendation to generate optimized tool descriptions for your agent.
- [Get recommendation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-get.md): Retrieve the status and results of a recommendation.
- [List recommendations](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-list.md): List all recommendations in your account.
- [Delete recommendation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-delete.md): Delete a recommendation and its associated metadata.
- [Recommendation encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/recommendations-encryption.md): When you specify a kmsKeyArn on a recommendation, the service encrypts the recommendation configuration and recommendation result using envelope encryption with the AWS Encryption SDK.

### [A/B testing](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing.md)

A/B testing splits live production traffic between two variants and continuously evaluates performance with statistical significance.

- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing-prereqs.md): Before you create an A/B test, ensure the following resources are in place.
- [Target-based A/B test](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing-target-based.md): Use the target-based routing pattern when the change you are testing involves code changes, a framework upgrade, or an entirely different agent implementation.
- [Configuration bundle A/B test](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing-config-bundle.md): Use the configuration bundle pattern when the change you are testing is purely configuration — a different system prompt, a different model ID, or different tool descriptions.
- [A/B test for external agents](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing-3p-agents.md): You can A/B test an agent that runs outside an AgentCore Runtime with an agent hosted anywhere, for example on AWS Lambda, Amazon EKS, or Amazon ECS.
- [Manage an A/B test](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/ab-testing-manage.md): Update an A/B test to start it, pause it, or stop it.

### [Insights (preview)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights.md)

- [How it works](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights-how-it-works.md): AgentCore insights answers three questions about your agent’s production behavior: Why is it failing? What are users asking for? and How is it solving problems?
- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights-prerequisites.md): Before you begin using AgentCore insights, ensure you have the following:
- [One-time report](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights-one-time-report.md): Use StartBatchEvaluation to run an on-demand insights analysis over your agent’s sessions.
- [Recurring report](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights-recurring-report.md): Create an online evaluation configuration with insights and a clustering schedule.
- [Generate recommendation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/insights-generate-recommendation.md): After reviewing your insights results, you can use the same agent traces to generate an improved system prompt.


## [AWS Agent Registry: Centrally catalog and discover AI Resources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry.md)

- [Key capabilities](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-key-capabilities.md)
- [Concepts and terminology](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-concepts.md)
- [Prerequisites](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-prerequisites.md)
- [Sample use cases](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-use-cases.md)
- [Get started with AWS Agent Registry](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-get-started.md)

### [Creating and managing registries](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-managing-registries.md)

A registry is the top-level resource in AWS Agent Registry.

- [Supported Inbound Authorization types](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-supported-auth-types.md)
- [Create and manage registries](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-create-manage.md)

### [Creating and managing registry records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-managing-records.md)

Registry records represent the individual resources published into a registry.

- [Supported record types and descriptors](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-supported-record-types.md)
- [Record lifecycle](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-record-lifecycle.md)
- [Create and manage records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-create-manage-records.md)
- [Synchronize records from external sources](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-sync-records.md)

### [Curating the registry](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-curating.md)

Curators are the quality gatekeepers of the registry.

- [Reviewing registry records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-reviewing-records.md)
- [Deprecating registry records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-deprecating-records.md)
- [Notifications for pending approvals](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-notifications-approvals.md)

### [Discovering the registry](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-searching.md)

As a consumer, you can discover MCP servers, agents, skills, and other resources that have been approved and published to the registry.

- [Search for registry records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-search-records.md)
- [Browse approved records](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-browse-records.md)
- [Using the Registry MCP endpoint](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-mcp-endpoint.md)
- [Notifications (Amazon EventBridge)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-eventbridge.md)
- [AWS Organizations integration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-organizations.md): AWS Agent Registry integrates with AWS Organizations so that you can automatically catalog supported resources across your organization’s member accounts in a single registry.
- [Cross-account sharing (RAM)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-cross-account-sharing.md): You can share an AWS Agent Registry registry with other AWS accounts using AWS Resource Access Manager (RAM).

### [Log Registry API calls with AWS CloudTrail](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-cloudtrail.md)

AWS Agent Registry control plane API calls are logged in AWS CloudTrail, providing a complete audit trail of who did what and when.

- [AWS CloudTrail integration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-cloudtrail-integration.md)
- [VPC and AWS PrivateLink](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-privatelink.md): You can use AWS PrivateLink to create a private connection between your VPC and AWS Agent Registry.
- [IAM Permissions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-iam-permissions.md)

### [Data protection](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-data-protection.md)

The AWS shared responsibility model applies to data protection in AWS Agent Registry.

- [Data encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-data-encryption.md): Data encryption typically falls into two categories: encryption at rest and encryption in transit.
- [Set customer managed key policy](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-kms-key-policy.md): To use a customer managed key with AWS Agent Registry, you must configure both an IAM policy for the calling principal and a KMS key policy that allows the service to perform encryption and decryption operations.
- [Configure KMS key for a registry](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-configure-encryption.md): The KMS key determines how your registry encrypts data at rest.
- [Cross-region inference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-cross-region-inference.md): As part of enabling semantic search, AWS Agent Registry automatically selects the optimal Region to process the embedding model inference request, maximizing available compute resources and model availability.
- [Service-linked roles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/using-service-linked-role-agent-registry.md)
- [Troubleshooting](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-troubleshooting.md)
- [Registry migration guide](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/registry-faq.md): AWS Agent Registry — Migrating to the new agent-registry namespace


## [Security](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security.md)

### [Data protection](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/data-protection.md)

The AWS shared responsibility model applies to data protection in Amazon Bedrock AgentCore.

- [Data encryption](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/data-encryption.md)

### [VPC and AWS PrivateLink](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/vpc.md)

You can use Amazon Virtual Private Cloud (Amazon VPC) and AWS PrivateLink to create private connections between your VPC and Amazon Bedrock AgentCore.

- [Use AWS PrivateLink to create a private connection](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/vpc-interface-endpoints.md): You can use AWS PrivateLink to create a private connection between your VPC and Amazon Bedrock AgentCore.
- [Configure Gateway VPC Egress](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-vpc-egress.md): The AgentCore Gateway service provides secure and controlled egress traffic management for your applications, enabling seamless communication with resources within your Virtual Private Cloud (VPC).
- [VPC egress with VPC Lattice](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/vpc-egress-private-endpoints.md): Amazon Bedrock AgentCore supports private connectivity to resources hosted inside your AWS VPC or on-premises environments connected to your VPC, such as private MCP servers, internal REST APIs, or databases, without exposing those services to the public internet.
- [Configure AgentCore Runtime and built-in tools VPC configuration](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agentcore-vpc.md): You can configure Amazon Bedrock AgentCore Runtime and built-in tools (Code Interpreter and Browser Tool) to connect to resources in your Amazon Virtual Private Cloud (VPC).
- [Use VPC condition keys](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-vpc-condition.md): Use Amazon Bedrock AgentCore-specific condition keys for VPC settings to more precisely control permissions for your AgentCore resources.
- [Cross-region inference](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/cross-region-inference.md): With cross-region inference, Amazon Bedrock AgentCore Memory, Policy in AgentCore, and AgentCore Evaluations will automatically select the optimal region (as described in more detail below) to process your inference request, maximizing available compute resources and model availability, and providing the best customer experience.

### [Identity and access management](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-iam.md)

AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources.

- [How Amazon Bedrock AgentCore works with IAM](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security_iam_service-with-iam.md): Before you use IAM to manage access to AgentCore, learn what IAM features are available to use with AgentCore.
- [Use condition keys with AgentCore Gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-gateway-condition-keys.md): Use Amazon Bedrock AgentCore-specific condition keys to control how you create and configure gateways and gateway targets in your organization.
- [Identity-based policy examples](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security_iam_id-based-policy-examples.md): By default, users and roles don’t have permission to create or modify AgentCore resources.
- [AWS managed policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-iam-awsmanpol.md): An AWS managed policy is a standalone policy that is created and administered by AWS.
- [Service-linked roles](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/service-linked-roles.md): Amazon Bedrock AgentCore uses AWS Identity and Access Management (IAM) service-linked roles.
- [Credentials Management](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security-credentials-management.md)
- [Troubleshooting](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/security_iam_troubleshoot.md): Use the following information to help you diagnose and fix common issues that you might encounter when working with AgentCore and IAM.

### [Runtime Instances and capacity providers](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances.md)

The Instances compute type runs your agents on AWS managed Amazon EC2 infrastructure in your own AWS account, provisioned through a capacity provider.

- [Security model and permissions](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-security.md): When you host agents on the Instances compute type, your agents run on Amazon EC2 instances in your own AWS account.
- [Encryption at rest](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-encryption.md): When you host agents on the Instances compute type, your data at rest lives on the Amazon EBS volumes that a capacity provider attaches to your sessions.
- [Manage your data](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-data-management.md): When you host agents on the Instances compute type, your data is stored on Amazon EBS volumes in your own AWS account.
- [Resource-based policies](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/resource-based-policies.md): Resource-based policies in Amazon Bedrock AgentCore allow you to control which principals (AWS accounts, IAM users, or IAM roles) can invoke and manage your Amazon Bedrock AgentCore resources (currently supported for Runtime, Gateway and Memory).
- [Compliance validation](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/compliance-validation.md): Amazon Bedrock AgentCore is HIPAA eligible and FedRAMP (Class C and Class D), SOC 2 and ISO (27001:2022, 27017:2015, 27018:2019, 27701:2019, 22301:2019, 20000-1:2018, 9001:2015) and CSA STAR compliant.
- [Resilience](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/disaster-recovery-resiliency.md): The AWS global infrastructure is built around AWS Regions and Availability Zones.
- [Cross-service confused deputy prevention](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/cross-service-confused-deputy-prevention.md): The confused deputy problem is a security issue where an entity that doesn’t have permission to perform an action can coerce a more-privileged entity to perform the action.


## Full content

The entire guide is also available as a single markdown file, useful for feeding the full guide to an LLM in one pass:

- [Complete guide (single file)](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/full.md)
