The current state of the AI Agents ecosystem reminds me of the early days of technologies like Big Data
written by Stefan Christoph
- 2 minutes readThe current state of the AI Agents ecosystem reminds me of the early days of technologies like Big Data/Hadoop or Containers/Kubernetes: many different tools, frameworks, and open source projects to choose from.
While flexibility is beneficial, it makes getting started quite challenging. Which direction should I go?
Exploring the options thoroughly costs time and resources most teams don’t have — solid, prescriptive guidance shortens that path.
And here we go: If you’re looking at building AI Agents on AWS, the AWS Prescriptive Guidance - Agentic AI [1] serves as an excellent starting point. It provides guidance on the foundations of Agentic AI, patterns and workflows on AWS, and also covers the growing selection of Agentic AI frameworks, protocols, and tools available on AWS [2]. Note that the scope extends beyond AWS/Amazon frameworks and tools to include discussions of open source frameworks like LangChain and LangGraph, as well as protocols like MCP and A2A. Many more topics are covered, so I highly recommend reading it when getting started with your Agentic AI projects on AWS or when you want to re-evaluate earlier decisions.
Feel free to reach out if you need to dive deeper into any of these topics.
[1] AWS Prescriptive Guidance — Agentic AI (guide series hub): https://aws.amazon.com/prescriptive-guidance/agentic-ai/ — including “Foundations of agentic AI on AWS”: https://docs.aws.amazon.com/prescriptive-guidance/latest/agentic-ai-foundations/introduction.html [2] AWS Prescriptive Guidance — “Agentic AI frameworks, platforms, protocols, and tools on AWS”: https://docs.aws.amazon.com/prescriptive-guidance/latest/agentic-ai-frameworks/introduction.html
#AWS #AgenticAI #PrescriptiveGuidance
📝 Last updated: August 14, 2026 — Technical corrections from a quality audit; repaired a title that the LinkedIn import had truncated mid-word