AWS Certified Generative AI Developer – Professional
Amazon Bedrock AgentCore services explained for AIP-C01
AgentCore is a set of separate services for running agents. Runtime hosts agent code you wrote in any framework, the harness runs a managed agent loop from configuration, Identity holds and vends credentials, Gateway turns APIs into MCP tools and proxies LLM calls, and Code Interpreter and Browser are sandboxed tools.
Runtime vs harness
AgentCore Runtime is serverless hosting for code you bring. You wrap the agent, written in any framework or none, with the AgentCore SDK's BedrockAgentCoreApp entrypoint, package it as an ARM64 container, push it to Amazon ECR and deploy. The orchestration loop is yours. Runtime provides isolation, scaling, sessions, inbound auth (IAM SigV4 or OAuth) and observability plumbing.
The AgentCore harness provides the loop itself, powered by Strands Agents. You declare the model, system prompt, tools and limits as configuration. The harness does not support a choice of agent framework or graph and workflow patterns.
Example: a LangGraph claims agent with a fixed four-step graph keeps its code on Runtime. Moving it to the harness would mean replacing the graph with the harness's own loop.
Identity
AgentCore Identity manages credentials for agents. Its credential management separates credential storage from credential access, so agents never have direct access to long-term secrets or refresh tokens. It supports OAuth2 access tokens, API keys and other credential types.
Example: a scheduling agent that acts in each employee's SaaS calendar uses an OAuth2 credential provider in AgentCore Identity and asks it for that employee's access token, instead of storing refresh tokens itself.
Gateway, tools and the rest
Gateway converts APIs, Lambda functions and existing services into MCP-compatible tools and connects to existing MCP servers. Inference targets on a gateway route LLM traffic: clients call one endpoint, for example with the OpenAI SDK, and switch models by changing the model string. The gateway authenticates to providers and can apply Amazon Bedrock Guardrails to every LLM call regardless of provider.
Code Interpreter runs agent-written code in an isolated sandbox with pre-built runtimes for Python, JavaScript and TypeScript, so calculations come from executed code rather than model text. Browser is a managed cloud browser for agents to navigate websites and fill forms.
Memory gives short-term memory for multi-turn conversations and long-term memory across sessions. Policy intercepts tool calls through Gateway and checks them against rules written in natural language or a Cedar-compatible policy language. Evaluations scores agent sessions, traces and spans. Observability shows each step of an agent's execution.
Where the exam catches people
- Believing the harness can run your existing LangGraph graph: the harness has no choice of framework and no graph patterns. Runtime hosts your own code.
- Believing the agent should store each user's refresh token in Secrets Manager: AgentCore Identity holds the tokens and vends access tokens to the agent.
- Believing a JWT authorizer on the runtime gives the agent access to a third-party API: that is inbound auth. Calling the third party on the user's behalf is outbound auth through an Identity credential provider.
- Believing the Browser tool is the way to do accurate arithmetic on a file: Code Interpreter runs generated code in a sandbox for that.