Amazon Bedrock AgentCore mindmap

Amazon Bedrock AgentCore

Agentic platform to build, deploy and operate agents securely at scale, with any framework and any model

• Harness: Managed agent loop you configure with a model, instructions and tools
• Runtime: Serverless hosting for agents and tools
  • Framework and model agnostic: Host agents built with LangGraph, Strands, CrewAI or custom code, using any model
  • Session isolation: Each session runs in its own microVM with isolated CPU, memory and file system
  • Long-running sessions: Up to 8 hours on microVMs, up to 14 days on Instances
  • Protocols: HTTP, MCP, A2A and AG-UI
  • Streaming: Streamed responses and bidirectional streaming
  • Deployment: Container image or direct code deployment
  • Versions and endpoints: Immutable versions, with endpoints that point to them
  • Consumption-based pricing: Pay for the resources actually consumed during a session
• Memory: Managed memory for context-aware agents
  • Short-term memory: Raw events within a session
  • Long-term memory: Structured information extracted across sessions by memory strategies
  • Built-in strategies: User preferences, semantic, session summaries and episodic
  • Custom strategies: Built-in overrides or self-managed pipelines
  • Namespaces: Organize records per actor or session for scoped retrieval
• Gateway: Turns APIs and services into MCP-compatible tools
  • Targets: Lambda, API Gateway stages, OpenAPI, Smithy, MCP servers and built-in templates
  • MCP endpoint: Agents list and call tools over the Model Context Protocol
  • Semantic tool search: Find the right tool with a natural language query
  • Inbound auth: JWT or IAM, or authorization offloaded to another component
  • Outbound auth: Gateway service role (SigV4), caller IAM credentials, OAuth or API keys
• Identity: Agent identity, access and credential management
  • Inbound auth: Who may call your agent or gateway: a JWT from your identity provider, or IAM
    • Amazon Cognito: A Cognito user pool as the identity provider and authorization server for Runtime and Gateway
    • Microsoft Entra ID: Your Microsoft Entra ID tenant as the identity provider and authorization server for Runtime and Gateway
    • Okta: Okta as the identity provider for Runtime and Gateway, or as an outbound credential provider
    • Auth0 by Okta: Auth0 as the identity provider for Runtime and Gateway, or as an outbound credential provider
    • Any OAuth 2.0 provider: The authorizer is provider agnostic: any OIDC or OAuth 2.0 provider with a discovery URL works
  • Outbound auth: Credential providers that let agents reach other services with OAuth tokens or API keys
    • Amazon Cognito: Get tokens for resources that Cognito authorizes
    • Microsoft Entra ID: Get tokens for resources that Microsoft Entra ID authorizes
    • Identity platforms: Built-in credential providers for identity and access platforms
      • Okta: Built-in outbound credential provider
      • Auth0 by Okta: Built-in outbound credential provider
      • Ping Identity (PingOne): Built-in outbound credential provider
      • OneLogin: Built-in outbound credential provider
      • CyberArk: Built-in outbound credential provider
      • FusionAuth: Built-in outbound credential provider
    • Work apps: Built-in credential providers for productivity, developer and business apps
      • Google: Built-in outbound credential provider
      • GitHub: Built-in outbound credential provider
      • Slack: Built-in outbound credential provider
      • Atlassian: Built-in outbound credential provider
      • Salesforce: Built-in outbound credential provider
      • HubSpot: Built-in outbound credential provider
      • Notion: Built-in outbound credential provider
      • Dropbox: Built-in outbound credential provider
      • Zoom: Built-in outbound credential provider
    • Social and media: Built-in credential providers for social and media platforms
      • Facebook: Built-in outbound credential provider
      • LinkedIn: Built-in outbound credential provider
      • X: Built-in outbound credential provider
      • Reddit: Built-in outbound credential provider
      • Spotify: Built-in outbound credential provider
      • Twitch: Built-in outbound credential provider
      • Yandex: Built-in outbound credential provider
    • API keys: API key credential providers, stored in the token vault
  • Token vault: Encrypted storage for OAuth tokens, client credentials and API keys
  • Workload identity: A unique identity per agent in the agent identity directory
• Built-in tools: Managed tools agents can call
  • Code Interpreter: Runs agent-generated code in an isolated sandbox
  • Browser: Managed, isolated browser for agents, with Live View and session replay
• Observability: Traces, metrics and logs for agents
  • OpenTelemetry: Standard telemetry format that works with your existing monitoring stack
  • CloudWatch dashboards: Trace visualizations, custom span metrics and error breakdowns for agent runtime data
• Policy: Deterministic rules that limit what agents can do with tools
• Evaluations: Automated quality scoring for agents and tools
• Registry: AWS Agent Registry, a catalog of agents, MCP servers, tools and skills
• Payments: Microtransaction payments for agents that use paid APIs and content
• Security
  • VPC connectivity: VPC configuration for Runtime and the built-in tools
  • Private endpoints: Interface VPC endpoints through AWS PrivateLink
  • Audit: Gateway and Registry API calls recorded in CloudTrail