Today News

I attended the Kiro and Amazon Quick Fiesta event in Malaysia

I attended the Kiro and Amazon Quick Fiesta event in Malaysia

I attended the Kiro and Amazon Quick Fiesta event in Malaysia

AWS's first agentic AI event in Malaysia showcased Kiro and Amazon Quick — two products designed to turn AI agents from demos into production workflows. Here's what happened, what I learned, and why the workflow framing matters more than the speed-up promises.
2026.07.17

I spent the day at the Kiro and Amazon Quick Fiesta Malaysia, AWS’s first local event dedicated to its two agentic AI products: Kiro, an agentic IDE for developers, and Amazon Quick, an agent-powered work companion for everyone else. Held at M World Hotel, Kuala Lumpur on 14 July 2026.

Event badge and booth stamp card
Badge and booth passport — six booths, six stamps.

Main ballroom filling up before the keynote
The ballroom before the 9:45am keynote.

Where the products sit in the portfolio

A portfolio slide put both products in context — Kiro and Amazon Quick sit at the applications and agents layer, on top of Bedrock/AgentCore, on top of SageMaker and the AI compute layer (Trainium, Inferentia, GPUs), with security and policies wrapped around the whole stack. Notably, “Frontier Agents” now includes a Kiro autonomous agent, an AWS DevOps Agent and an AWS Security Agent.

AWS AI portfolio slide showing layers from infrastructure to frontier agents
The AWS AI portfolio. Kiro and Amazon Quick sit at the top; everything below is plumbing.

Amazon Quick: agents for the rest of the org

If Kiro is for people who write code, Amazon Quick is for everyone who doesn’t. It bundles six capabilities into one surface:

Amazon Quick architecture slide
Amazon Quick’s components, sitting on company data, world knowledge and actions in third-party apps.

  • Spaces — organise files, dashboards and data sources into a workspace per project.
  • Chat Agents — custom AI assistants grounded in your business knowledge.
  • Research — deep-dive analysis producing professional, citable reports.
  • Quick Sight — the BI and visualisation piece, now folded in.
  • Flows — no-code workflow automation over pre-defined steps.
  • Automate — complex, multi-step automation of entire business processes.

Underneath: company data via 40+ data connectors, uploaded files and QuickSight data; world knowledge via Bedrock models and web search; and actions into third-party apps. Governance, access controls, guardrails, Responsible AI and regulatory compliance run across all of it — which is the part that actually decides whether an enterprise can deploy this.

Fireside: From Code to Customer

Christopher Thong (Head of Solutions Architecture, AWS Malaysia) hosted Raunak Kathuria (VP of Engineering, Deriv), Hiroki Kobayashi (Head of Integration, NTT Data Payment) and Neil Tomkinson (CIO, U Mobile) on how AI agents are rewiring trading, telco and payments.

Fireside chat slide: From Code to Customer panel
Practitioners from trading, payments and telco

The breakouts

Two afternoon tracks across four halls, mixing hands-on labs (L200–L300) with presentations.

Breakout sessions grid showing four halls and two time slots
The breakout grid. Hall A and B ran hands-on Kiro and Quick labs; C and D went deeper on ops, security and MCP.

TimeHall AHall BHall CHall D
1:15–2:30Kiro: Agentic Coding
(Hands-on · L200)
Amazon Quick: AI Work Companion
(Hands-on · L200)
Kiro CLI for Cloud Operations
(Hands-on · L300)
ML Development with Kiro & SageMaker AI
(Hands-on · L300)
3:00–4:15Kiro: Agentic Coding
(Hands-on · L300)
Amazon Quick: AI Work Companion
(Hands-on · L300)
Frontier Agents for Security, DevOps and Finance
(Presentation · L200)
MCP and Skills deep dive
(Presentation · L200)

Kiro, properly explained

Thenesh (Solutions Lead) gave the clearest framing of Kiro I’ve heard: an agentic AI development environment from prototype to production. The emphasis is on that last part. Plenty of tools get you a demo; Kiro’s pitch is the path from demo to something you’d deploy.

Kiro session title slide
“Agentic AI development environment from prototype to production.”

Spec-driven development

Kiro IDE slide explaining spec-driven development
Kiro turns a prompt into requirements, system design and discrete tasks — before writing code.

This is the differentiator. Instead of prompt → code, Kiro does prompt → spec → code:

<ol data-line…

     
                    WhatsApp Channel                             Join Now            
   
                    Telegram Channel                             Join Now            
   
                    Instagram follow us                             Join Now