Vertex Macro｜Financial Cloud Cloud · AWS Amarathon 2025
Vertex Macro｜Amarathon 2025 Recap 14：What if AI does my job How Q Developer CLI and Kiro have changed my daily routine
What I Do
● Overview of the author's professional activities and responsibilities.
● Detailed sections covering various aspects of the author's work:
● Amazon Reference
● Technical Reference
● New Projects
● Problematic Projects
● Core Projects
● Business Initiatives
● Areas needing assistance
Q Developer CLI and Kiro Saves Me, I didn't like GenAI, Q Developer CLI
● Discussion on the utility of Q Developer CLI and Kiro.
● Personal dislike for GenAI.
● Specific praises for Q Developer CLI.
How They Works
● Explanation of the functioning and mechanisms of the tools mentioned.
● Amazon MCP Servers
● Super Powers
● CLI Commands
● Knowledge
● Pricing
● Git Research
● Terraform
Agentic Loop (Q Developer CLI)
● Description of the agentic loop in Q Developer CLI:
● Perception
● Planification
● Action
● Learn
● Evaluation
Spec Driven (Kiro)
● Focus on specification-driven development using Kiro.
● Requirements
● Design
● Task
● All Works Fine.
Are they helpful for me?
● Assessment of the tools' usefulness to the author.
Various use cases for the tools
● Code
● Assessment
● Optimizations
● Problem Resolution
● Cost Calculation
● Deployments
● Documentation
● Testing
Q Developer CLI vs Kiro,
● Comparison between Q Developer CLI and Kiro:
● Immediate use: amazon Q
● End-to-end solutions: Kiro
Real-world examples of tool usage
● Creating a landing zone
● Establishing a baseline from past projects
● Improving a blog website and creating a deployment structure
● Migrating a project from another CDN to CloudFront
● Creating a migration plan
● Designing resilient architectures
● Assessing Terraform projects
● Reviewing numerous problems
All things good?
● Critical evaluation of whether everything is beneficial.
Lessons learned from using the tools
● Careful review of requirements
● Need for supervision
● Opting for the easy path
● Potential for getting stuck in loops
● Amazing but sometimes unrealistic ideas
● Caution against code deletion
Positive aspects of using the tools
● Reduced time dedication
● Development of cool ideas
● Superior code explanation
● Ability to execute tasks during meetings
Concluding thoughts
● Empowering developers and engineers rather than replacing them
● Responsibility in technology usage