Amazon Kiro at AWS Summit NYC: Spec-Driven AI Goes Mobile

AWS Goes All-In on Spec-Driven Coding

On 17 June 2026, Amazon Web Services held its annual Summit at the Javits Center in New York, with VP of Agentic AI Swami Sivasubramanian opening a keynote that confirmed AWS's direction for the rest of the year: AI agents that do engineering work, not just assist with it. The centrepiece product at the Summit was Kiro, Amazon's agentic IDE launched on 7 May 2026 as a complete replacement for Amazon Q Developer. Two announcements headlined the event: a Kiro Pro Max tier at $100 per month, and a native Kiro for iOS application giving developers a mobile surface to manage, review, and approve agent work from their phones.

What Kiro Is and Why Amazon Built It

Amazon Q Developer, Amazon's previous AI coding assistant, was a plugin layered on top of existing editors. Kiro is not a plugin. It is a standalone editor built on Code OSS, the MIT-licensed open-source base from which Visual Studio Code is derived, with AWS's agentic architecture built into it from the start. New Q Developer signups have been blocked since 15 May 2026, and full end-of-support for Q Developer IDE plugins is set for 30 April 2027.

The founding design decision in Kiro is that code generation should not begin until a formal specification exists. When a developer starts a new feature, Kiro runs a structured three-phase workflow that produces three documents: a requirements.md file capturing functional and non-functional requirements, a design.md file describing the intended architecture, and a tasks.md file breaking implementation into discrete, tracked steps. The agent can generate code only after these documents exist and the developer has reviewed them.

Kiro uses EARS notation — Easy Approach to Requirements Syntax, a technique developed for aerospace and safety-critical systems — to structure the requirements phase. The choice matters: EARS produces requirements that are unambiguous and testable, giving the agent a precise specification to code against rather than an open-ended prompt.

Powered by Claude via Amazon Bedrock

Kiro's coding and reasoning capabilities are currently powered by Claude models accessed through Amazon Bedrock. The Bedrock integration means Kiro can be configured to route tasks to any Bedrock-available model, giving enterprise teams flexibility on cost, capability, and compliance. At the Summit, AWS also expanded Amazon Bedrock AgentCore with new capabilities for connecting AI agents to organisational knowledge bases, monitoring agent behaviour in production, and enforcing usage controls as agents take on more autonomous tasks.

The Two New Announcements: Pro Max and iOS

Kiro Pro Max, confirmed at the Summit on 17 June, is a $100 per month tier sitting between the Pro+ plan at $40 per month and the Power tier at $200 per month. It raises the monthly credit limit for agentic sessions and includes access to the latest frontier models available through Bedrock. Pro Max addresses the gap that emerged as engineering teams scaled Kiro adoption and found Pro+ credits exhausted before month-end — the same pattern that drove the Copilot AI Credits cost conversations at organisations using GitHub's metered billing.

Kiro for iOS is a native mobile application in gated preview, released on 17 June 2026. It is not a mobile editor — it is a supervision surface. Developers can start new Kiro agent sessions from their phones, check session progress while away from their desks, review diffs the agent has produced, and approve or reject proposed changes. The practical scenario the product targets is a developer who kicks off a substantial agent task at the end of the working day — a feature branch, a refactoring pass, a test suite — and follows its progress from a phone without keeping a laptop running overnight.

The Security Angle

AWS also announced deeper integration between Kiro and its AWS Security Agent, now part of AWS Continuum. The integration adds threat modelling directly inside Kiro sessions, with security review running in the same environment as the code being written. AWS positioned this as closing the gap between the security review cycle and the development cycle — a gap that traditionally requires switching between tools and losing context. The same integration connects Claude Code's plugin architecture to Kiro via the Model Context Protocol, meaning teams using both tools can share context between their sessions.

What This Means for Indian Engineering Teams

Indian product companies and digital agencies that build on AWS infrastructure have a direct integration path with Kiro given its Bedrock backend. For teams already using Claude via Bedrock for other applications — document processing, API summarisation, or internal tooling — Kiro adds an agentic IDE surface without requiring a new API contract or a separate model evaluation process.

The spec-driven workflow addresses a genuine pain point in AI-assisted development at scale. The most common failure mode with code-generation agents is that they write code against an ambiguous brief and produce output that does not match the intended design. Kiro's requirements and design documents shift that failure to earlier in the process, where it is cheaper to resolve. For teams charging clients on a fixed-price basis, the structure that Kiro enforces before a single line of code is generated reduces the risk of late-stage rework — which is precisely where fixed-price projects lose margin.

The Bottom Line

At AWS Summit New York on 17 June 2026, Amazon expanded Kiro with a Pro Max tier at $100 per month and a native iOS app for mobile supervision of agent sessions. Kiro, which replaced Amazon Q Developer on 7 May 2026, enforces a spec-first development workflow using EARS notation before any code is generated — a structural safeguard against the ambiguous-brief failure mode common to agentic coding tools. For Indian teams on AWS infrastructure, the Bedrock backend makes Kiro an immediately accessible option. The spec-driven model is its strongest practical argument.