◈ AWS AGENTCORE BLUEPRINTS
PART I · FOUNDATIONS · CHAPTER 02 / 36
TOCCONSULTING.FR
AMAZON BEDROCK AGENTCORE / READ ME FIRST

KEY TERMS, IN PLAIN LANGUAGE

CHAPTER 02 / 36
FOR humans, no jargon assumed
REV 2026.07

Every other chapter uses these words. Read this once and the rest will make sense. Each term has a one-line meaning and, where it helps, a simple comparison.

[ THE BASICS ]
Agent
A program that uses an AI model to reach a goal. It can decide what to do, call tools, and use the results, not just reply with text.
Modelthe LLM
The AI "brain" (for example Anthropic Claude) that reads, reasons, and writes. It does not act by itself. The agent gives it tools.
Tool
Anything the agent can call to do real work or fetch real data: a function you wrote, an API, a database query, a web search. Think of tools as the agent's hands.
Agent framework
A code library for building agents: Strands, LangGraph, CrewAI, LlamaIndex, Google ADK. It wires the model, the instructions, and the tools together.
The agentic loop
The repeating cycle an agent runs: the model thinks, calls a tool, reads the result, thinks again, and so on, until it has a final answer.
Session
One continuous run or conversation, named by a session id. Like a single phone call. Reusing the id continues the same conversation.
[ RUNNING IT ON AWS ]
Serverless
You run and manage no servers. AWS starts, scales, and stops the compute for you, and you pay only for what you use.
Container image
A sealed package of your code plus everything it needs to run. AgentCore can run your agent from a container image, or from directly deployed code (a zip).
ARM64AWS Graviton
The processor type AgentCore runs on. Your container image must be built for ARM64, or it will not start.
microVM
A tiny, private virtual computer created for one session, with its own CPU, memory, and disk. One user's data cannot leak into another's. It is destroyed and its memory wiped when the session ends (by default; optional session storage can keep files). Like a private, single-use room.
/ping health check
A small status endpoint AgentCore calls to ask "are you healthy, and are you busy?" If an agent doing long work does not answer "busy," it is treated as idle and stopped.
Session replay
A recording of a Browser session (pages visited, clicks, actions) you can watch back later, like a screen recording, to see exactly what the agent did.
[ CONNECTING, THE TWO PROTOCOLS ]
MCPModel Context Protocol
An open standard for how an agent finds and calls tools. Like a universal plug (think USB) so any agent can use any MCP tool.
A2AAgent-to-Agent
An open standard for how one agent talks to another agent to hand off or share work, even across different companies. A shared language for agents to collaborate.
Namespace
A folder-like path that organizes an agent's long-term memories, so they are easy to find, filter, and control.
Gatewayan AgentCore service
Turns your existing APIs and AWS Lambda functions into MCP tools, behind one secure address, so agents can use them without custom glue code.
[ SECURITY AND OPERATIONS ]
IAM
AWS's permission system: who or what may do which actions. Least privilege means granting only the access actually needed.
OAuth scope
The exact permissions a login token grants (for example, "read your calendar"). Too broad a scope hands over more access than necessary.
KMSKey Management Service
AWS's service for encryption keys. A customer-managed key means you own and control the key that encrypts your data.
Trace and spanobservability
A record of what the agent did. A trace is one whole request. A span is one step inside it (a model call, a tool call). Like a flight recorder for debugging.
[ MONEY ]
x402
An open web payment standard (it reuses the HTTP "402 Payment Required" response) that lets software make tiny automatic payments for paid services. Note: this is real money, not the "tokens" an LLM processes.
Multi-modal
Able to handle more than text: images, audio, files, not just words.
The big picture: chapter 01, Overview. Then read each service chapter in order.
DRAWN 2026.06, REV 2026.07.26
◄ PREVIOUS · CH 01
AgentCore Overview, Plain Language
NEXT · CH 03 ►
AgentCore, Common Mistakes Explained
AWS AGENTCORE BLUEPRINTS · CONTENTS
Back to tocconsulting.fr Cover & Table of Contents
PART I · FOUNDATIONS
01AgentCore Overview, Plain LanguageCONCEPT02AgentCore, Key Terms in Plain LanguageCONCEPT03AgentCore, Common Mistakes ExplainedCONCEPT04Inside an AgentCore Agent, BlueprintCONCEPT05Harness, Practical 1, Strands PathPRACTICAL06Harness, Practical 2, Managed HarnessPRACTICAL
PART II · CORE SERVICES
07AgentCore Runtime, Plain LanguageCONCEPT08AgentCore Runtime, PracticalPRACTICAL09AgentCore Memory, Plain LanguageCONCEPT10AgentCore Memory, PracticalPRACTICAL11AgentCore Gateway, Plain LanguageCONCEPT12AgentCore Gateway, PracticalPRACTICAL13AgentCore Identity, Plain LanguageCONCEPT14AgentCore Identity, PracticalPRACTICAL
PART III · TOOLS AND OPERATIONS
15AgentCore Code Interpreter, Plain LanguageCONCEPT16AgentCore Code Interpreter, PracticalPRACTICAL17AgentCore Browser, Plain LanguageCONCEPT18AgentCore Browser, PracticalPRACTICAL19AgentCore Observability, Plain LanguageCONCEPT20AgentCore Observability, PracticalPRACTICAL21AgentCore Evaluations, Plain LanguageCONCEPT22AgentCore Evaluations, PracticalPRACTICAL
PART IV · GOVERNANCE AND TRANSACTIONS
23AgentCore Policy, Plain LanguageCONCEPT24AgentCore Policy, PracticalPRACTICAL25AgentCore Registry, Plain LanguageCONCEPT26AgentCore Registry, PracticalPRACTICAL27AgentCore Payments, Plain LanguageCONCEPT28AgentCore Payments, PracticalPRACTICAL
PART V · MULTI-AGENT AND ARCHITECTURE
29A2A and Multi-Agent, Plain LanguageCONCEPT30A2A and Multi-Agent, PracticalPRACTICAL31Architecture Patterns, Plain LanguageCONCEPT32Multi-Tenant Agents, Plain LanguageCONCEPT33Agent Security and Threat Model, Plain LanguageCONCEPT34Governance at Org Scale, Plain LanguageCONCEPT35Governance at Org Scale, PracticalPRACTICAL36Multi-Region and Distribution, Plain LanguageCONCEPT