There are a lot of coding assistants now and most of them are competing on the same axis, which is how well the underlying model writes code. Amazon Q Developer competes on a different one, which is how much it knows about AWS, and that turns out to matter more than I expected for people who spend their days in that ecosystem. AWS has a very large surface area. Hundreds of services, thousands of configuration options, permission models that defeat experienced engineers, and documentation that is comprehensive and famously hard to search.
An assistant that has absorbed all of that and can answer a specific question about a specific service configuration in context is solving a real problem. Ask a general coding assistant to write an identity policy with least privilege for a particular access pattern and you will often get something plausible that does not work. Ask this and you have a better chance, because service specificity is the thing it was built for. The code transformation capability is the most commercially interesting part and the least discussed.
Upgrading a large Java codebase across major versions is genuinely expensive work that organisations defer for years. The transformation tooling automates a substantial portion of it, and while it does not do the whole job and will not handle the genuinely hard parts, going from a six month project to a six week one is a large saving. If your organisation has that problem, this alone can justify the evaluation. The documentation follows AWS conventions, which means it is thorough, it is current, it covers every option, and finding the thing you actually want is an exercise in patience.
There are getting started guides, service references, IDE specific setup pages, command line documentation, administrator guides for the enterprise deployment, and they overlap. The workshops are the better entry point. AWS produces free hands-on workshop content with real exercises and those are more efficient than reading the reference, and I would start there rather than at the documentation root. The free tier deserves credit.
You can use a meaningful amount of the functionality without a purchase decision or a procurement conversation, which is unusual for enterprise developer tooling and removes the main barrier to evaluation. Try it on your own work for a week before anyone signs anything. Now the criticisms. As a general coding assistant, on ordinary application code with no AWS involvement, it is behind.
The suggestions are competent and the agent behaviour is less capable than the current leaders, and if I were choosing a single assistant for a team that writes mostly business logic I would not pick this. That is a fair comparison because these tools are directly substitutable and the gap is visible within a day of use. The naming has been a mess. The product has been rebranded and restructured more than once, the boundaries between the developer offering and the broader business offering have moved, and the consequence is that search results, blog posts and even some AWS documentation refer to configurations that no longer exist under names that have changed.
Check the date on anything you read and prefer the official docs, which are at least kept current. Enterprise setup is heavier than it should be. Identity Center integration, subscription management, policy configuration, and the administrator experience generally feels like it was designed by people who assume you already run a large AWS organisation with a dedicated platform team. Smaller teams will find the path from free tier to paid deployment involves more infrastructure decisions than they wanted.
The value proposition collapses off AWS. If you build on another cloud or on your own hardware, the service knowledge that makes this worth using is irrelevant to you, and what remains is a mid-tier coding assistant. That is not a criticism of the product so much as a statement of who it is for, and it is worth being clear about because the marketing is not. My three point six is for a tool that is genuinely good at a narrow and valuable thing, with free learning material that is well made, held back by general purpose performance that does not keep up, documentation that is exhausting to navigate, and a product identity that has changed often enough to make the internet's advice unreliable.
If you live in AWS, evaluate it seriously. If you do not, look elsewhere.