
Sync or async between agents
If the caller needs the answer in this turn, call and wait. If it can come later, send a request with a correlation ID. If nobody needs to answer, publish a fact as an event.
Amazon EventBridge
An event starts an agent, an agent publishes a fact, and other agents subscribe to it, replay it or wait for it without knowing who produced it.
Pause and resume
When an agent runs for minutes or hours, something holds the token that resumes the caller: an AWS Step Functions task token, an AWS Lambda durable functions callback, or a completion event the agent emits itself.
The foundations
The event-driven basics this session builds on: producers and consumers that don't know about each other, with an event bus between them.
re:Invent 2022 keynote, Dr. Werner Vogels
re:Invent 2022, API311-R
re:Invent 2024, API307
The approval is another event
When the hotel agent goes over budget, the workflow sends an approval request with its token, waits without using compute, and resumes when the matching answer comes back.
Delivery, the business step, the agent
Agents run on the same at-least-once delivery as any event-driven system, so make every step safe to retry and give every multi-step booking a way to undo itself.
Tracing and evaluation
A failed delivery shows up in the logs, a wrong answer from an agent does not. Trace every hop, log the bus and score agent output.
GitHub repo
AWS Step Functions orchestrates Strands agents on Amazon Bedrock AgentCore and pauses and resumes them with callback tokens.
Previous re:Invent session: 2025, CNS359
Previous re:Invent session: 2025, MAM327
Previous re:Invent session: 2025, NTA405
Previous re:Invent session: 2025, AIM3348
Previous re:Invent session: 2024, AIM304
Agents and multi-agent patterns
The loop, then the team
An agent is a model in a loop with tools, data and memory. The common multi-agent patterns call each other synchronously by default.