Agentic AI · Hands-on for developers

Your developers build a working multi-agent system in one day.

A guided run through the AWS workshop Once Upon Agentic AI: Strands Agents, custom tools, MCP servers and agent-to-agent communication on Amazon Bedrock. Every chapter runs on the attendees' machines, and I explain where the SDKs have moved on.

  • €5,000 per group
  • Up to 12 developers
  • Level 300
  • English or German
Why guided

The workshop is free. Finishing it is the hard part.

Once Upon Agentic AI is an AWS workshop at level 300: about two hours, eight chapters plus cleanup, available in English, French, German and Korean[1]. The code is open on GitHub[2].

In practice teams stall on the setup, on version changes and on the step from one agent to four processes talking to each other. When I ran every chapter in September 2026, four places had moved on: a deprecated built-in tool in strands_tools and a renamed server class in the MCP Python SDK among them.

The guided format keeps the whole group moving, answers the questions the page does not, and ends with a conversation about what the same pattern means for your own systems.

Your developers leave with running code, not with a bookmark to a workshop they never finished.
What they build

Four processes, one game master.

A role-playing game as the teaching story: a game master agent orchestrates a rules agent with a vector knowledge base, a character agent and a dice service behind MCP. The pattern is the same one used for support, claims or operations agents.

Architecture: web interface, game master orchestrator on port 8009 calling a rules agent and a character agent over A2A and a dice service over MCP.
What runs at the end: a web interface, the game master orchestrator, two agents behind A2A servers and one tool behind an MCP server, each in its own process.Source: Linda Mohamed, walkthrough of the AWS workshop Once Upon Agentic AI, September 2026
The chapters

Eight chapters, each one runs.

Table of chapters 0 to 7: setup, simple agent, built-in tools, custom tools, MCP server and client, A2A agents, web page, next steps.
From setup and a first agent to built-in and custom tools, MCP, A2A and a web interface. Each chapter lists the file you edit and what you run.Source: Linda Mohamed, walkthrough of the AWS workshop Once Upon Agentic AI, September 2026
Chapter 3 local tool versus chapter 4 MCP server over streamable HTTP.
The key step: a local @tool function becomes an MCP server the agent reaches over streamable HTTP[4].Source: Linda Mohamed, walkthrough of the AWS workshop Once Upon Agentic AI, September 2026
Outcomes

What your developers can do afterwards.

1

Build an agent

Model, system prompt and tools with the Strands Agents SDK[3] on Amazon Bedrock[7].

2

Write tools that models use correctly

Custom @tool functions where the docstring is the contract the model reads.

3

Move tools behind MCP

Share one tool across agents and teams with a Model Context Protocol server.

4

Connect agents with A2A

Agents as servers, an orchestrator that calls them, structured output and a web UI.

5

Debug a multi-process agent system

Ports, logs and the typical failure points, plus the SDK changes to watch.

Price

One group, one day.

Two workshop blocks (€2,000 each) and one written result: a starter repository adapted to your context with debrief notes (€1,000). Net, plus VAT.

Agentic AI hands-on workshop

Setup check before the day, two guided blocks for up to 12 developers, remote or on-site.

Workshop
€2,000 each, 3 to 4 hours, remote or on-site
2
Written results€1,000 per result
€1,000
€1,000
€1,000
Your package
€5,000


Delivered within 5 business days after the last session.

Book a free 30-min Idea Call15-min question slot
Half day

Core chapters

€3,0001 block + starter repository
Standard

Full workshop

€5,0002 blocks + starter repository
Build instead

AI Agent Workshop

€5,000A prototype on your data
See the build workshop →

Attendees can use the free AWS Builder Center sandbox environment for the day[5] or your own AWS account with Bedrock model access.

How the day runs

Setup, build, transfer.

Before

Setup check

A short checklist: git, uv, Python, AWS access. Blockers are solved before the day, not during it.

Block 1

Agents and tools

First agent, built-in tools, custom tools, then the dice service as an MCP server.

Block 2

Multi-agent system

Rules and character agents behind A2A, the game master, the web page, and a debrief on your use cases.

AWS services

The AWS services behind this work.

Plain-language notes on the services I use for this kind of project. Each name links to the official AWS documentation.

Amazon Bedrock

Managed access to foundation models from several providers through one API. You choose the model and write the prompt; AWS runs the model.

Amazon Bedrock AgentCore

Runtime, memory, identity and tool gateway for AI agents built with any framework, such as Strands or CrewAI.

Amazon Bedrock Knowledge Bases

Retrieval-augmented generation: your documents are chunked, embedded and stored in a vector store, and the relevant parts go into the prompt.

Amazon Bedrock Guardrails

Filters for topics, harmful content and personal data on the way into and out of the model.

AWS Identity and Access Management (IAM)

Who and what may call which service. For agents: one narrow role per agent.

Amazon CloudWatch

Logs, metrics and alarms. For AI systems: latency, errors and cost per call.

Questions

What people ask before booking.

What does the workshop cost?

€5,000 net for one group of up to 12 developers: two guided blocks plus a starter repository with debrief notes. A half-day version with the core chapters is €3,000.

Is the workshop content yours?

No. The workshop and its code belong to AWS and are published as aws-samples under an open licence. I deliver it as a guided session, with my notes on the current SDK versions and a debrief on your use cases.

What do attendees need?

A laptop with git, Python and uv, and access to an AWS account with Amazon Bedrock model access, or the free AWS Builder Center sandbox.

Which level is it?

Level 300. Attendees should be comfortable with Python and a terminal. No prior agent experience needed.

Can it run in German?

Yes. The workshop pages exist in German, and I run the session in German or English.

Linda Mohamed, AWS Community Hero, AI and cloud architect in Vienna
Who runs it

Linda Mohamed

AWS Community HeroAWS User Group Vienna organiserLecturer, Hochschule BurgenlandAmazon Bedrock · SageMaker AI · OpenShift AIEN & DE

I design and build AI and cloud systems on AWS and hybrid platforms, and I teach how they work. I have organised the AWS User Group Vienna for more than seven years, co-organise AWS Community Day DACH, teach AI architectures at Hochschule Burgenland, speak at conferences in Europe and the US, and maintain ai-solutions.wiki. Based in Vienna. Remote or on-site, in English or German.

Projects, open source and talks →

Stay in the loop

Architecture notes, straight to your inbox.

New AI architecture write-ups, use cases added to ai-solutions.wiki, workshop dates and AWS community events in Vienna and online. Choose the topic you care about most.

  • Patterns and trade-offs from real AWS projects
  • Workshop and lab dates before they are announced
  • AWS User Group Vienna and Community Day events

Double opt-in: you confirm by email first. Unsubscribe with one click.

Start here

Start with one conversation.

30 minutes to look at your idea, your data and the right starting point. Or book 15 minutes if you only have a question.

  • Group size and level
  • Remote or on-site
  • Sandbox or your own AWS account
  • A date for the workshop

Vienna, Austria · remote across Europe · [email protected]