SVS317: Integrating AI agents with event-driven architectures

Resources for SVS317: Integrating AI agents with event-driven architectures

Multi-agent systems call each other synchronously by default, so one slow agent blocks the chain, failures are hard to replay and debugging across agents gets hard. In this chalk talk we took a travel concierge with a trip agent and flight, hotel and ground agents, and moved its calls to an event bus: labelling each call now, later or never, triggering agents from events, pausing and resuming them for long-running work and human approval, and handling the parts that fail.

This page has the slides and links for each topic of the session.

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.

Now, later, never

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.

Long-running agents: who holds the call

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.

Event-driven architectures

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.

Asynchronous systems and event-driven architecture for global scale

re:Invent 2022 keynote, Dr. Werner Vogels

Building next-gen applications with event-driven architectures

re:Invent 2022, API311-R

Event-driven architectures at scale: manage millions of events

re:Invent 2024, API307

Human in the loop with events

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.

When things fail

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.

Seeing what agents do

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.

Try it yourself

GitHub repo

AWS Step Functions orchestrates Strands agents on Amazon Bedrock AgentCore and pauses and resumes them with callback tokens.

Build, deploy, and operate agentic architectures on AWS Serverless

Previous re:Invent session: 2025, CNS359

Building intelligent workflows with event-driven AI

Previous re:Invent session: 2025, MAM327

Building AI agents with serverless, Strands, and MCP

Previous re:Invent session: 2025, NTA405

Improve agent quality in production with Amazon Bedrock AgentCore Evaluations

Previous re:Invent session: 2025, AIM3348

Using multiple agents for scalable generative AI applications

Previous re:Invent session: 2024, AIM304

Presented by:

Marco Jahn

Marco Jahn

Senior Solutions Architect - ISV, Amazon Web Services

Follow on LinkedIn

Tolga Orhon

Tolga Orhon

Senior Technical Account Manager at AWS, helping people to keep things running. I enjoy Serverless, Event Driven Architectures, Operational Excellence and Optimization.

Follow on LinkedIn