TIETOJA TÄSTÄ JAKSOSTA
Tipu Qureshi — Senior Principal Engineer at AWS — joins the show fresh from the AWS Summit NYC 2026 announcements to break down how DevOps Agent is changing the way teams handle operations and release management. After 14 years across EC2, Elastic Load Balancing, AWS Support, and Networking, Tipu moved into the Agentic AI organization to build the DevOps Agent and contribute to Agent Core. We explore how the agent investigates incidents autonomously, integrates with your IDE through Kiro and Claude, and validates code changes in sandboxes before they hit production. Key takeaways: • Reactive and proactive — DevOps Agent triggers on alarms and ServiceNow incidents, but Custom Agents now run on schedules to detect anomalies before they become outages. • Context is king — Customers who integrate their Git repos, metrics, and logs get significantly more accurate root causes. Native GitHub/GitHub Enterprise support plus bring-your-own MCP for custom observability. • IDE integration — Kiro powers and Claude plugins give on-call engineers the full agentic loop: investigate, root-cause, fix, and validate without leaving the editor. • Release management — The new readiness review inspects pipeline stages, past deployment failures, and integration tests to catch issues before merge, while sandbox testing validates proposed fixes. • Multi-cloud support — Native Azure integration via IDC with RBAC, plus bring-your-own MCP and A2A for on-premises and other clouds. • Custom agents and skills — Bring domain-specific knowledge (SAP HANA failure modes, proprietary tooling) via skills from GitHub repos or the assets API, with MCP tools for full customization. • A2A bi-directional — DevOps Agent can be engaged by other agents and can reach out to other agents, enabling multi-agent escalation workflows. • Transparency — Every tool call, skill invocation, and reasoning step is captured in a journal visible to customers via API and the operator console. • What's next — Deeper integrations, automated mitigation actions with safety policies, time-bound rules for agent escalation, and script execution coming soon.With Tipu Qureshi, Senior Principal Engineer at AWS
Englanti
Yhdysvallat
TRANSKRIPTIO 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
HAE EDELLISIÄ EPISODEJA
Hae kanavan The AWS Developers Podcast vanhoja jaksoja.
MUITA jaksoja TÄSSÄ PODCASTISSA
Davide de Sio built KiroGraph as a personal side project to stop his AI agent from burning through credits just searching files. It turned into a community-driven, open-source MCP server that gives Kiro (and other AI agents) a semantic map of your codebase — reducing token usage by up to 80%. We di…
John Sexton and Aaron Tummon from Genesys join the show to share hard-won lessons from building and operating Cloud Copilot — an agentic AI layer serving 2 million users across 21+ AWS regions. Genesys powers customer experience for brands like Virgin Atlantic, Vodafone, and HSBC, and their copilot…
Most MCP tools today return text. But what if your agent could render a chart, a form, or a full dashboard right inside the chat? That's what MCP apps do — and they're already live on ChatGPT, Claude, and Amazon Quick. Romain sits down with Luigi Pederzani, co-founder of Manufact (the company behin…
An honest, no-filter conversation about where developers actually stand with AI today. Warren Parad — CTO at Authress, AWS Community Builder, and host of Adventures in DevOps — brings a contrarian 'LLM realist' perspective grounded in daily use, while Romain nuances with enterprise customer observa…
Vastuuvapautusilmoitus: Tälle sivulle upotettu podcast ja kuvitus ovat peräisin Amazon Web Services:ltä, joka on sen omistajan omaisuutta, eikä se ole sidoksissa Listen Notes, Inc:n tukemaan.
MUOKKAA
Kiitos, kun autoit pitämään podcast-tietokantaa ajan tasalla.
