Peter Ross McAree

Following on from my previous post, I thought I would dive a little deeper into two specific features with AWS Kiro that I use frequently. Two features that I feel work well for my use cases. As I build trust with agentic workflows, I find myself delegating more tasks (of specific types) to Kiro's agent. That trust is building through the spec-driven development nature of Kiro, and the approach that it takes.

With AI tooling absolutely dominating the tech space (and world for that matter) right now, it only seems fitting that as an engineer I test the bleeding edge tools to evaluate for myself. So I thought I'd give it a test whilst building a real feature that was sitting in my backlog for a while, but never had the time to get round to. The feature in question is a embedded social widget within an existing blog website.

Having a professional, branded API endpoint is essential for modern applications - especially when you want your users to interact with something memorable like api.yourcompany.com rather than the default, randomly generated AWS endpoint like https://d-abc123xyz.execute-api.us-east-1.amazonaws.com.