AI in SDLC: Kiro and OpenAI Codex Workshop Comes to AWS Seattle on July 1

The conversation around AI in the software development lifecycle has matured. The question is no longer whether AI belongs in engineering workflows. The harder question is how teams use it in production without creating new problems around governance, quality, security, and accountability.

That is the backdrop for AI in SDLC: Executive Panel & Hands-on Workshop with Kiro and Codex, an upcoming AWS Connected Community event scheduled for July 1, 2026 at AWS in Seattle. The session combines an executive panel with a hands-on workshop focused on Kiro and OpenAI Codex, giving engineering leaders and builders a place to discuss what happens after the AI demo.

This article covers the July 1, 2026 Kiro and Codex workshop specifically. AWS has hosted and promoted other similarly named AI in SDLC events with different tool combinations and different speaker lineups, so the details here should not be blended with those adjacent sessions.

About the July 1 AI in SDLC Workshop

The July 1, 2026 event is framed around a practical shift in software engineering. AI coding tools are no longer only experimental assistants. They are becoming part of planning, implementation, testing, documentation, and deployment workflows.

The official event listing positions the workshop around AI-driven development and the software development lifecycle. A participant announcement from Shikhar Kwatra describes the focus more directly: what is working beyond demonstrations, how organizations are moving from experimentation into production, how developer velocity can improve without sacrificing governance, and how engineering roles continue to change as AI becomes part of daily software delivery.

The hands-on portion matters because it changes the event from a panel about AI into a working session around tools. Attendees are encouraged to bring laptops and hard questions, which suggests a room built for practitioners rather than passive observers.

That orientation fits the moment. Many organizations have already tested AI coding assistants. Fewer have answered the operational questions that follow: who reviews AI-generated work, how quality is measured, what governance belongs in the workflow, and how teams decide which parts of the software lifecycle should remain human-led.

Why It Matters Now

Software teams are entering a more serious phase of AI adoption.

The first phase rewarded experimentation. Teams tested assistants, ran pilots, and measured whether developers could move faster. The next phase is less forgiving. It requires engineering organizations to turn AI into repeatable systems that can survive production constraints.

AWS has described an AI-Driven Development Life Cycle methodology in which AI can participate across planning, construction, and operations while maintaining human oversight. Kiro represents AWS's spec-driven approach to agentic development workflows. OpenAI Codex represents another path toward agentic coding in terminal, IDE, and cloud contexts.

Putting those tools into the same workshop creates a useful comparison for engineering leaders. The strategic question is not which product creates the most impressive demo. It is how each approach changes the work of planning, reviewing, securing, and shipping software.

For founders and technical leaders, that distinction matters. Speed alone is not enough if it introduces risk that teams cannot see until later. The real advantage comes from combining faster execution with better judgment about what should be automated, what should be reviewed, and where accountability belongs.

The Panel Lineup

The confirmed July 1 speaker lineup includes Shikhar Kwatra, Chad Neal, Luke Stevens, Abhisheikh Lahoti, and Josh Browder. Shikhar Kwatra brings the OpenAI perspective and prior AWS experience, giving the discussion a bridge between Codex, enterprise deployment, and AWS-native engineering environments.

Chad Neal brings an AWS cloud architecture perspective on how AI-assisted development fits into real delivery systems rather than isolated experiments.

Luke Stevens, affiliated with Jellyfish, brings an engineering measurement lens. That is increasingly important because teams adopting AI need to understand impact beyond anecdotal productivity stories.

Abhisheikh Lahoti adds an AWS ecosystem and platform perspective, including how partner and marketplace dynamics may shape AI-native software delivery.

Josh Browder, founder and CEO of DoNotPay, adds the view of a product builder operating in a sensitive, highly scrutinized AI category. That perspective is useful because AI governance stops being theoretical when software touches legal, consumer, or regulated workflows.

The mix is useful because it does not represent one narrow vendor narrative. It brings together cloud architecture, agentic coding, engineering intelligence, partner ecosystems, and AI-native product development.

What Kiro and Codex Put Into the Room

Kiro and Codex are both part of the broader move from AI-assisted coding toward AI-native software development, but they approach the problem from different angles.

Kiro is associated with spec-driven development, where requirements, design, acceptance criteria, and implementation planning become a structured part of the AI workflow. That approach matters because many software failures begin before code is written, when teams misunderstand requirements or skip design clarity.

OpenAI Codex emphasizes agentic coding across developer environments, including command-line and IDE workflows. Its relevance for enterprise teams is not only code generation. It is the possibility of delegating bounded engineering tasks while preserving review, sandboxing, and approval gates.

The workshop format is valuable because the comparison can move beyond product positioning. Attendees can ask how these tools fit into existing repositories, team rituals, security models, and release processes.

Those questions are where AI adoption becomes operational. The tools matter, but the operating model around the tools may matter more.

Why Seattle and AWS Connected Community Matter

Seattle remains one of the world's strongest centers for cloud infrastructure, enterprise software, developer tooling, and AI talent. Hosting this conversation at AWS in Seattle places it inside an ecosystem where many companies already build and operate cloud-native software at meaningful scale.

AWS Connected Community is also a relevant host because its programming is aimed at builders and operators working through real technology transitions. For this event, that means the conversation can stay close to practical implementation rather than drifting into broad predictions about AI's future.

The verified materials confirm AWS Connected Community as the host and AWS Seattle as the venue context. They do not confirm OpenAI, Jellyfish, DoNotPay, iSpot, or any other organization as formal sponsors. Those organizations should be understood through the speaker affiliations and public source context, not as verified sponsorship claims.

That distinction is important because several AI in SDLC events exist with similar naming. Accuracy depends on keeping the July 1 Kiro and Codex event separate from other AWS workshops and panels.

What Engineering Leaders Should Watch

The event is worth watching because it sits at the point where AI coding stops being a novelty and becomes an organizational design question. Engineering leaders should pay attention to how the panel frames governance. The strongest AI development workflows will likely be the ones that make review, traceability, security, and human judgment easier to apply, not harder.

They should also pay attention to measurement. If AI changes how software is planned and built, teams need better ways to understand whether quality, throughput, maintainability, and customer outcomes are improving together.

Finally, they should watch how builders talk about roles. AI does not remove the need for product judgment, architecture, code review, incident response, and accountability. It changes where those responsibilities show up in the workflow.

That is why the July 1 workshop is more than a tool demo. It is a signal that the next phase of AI in software development will be judged by execution discipline, not enthusiasm.

For founders, CTOs, engineering managers, and product leaders responsible for production software, that is the conversation worth having before the next development cycle begins.