『The AWS Developers Podcast』のカバーアート

The AWS Developers Podcast

The AWS Developers Podcast

著者: Amazon Web Services
無料で聴く

Stay updated on the latest AWS news and insights for developers, wherever you are, whenever you want.All rights reserved
エピソード
  • AWS DevOps Agent: Can Your Pipeline Keep Up with AI?
    2026/06/24
    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.
    続きを読む 一部表示
    46 分
  • KiroGraph: How a Local Code Graph Saves 80% of Your AI Tokens
    2026/06/17
    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 dive into the architecture, security, and modules, how everything runs 100% locally, and how the AWS Community shaped the project's roadmap. Key takeaways: • Code graphs vs. grep — Tree-sitter and AST-based graph generation give AI agents a smarter navigation model, eliminating wasteful file searches. • Architecture module — Detects patterns and prevents drift by validating your codebase against its own structural rules. • Security module — Finds exposed secrets and vulnerabilities by tracing the call graph, born from an AWS Summit Milano talk. • Watchman module — Auto-generates Kiro skills from repetitive patterns, building persistent memory for your agent. • 100% local execution — Embeddings run with Nomic and summarization with Gemma 3, no data leaves your machine. • Spec-driven development — Davide built KiroGraph with Kiro itself, using specs to drive the entire development lifecycle. • Portability — Commit the graph to Git and share it across machines and team members. • Community-driven roadmap — CI/CD integration, validation hooks, and container deployment are next.
    続きを読む 一部表示
    1 時間 7 分
  • Cutting Through the AI Developer Hype
    2026/06/10
    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 observations and the data behind the hype. Together they explore why 93% of devs feel productive but only 4% of enterprises see results — and what separates those who benefit from those who don't. Key takeaways: • AI is a multiplier, not a magic wand — The DORA 2025 report confirms AI amplifies your existing processes. If those processes are broken, AI makes them worse faster. • Spec-driven development beats instant responses — Long-form spec-based workflows let you disengage and return, avoiding the 'TikTok-ification' of software engineering where you're always context-switching. • Sub-agent opacity is a real problem — When agents delegate to sub-agents, you lose visibility into why decisions were made. Custom agents with explicit permissions and tool access help contain the blast radius. • Greenfield work is where LLMs struggle most — LLMs excel at refactoring and targeted feature changes where engineers already know the implementation. Open-ended new projects lead to scope creep and unfinished work. • Critical thinking erosion is measurable — Microsoft/Carnegie Mellon research shows knowledge workers self-report reduced cognitive effort when using AI. The long-term implications for engineering judgment are concerning. • Governance first, tools second — Enterprises that succeed with AI spend the first month on governance, AI registries, and codifying best practices before enabling tools across teams. • Software development was never the bottleneck — Unless AI solves handoffs, knowledge management, and organizational alignment, faster coding alone won't compress your roadmap.
    続きを読む 一部表示
    1 時間 20 分
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません