Ship Without the Guesswork — Kiro + Agent Toolkit

Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.

Original language: English

Original video: Ship Without the Guesswork — Kiro + Agent Toolkit · Channel: Kiro · 07:17 · Watch on YouTube

Topics: AI agents, Software engineering with AI, AI infrastructure and hardware

Summary

The presenter needed a portfolio website to share talks, blog posts, and event resources, but was unfamiliar with deploying a site on AWS Amplify. They install the Agent Toolkit for AWS, which gives Kiro access to current AWS documentation, curated workflow skills, and security guardrails. Using spec-driven development, Kiro helps build and deploy the site, including its content and event pages, without requiring the presenter to learn Amplify configuration first. The presenter highlights how the toolkit can also support future AWS projects and recommends trying it.

Key points

The presenter wanted one place to share their talks, writing, and conference resources.
They chose a simple HTML, CSS, and vanilla JavaScript site hosted on AWS Amplify.
Without AWS context, coding agents may rely on stale information, guess configurations, or miss security practices.
The Agent Toolkit for AWS provides current documentation fetched at query time, curated skills, and IAM-based security guardrails.
Kiro uses the toolkit to follow deployment procedures and configure Amplify build settings.
The portfolio includes content pages and an events page with resources from past events.
The project was built using spec-driven development rather than simply coding from an open-ended prompt.
The presenter says the toolkit can work with more than 300 AWS services and 15,000 API actions through a single tool.
The toolkit has no additional charge; users pay for the AWS resources their agent provisions or interacts with.

Chapters

Start	Chapter	Summary
00:00	Why a portfolio website was needed	The presenter explains the need for a single place to share their talks, writing, and conference materials, and their uncertainty about deploying a site on Amplify.
01:02	Introducing the AWS Agent Toolkit	The presenter contrasts unguided coding agents with the toolkit’s current AWS documentation, curated skills, and security guardrails.
02:05	Building and deploying the portfolio	Kiro uses the toolkit to work through the Amplify workflow, while the presenter shows the project files, development process, and live portfolio.
05:45	What the toolkit enables	The presenter describes the spec-driven build, the toolkit’s AWS capabilities, possible future uses, and how to get started.

Quotes

docs fetched at query time. — 01:33

It doesn’t improvise. — 02:05

I didn’t need to be an amplify expert in this use case. — 05:45

the agent toolkit made sure Kiro knew how to build it properly. — 06:16

There’s no additional charge to use it. — 06:47

Concepts and entities

Agent Toolkit for AWS, Kiro, AWS Amplify, AWS, Spec-driven development, IAM, AWS CLI

Full transcript (original language)

00:00 As I travel to community meetups and conferences, I find that folks keep asking me, “Where can I find your talks? What’s the latest blog you’ve written?” Well, the answer was a list of links and QR codes across all the mediums I publish content to, from [music] YouTube to Dev.to, and conference sessions scattered across different event pages. But no single place someone could go to see it all. And that’s when I realized I needed a portfolio website, somewhere [music] I could point both community members who wanted to find me and conference organizers who wanted to see samples of my work. I knew I wanted to

00:30 build a simple [music] HTML, CSS, vanilla JS site, and a peer suggested I host it on AWS Amplify. But beyond that, I didn’t know where to begin, and I’m no Amplify expert. I [music] don’t have the deployment configs memorized, and I don’t know off the top of my head what the best practices are for hosting securely using this AWS service. Now, I know what you may be thinking, [music] “Well, couldn’t you just open up any coding assistant and say, ‘Build me a portfolio website on Amplify,’ and see what happens?” But here’s what happens when you do let a coding agent run wild

01:02 on AWS with no context. [music] It works from old training data that could be months old, it guesses at configurations, it might be using deprecated APIs, it might miss security best practices, and overall, it’s just burning through tokens, retrying things that don’t work anymore. So, instead, I’m giving my coding assistant something extra, the Agent Toolkit for AWS. Now, in this walk-through, I’m going to be using Kira CLI and IDE as my software engineering agents. But the toolkit can be used widely with any other coding

01:33 agents as well. Now, as we can see here, with a single bash command, I’m able to install the toolkit and get through setup in a few seconds. And now, Kira has access to always current AWS documentation, so not stale training data, but docs fetched at query time. It has access to curated skills, so tested step-by-step procedures for common AWS workflows, and it has access to security guardrails, so IAM-based controls, so the agent operates with least privilege. [music] This is fewer wasted tokens, always current AWS knowledge, and my agent

02:05 isn’t guessing anymore. It’s building with best practices from the start. Okay, so back to my portfolio website, with the toolkit now installed, let’s take it for a spin. I tell Kiro what I want, and here in the Kiro CLI, I say I want a portfolio website hosted on Amplify. And because it has a toolkit installed, it doesn’t improvise. We can see it pulls current Amplify documentation, and if necessary, has AWS specific knowledge of what other services Amplify may rely on to work through a complex workflow. With the toolkit, Kiro can follow tested deployment procedures, and when we’re

02:36 ready, it configures the build settings correctly on the first pass. I didn’t have to go read Amplify docs myself. [music] I don’t have to know what the right build specs look like, or how custom rewrites work, >> [music] >> or what headers I should be using for static site. The toolkit gave Kiro all of that knowledge on my behalf. It’s building securely, following AWS best practices, >> [music] >> and I can focus on what I want the site to do, instead of how to configure the infrastructure. So, in true cooking show magic, I let Kiro and the toolkit do their thing here with some spec-driven

03:06 development, and here’s where we are after that all takes place. Now, we [music] can see here in the IDE, the Kiro IDE, that I have the project repo opened up. Now again, I mentioned earlier that this website is just some simple HTML, um JS, CSS, and uh vanilla JS. So, we have here the index.html, which is basically giving us the structure for the home page, and then all of the various content pages that I have are here. And then for the events uh site, which we’ll

03:38 see in a second, I have all of my events listed out, and each of their details are uh included in there as well, so that the site pulls from the specific details that happen for each event. >> [music] >> Now, how did this all come about? Obviously, this was something that Kiro and I worked together on and I you can see here as well that I have some [music] um Spectra in development that I was using to get prepared for changing some of the aspects of the UI. So, I let Kiro um work through some design and then requirements and then finally end up

04:09 with some tasks that it was executing. Now, what this looks like on the actual website [music] is uh we can go here to the AWS console and I have AWS Amplify uh opened up here so we can see where this event resources website is being hosted. >> [music] >> Uh now again, this is something that I didn’t know how to use when I first started working on this project. I had heard from some peers that this was >> [music] >> uh what I should be using for hosting a website, but I wanted to let Kiro and the toolkit work together to figure out how to actually launch this on my behalf. So, I knew again, what I wanted

04:41 the website to look like >> [music] >> um but I didn’t quite know how to get it there. So, with the toolkit installed, Kiro did its thing and we can see here the the finished product is this portfolio website that I now have uh live and I can give this to anyone who’s asking me on the fly. If I’m meeting someone at a conference or at a community meet-up, I can point them to this resource and say, “Hey, check out the content that I’ve been working on if you want to learn more about uh you know, multi-agent systems with strands or you want to learn more about um pushing Kiro’s limits on the free tier,

05:12 etc.” There also is all the way at the bottom here um [music] for folks who had been wanting to get resources from previous events, there’s an events page where I list out all of the events that I’ve been to over the course of the last 2 years and for folks who wanted to go back and check out the resources from a particular event, they’re able to go into that uh specific [music] date and time and find the resources from that workshop. So, in this case, this was a presentation at Grace Hopper that we did and so they can go ahead and access the workshop here and the deck, etc. And

05:45 this was all again something that I was able to put together with [music] Kiro via spec driven development. So rather than just vibe coding out the whole thing, I wanted to make sure that I had the right steps in place before we started building. And with the toolkit alongside Kiro here, we were able to get this up into amplify >> [music] >> in just a couple of hours. And here’s the point. Again, I didn’t need to be an amplify expert in this use [music] case. I didn’t need to read deployment docs or memorize AWS configuration formats. I knew what I wanted, a portfolio website

06:16 hosted securely on AWS, and the agent toolkit made sure Kiro knew how to build it properly. Agents can interact with any of the 300 plus AWS services and 15,000 plus API [music] actions through a single tool without installing the AWS CLI locally. All of this is available to my coding agent without me leaving the CLI or IDE. And what’s great about this setup is I can continue using the toolkit with Kiro [music] as I find my project needs improvements. If I’m thinking about implementing caching or using a database, I can go

06:47 back to chatting with Kiro and have it use the toolkit to brainstorm recommendations for the best pathway with knowledge of the AWS well-architected best practices. Now, if you’re building on AWS, I highly recommend you check out the AWS agent toolkit and install it in just a few seconds. There’s no additional charge to use it. You only pay for the AWS resources your agent provisions or interacts with. Links [music] to everything are in the description, the agent toolkit docs, the Kiro setup guide. And if you want to see more like this, hit that like and subscribe. [music]

07:17 And if you set up agent toolkit and it helps you build something, drop a comment below and tell me what you used it for. >> [music] >> We’ll see you in the next one.