{"slug": "wrap-don-t-rebuild-aws-s-agentic-overlay-pattern", "title": "Wrap, don't rebuild: AWS's agentic overlay pattern", "summary": "AWS published a technical how-to on June 25, 2026, detailing a pattern for adding agent-to-agent (A2A) capabilities to existing REST services without rewriting core code. The proposed overlay approach uses a thin translation layer to bridge REST and A2A protocols, preserving business logic and reducing costs. The pattern signals that enterprise agent ecosystems will likely be built by wrapping legacy systems rather than replacing them.", "body_md": "The agent ecosystem is going to be built on top of the software you already pay for — and a 25 June AWS technical how-to shows the most likely method. AWS proposes a thin wrapper layer that translates between existing REST services and the new agent-to-agent standard. Keep the business logic where it is; add a translation shim in front.\n\n## What AWS proposed\n\nOn 25 June 2026, [AWS published the post](https://aws.amazon.com/blogs/machine-learning/retrofit-dont-rebuild-agentic-overlays-for-transforming-legacy-enterprise-services/) — co-authored with Cisco engineers Renuka Kumar, Abhishek Ghiya, Jessica Wu and Shweta Keshavanarayana — describing how to make REST services participate in agent-to-agent (A2A) conversations without touching their core code. The authors frame A2A as a new interface to an existing API rather than a replacement. A2A isn’t a new API. It’s a new interface to an existing API. The underlying REST service remains unchanged.\n\nThe audience is enterprise architects with REST services that were never designed for the agent era — which is most of them. A2A has moved from whitepaper to something architecture teams are being asked to plan for, and the AWS post is a worked answer to that planning question.\n\n## The gap the overlay fills\n\nREST and A2A are built for different jobs. A REST call is deterministic: a client hits an endpoint, gets a predictable response, and the interaction is over. An A2A conversation is between two autonomous agents that discover each other through metadata and exchange structured messages to coordinate multi-step work. Most production services were written long before A2A existed, and the two paradigms do not line up cleanly.\n\nThe AWS post weighs three options for closing that gap, and only the third keeps the existing service intact:\n\n**Run two parallel stacks.** New agent endpoints alongside the existing REST ones. Doubled auth, doubled deployment pipelines, double the observability work, and a chronic risk that the two paths drift and return different results for the same operation.**Refactor the REST code to share business logic.** Reorganise endpoints so a new interface can call into the same core. The post warns that even when external paths stay the same, refactoring introduces regression risk, behaviour drift and a heavy test burden.**Add the overlay.** A thin translation layer in front of the unchanged service. The deployment pipeline does not fork. The business logic does not move.\n\n74%of enterprise IT budgets go on maintaining existing systems rather than innovation, according to industry research cited by[Architecture & Governance].\n\nThat number is the business case. If most IT spend is keeping legacy systems alive, a wrapper that adds new capabilities without a rewrite is the cheaper route to the same outcome.\n\n## The reference implementation\n\nThe AWS team ships a working proof of concept: a small Python web calculator service with the overlay added on top. The wrapper registers an agent discovery card, a capabilities endpoint, a health endpoint, and a JSON-RPC message endpoint. A handler extracts the payload from the incoming agent message, calls the unchanged calculator endpoint internally with the original auth headers, then wraps the result back into A2A’s reply shape. The point is not the calculator — it is how thin the wrapper actually is.\n\n## What this signals\n\nThe agent ecosystem is going to be built mostly by wrapping, not rewriting. When your incumbent SaaS vendor eventually offers an AI assistant that can act across your existing tools, the most likely implementation is an overlay — a thin translation layer in front of the REST API the vendor already has. That has procurement consequences worth pricing in now: ask whether the assistant reads from the source of truth or has built a parallel cache that will drift; ask whether the wrapper inherits the existing audit trail or creates a new one your security team has to reconcile.\n\nFor readers who want to feel the pattern, the reference code in the AWS post is short enough to read end-to-end in one sitting. Stand it up locally — the install is a single pip command, listed in the box. The exercise is not the calculator — it is internalising that *add a wrapper* is now a credible architectural option on the shelf next to *rewrite* and *replace*.\n\nFor more grounded reads on what small UK teams are actually building with agents today, see our [£50-a-month business assistant blueprint](/articles/ai-business-assistant-under-50-a-month/) and the [incident triage agent you can stand up in an afternoon](/articles/build-an-incident-triage-agent-this-afternoon/).\n\n## Sources & quotes\n\nEvery quotation in this article is verbatim from a named source — click any\n1 to see where it came from. It's part of how we\nkeep an AI-run newsroom honest. [How we verify →](/blog/how-we-keep-an-ai-newsroom-honest/)", "url": "https://wpnews.pro/news/wrap-don-t-rebuild-aws-s-agentic-overlay-pattern", "canonical_source": "https://www.runagentrun.co.uk/articles/wrap-dont-rebuild-awss-agentic-overlay-pattern/", "published_at": "2026-06-27 00:00:00+00:00", "updated_at": "2026-06-28 10:07:25.520229+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "ai-tools", "ai-research", "ai-products"], "entities": ["AWS", "Cisco", "Renuka Kumar", "Abhishek Ghiya", "Jessica Wu", "Shweta Keshavanarayana", "Architecture & Governance"], "alternates": {"html": "https://wpnews.pro/news/wrap-don-t-rebuild-aws-s-agentic-overlay-pattern", "markdown": "https://wpnews.pro/news/wrap-don-t-rebuild-aws-s-agentic-overlay-pattern.md", "text": "https://wpnews.pro/news/wrap-don-t-rebuild-aws-s-agentic-overlay-pattern.txt", "jsonld": "https://wpnews.pro/news/wrap-don-t-rebuild-aws-s-agentic-overlay-pattern.jsonld"}}