I've been working with AWS for quite some time, mostly using the Console and CloudFormation, but now I'm diving deeper to build on my Salesforce expertise. I've heard that Amazon Q is intended to replace some of the older methods of coding and architecture. I'm really interested to hear if anyone out there is using Amazon Q in their enterprise environment, whether as a Developer or Solutions Architect. What specific workflows are you implementing with it? Also, how do you approach using Amazon Q in your projects? Is having a solid understanding of it essential for securing a more AWS-focused role these days?
3 Answers
I use Amazon Q Developer Pro (also known as Kiro-CLI) almost daily through the command line. It’s super handy for those long commands I often forget, with my own configurations for cost and knowledge servers. I can easily query my AWS infrastructure and create diagrams right from the CLI.
To be honest, most people I know aren't using Amazon Q. I've heard it's being phased out in favor of tools like Quicksuite and Kiro. If you're focusing on AWS, I recommend sticking with the core infrastructure, where they really make their profits.
I actually like Amazon Q for quick tasks. It’s great for generating single-input commands, like creating an S3 bucket in Terraform. It captures existing patterns and saves me from repetitive code, especially when migrating older accounts into Terraform. Just need to keep an eye on the project-wide context, though.
Totally agree! I rely on it for those repetitive tasks too. It’s super helpful when you need to quickly set up new resources based on existing structures.