Amazon Q Reviews

My main use case for Amazon Q is that we have access to it in our company, and on a daily basis, we receive a lot of requirements from clients to build websites and probably do all the other work as well. I use Amazon Q for debugging, enhancements, and building applications. I also use Amazon Q for summarizing content and summarizing meeting descriptions. On a daily basis, Amazon Q helps me in many ways, which are mostly in developing, and some of my peer group use it for testing purposes as well. We build cool automations using Amazon Q. The project that we are currently doing is totally on AWS. Amazon Q has been the primary source for any questions that I have while implementing the product and the application in AWS. It helps a lot on a daily basis.

A recent task where Amazon Q made a difference was regarding a DocumentDB connection and Secret Manager connection issue that I faced today. I was not able to figure out what was really failing in the Lambda, but when I provided the code to Amazon Q and shared the details with it, it was able to determine that we were missing important string details in the Secret Manager that are related to DocumentDB. That was the reason the Lambda was failing to fetch the details from DocumentDB using the Secret Manager in which we store all the details of DocumentDB. It was not an easy task for me because it was a minute detail that I was not able to figure out because everything seemed to be very similar. Amazon Q helped in figuring out the issue. Before this, the actual challenging task of the project, which is setting up all the context of the project and building services and the Lambda layers and then all the Terraform code, has been done in Amazon Q. The project that we are currently doing, most of the work, whether it is Terraform code or Lambda code, which is written in Python, is completely done by Amazon Q. Amazon Q has also taken care of the gateway connections and all the other work.

On a daily basis, I use Amazon Q for building the project that we are currently building on AWS. I use it for debugging, development, and all the automations that we have in the project. Apart from that, it helps in participating in hackathons confidently because we have Amazon Q as a backup. The moment we get some idea in the hackathon, we go ahead and build it by prompting the idea to Amazon Q, and it immediately sets up the complete project. The main use case is that it helps in a lot of development work, automation, and debugging as well. The primary areas of focus are development, automation, and debugging. Regardless of the environment that I am in, whether it is in a product development space, an automation space, or a hackathon, I rely on Amazon Q on a daily basis.

The best features Amazon Q offers are the agentic mode and the ask mode. In the agentic mode, it is just a matter of prompting and it completely goes into the codebase and searches for the context and then answers me in detail. I do not need to rely on experts who know the codebase. Instead, I can just rely on Amazon Q and turn on the agentic mode so that it gets complete context and then answers me in the way that I want with the knowledge that it has of all the codebase. The main features of Amazon Q that are best in terms of the work that I do is its ability to understand the context of the codebase. The agentic mode in Amazon Q is amazing. It helps in debugging and helps in building applications.

Amazon Q has impacted my organization positively because earlier, we developers relied completely on the experienced software developers who knew the codebase. But now, since we have Amazon Q, we just clone the codebase and then make sure we are giving a detailed prompt that helps us in getting complete context of the codebase. Majorly, when I go into new projects, the moment I clone the project, I prompt it to make two documents: one specifically mentioning the complete API details, and two, giving me the complete flowchart of the application of the API details. Understanding the context of the project is something that is so important before development. Amazon Q solves this amazingly. For all the developers who are in the process of migrating the applications from Java 7, Java 8, or Java 17, it drastically helps them because they do not need to specifically go to some classes and make changes manually. Instead, they just turn on the agentic mode and then ask it to migrate the complete project into Java 17, which would eventually take time, but figuring it out is simple in terms of manual work. Figuring it out has been a greater solution with Amazon Q rather than the manual work. Also, the important point here is that even in the automation, connecting to the MCP servers and then making changes and then getting all the details in a PDF, in a text format and MD format. It had a greater impact on the development side, on the product side, on the automation side. Importantly, all the salespeople out there, I heard from them saying that they would be using Amazon Q for getting all the knowledge of the applications instead of relying on the developers for the knowledge. This is a drastic change, and it is just with a matter of a prompt that I give to Amazon Q that helps me in all the understanding and development and debugging and automation of the complete applications.

One improvement for Amazon Q is that I use it in Visual Studio, and in Visual Studio, I am not given an option to upload an image in Amazon Q. Also, this is one part of it. The second part is the context window of Amazon Q is very less compared to other GenAI tools. The moment I would be in a deep research or deep development or deep debugging mode in Amazon Q, the moment I hit the context length of the window, it would ask me to clear the complete context, and it would lose the complete context of the chat that I had previously. The two major pain points are that I have Amazon Q in Visual Studio, but I am not given an option to upload an image as a reference in Amazon Q. The second part is the context window is so limited. The moment I deep dive into some discussion in terms of development or debugging or automation, I hit a context length of the window, and the moment I hit it, it would lose the complete context. It has an option of summarizing the complete context and having it as a memory, but it would not be sufficient because I would have given a lot of details in the chat by that time.

I have mentioned the two points earlier, so those are the only two points that I have in mind for improvements needed for Amazon Q.

I have been using Amazon Q for about one to one and a half years.

Amazon Q is stable.

Amazon Q's scalability is very good.

The customer support for Amazon Q is fantastic because the moment I encounter some issues in Amazon Q, I reach out to them and they help me in figuring it out, and they help me in rapidly closing that issue. The moment I encounter any issues, they help me in solving them. The customer support is great.

I use GitHub Copilot as well. I did not switch really to Amazon Q, but I use it in parallel. I do a lot of development using all the GenAI tools out there. Out of all these tools, Amazon Q stands tall as it takes a lot of time from me, and I really rely on these GenAI tools, but the top of the chart is Amazon Q. It is not really a switching matter that I do, but I use it in parallel with all the other tools out there.

I did not really evaluate other options before choosing Amazon Q, but I was given both tools called Copilot and Amazon Q. I did a lot of development in Copilot. After that, once I had Amazon Q and AWS projects, I was encountering a lot of issues that were in AWS. I thought Amazon Q would solve it nicely. With that intuition, I went ahead and used Amazon Q, and then I started falling in love with Amazon Q because it was able to help me in a lot of debugging and a lot of development and a lot of automation. I did evaluate GitHub Copilot, but once I got into AWS projects, I was completely into AWS and Amazon Q.

My experience with pricing, setup cost, and licensing for Amazon Q is that the organization has provided me with an enterprise plan. Amazon Q was not completely given to all the developers out there, but it was given to most of the developers who do a major portion of work and most of the automation people who do a major automation portion. I assume that the organization would have dealt with the enterprise plan, but I really do not know if it was pricing high, which led them not to give access for all the people out there. I purchased Amazon Q through the AWS Marketplace.

There is a lot of return on investment from using Amazon Q because the number of developers needed or the number of researchers needed, the number of automation people needed has been drastically reduced. With the use of Amazon Q, the dependency on the DevOps team or the dependency on senior developers has been completely removed. One more important metric is the scale at which we were deploying applications to production has been drastically increased with the use of Amazon Q. Overall, there is a lot of increase in the movement of moving things to production grade and building things that are production grade from earlier, and the number of people that are required to build that scale of applications has been drastically reduced. This is a win situation for Amazon Q.

In the migration of Java applications from older versions to new versions, it usually takes a minimum of one quarter or two quarters or three quarters of time. But in the last quarter, I was able to migrate the whole applications of my organization into Java 17, which is the latest version. I was able to do it in about ninety days. It is a tremendous achievement. Parallelly, I was able to enter into new product space wherein I was able to onboard new clients with the products that I built using this. I had two initiatives that were completely run by using GenAI, and Amazon Q was a major part of it. The two initiatives were completely written from scratch to production grade environment code and deployed and used by clients out there in about just ninety days. This itself shows a lot of capability and the strength that I got just by using Amazon Q. The products that I have built using Amazon Q and GenAI tools, they had a very good client number as well. It has a greater impact on the organization level.

My advice to others looking into using Amazon Q is very simple. Go and take a shot on Amazon Q and build cool applications. If someone has any existing project, go ahead and start analyzing the complete project just by giving the prompt in Amazon Q. Turn on agentic mode, go ahead and start building applications using agentic mode, and start debugging applications using agentic mode, and probably use it for all the visualizations that can be done in terms of the applications that I build. Someone can deeply research about the complete application and probably get a lot of ideas. There is a lot that can be done. Probably one is research, the second is amazing development, the third one is automation, and the fourth one is debugging a lot of existing issues and probably putting a fix using Amazon Q. The only advice that I would give is to go ahead, purchase Amazon Q, start building applications, and get hands dirty. This is how to do it. Once someone gets hands dirty using Amazon Q, it would help them figure out the developer inside them. I give this product a rating of eight point five out of ten. Go ahead and pick Amazon Q and start building.

My use cases for Amazon Q involve producing the premium service of Amazon Q that we got access to from the company. We usually use it for different purposes. One of the purposes is that we use it for testing when developing modules and software modules. We run the test cases and write them using it, doing automation testing with it.

Apart from this, I often use it to get an idea about the product. For example, I have a code base right now, and I did a plug-in inside my editor, Versus Code, the Amazon Q editor plug-in. I give permission to scan through my code base and get the context of the product to understand the different coding patterns and the code structure. If I plan to work on a new module or feature, I just prompt it with the details, and it gives me the context about the flow of that module, understanding the existing flow of the code base. Additionally, I am writing unit tests with Amazon Q right now.

What I find best about Amazon Q is that I have used multiple AI tools such as Copilot and earlier Chat GPT. I think that, apart from the other tools, Amazon Q has an edge because if I want to run any command, such as scanning my whole database and checking schemas, it can generate the command and ask for permission whether I want to execute it. I can directly run that command from there, which I find is an advantage compared to other AI tools.

I often use it to get an idea about the product. For example, I have a code base right now, and I did a plug-in inside my editor, Versus Code, the Amazon Q editor plug-in. I give permission to scan through my code base and get the context of the product to understand the different coding patterns and the code structure. If I plan to work on a new module or feature, I just prompt it with the details, and it gives me the context about the flow of that module, understanding the existing flow of the code base. Additionally, I am writing unit tests with Amazon Q right now. From one to ten, I can give Amazon Q an eight point five, comparing it to other tools.

In terms of whether Amazon Q is overall easy to use, I feel it is somewhat the same in terms of usage. The UI is friendly, but there are a few things I face issues with, such as the number of tabs you can use. In the UI version, you can only use a maximum of ten tabs at a time, which is a limitation I encounter. Also, when scanning a code base with many files, it stops and gives a message that the context is too large, which I feel is a restriction. However, there are great feature points, such as being able to select a code snippet to fix or explain directly. These edge points are things that I feel are not available in other AI tools.

When it comes to issues with the stability of Amazon Q, I have not experienced bugs per se, but if I use multiple tabs, I feel it does not manage the context between them. For example, if I start with a prompt in one tab and then try to continue in another, it does not retain that context. In instances where I use only a single tab, it seems to have memory issues, so I need to stop and give the same context again in a new tab to resolve the issue. Also, when scanning a large number of files, there are limitations there.

I have been using Amazon Q for almost a month now.

When it comes to issues with the stability of Amazon Q, I have not experienced bugs per se, but if I use multiple tabs, I feel it does not manage the context between them. For example, if I start with a prompt in one tab and then try to continue in another, it does not retain that context. In instances where I use only a single tab, it seems to have memory issues, so I need to stop and give the same context again in a new tab to resolve the issue. Also, when scanning a large number of files, there are limitations there.

As for my thoughts on the support team from Amazon Q, I am not sure right now. I am a user of Amazon Q; we have other members who manage things at a higher level. Those team members reach out to Amazon if they face issues during setup or have dependencies. I am just using it as a tool; I am not directly interacting with Amazon.

Positive

Regarding the initial setup of Amazon Q, I find it easy; I just had to copy the URL and paste it there, and it was ready to go. I just had to sign in, and that was it.

I have used Copilot and cannot say it is not a good tool; it has its own features. However, Amazon Q's ability to directly interact with your CLI is a significant plus point.

In our organization, everybody is using Amazon Q because it is the only AI tool allowed. We are not allowed to use Copilot or other AI tools due to data security concerns around health-related products. While I would recommend it to other associates in our organization, I am not sure if it is free or not since I got the link from my team. If many people usually look for free versions, I will definitely recommend it; however, I would not expect people to jump directly to the subscription version.

I want to note that I prefer not to be completely anonymous. However, if I mention the company's name, it raises privacy issues, so I think limiting that is fine.

On a scale of one to ten, I rate Amazon Q an 8.5.

Amazon Q is primarily used to find employees' internet information, summarize documentation, access enterprise data sources, and create low-code AI applications. Amazon Q has built-in native software engineering capabilities as well as IT professional self-coding features that help write new code, debug errors, scan for security vulnerabilities, and manage AWS console resources. From the enterprise level, we can create deep integration with the larger Amazon family.

I have created a specific dashboard for seven use cases for the enterprise AI structure using Amazon Q, which helps us to consolidate log sources and parse them. The dashboard consolidates all telemetry data from end-users or servers into a single structure, helping us visualize data pointers in a structured way so that our enterprise security architecture remains robust. All deep integrations can be seen directly from the management console. The chat tools, Microsoft Teams, and personal platforms are much more useful, helping us serve any application relevant to the business use case.

The integration workflow with data is what fits the bill for our use case.

In terms of configuration, business use case, integration, administrative automation, and agentic workflows, Amazon Q has enhanced the business workflow in my organization.

I can justify that we have saved considerable time and effort in the automation process because of Amazon Q. The query, API call, and response driven by Amazon Q are robust, and I am satisfied with the outcome.

Amazon Q offers native API integration, specialized business use cases, and a coding structure so that all development tools are integrated. From the developer's perspective, they can visualize data in a structured manner, which can be leveraged by the business.

The native API integration helps us connect all endpoints and interfaces on a single dashboard. I have created almost fifty APIs for identity, knowledge assessment, and the prebuilt web console. When we pull data sources from the portal to the mobile application and internet connections, they are served through API. The core use case revolves around the identity and action portal I have created. By integrating multiple repositories scattered around the globe, API enhances the front-end, back-end, chat interface, and plugins for back-end integration, serving native API integration as a built-in structure offered by Amazon Q. It also enhances the index layer and agentic workflow.

I am satisfied with the features offered by Amazon Q.

Amazon Q has various areas for improvement where Amazon is not entirely improving the product stack as a holistic offering. From the development perspective, considerable pivoting is needed. Non-developer users in a corporate setup find it challenging because not every user is native to the AWS environment. AWS transition for business applications is layered on Amazon Q, requiring significant synergy to bring rapid improvements, especially in how autonomous agents can handle regular activities related to cross-department processes, API calls, and multi-data set analytics. Integration for analysis is much needed, which currently lacks in Amazon Q.

The needed improvements include working on code generation accuracy and the migration strategy to various other platforms.

The governance and security within Amazon Q are not robust at this time.

I have been using Amazon Q for the past three years.

Amazon Q is stable.

Amazon Q's scalability is robust.

Customer support is primarily agentic driven with a dedicated customer success manager.

Six months ago, I used a different solution, but it would not be relevant to mention.

Amazon Q requires a larger team size, but it has saved costs and time efforts in the past.

My company has built a built-in licensing structure for Amazon Q. The experience with pricing, setup cost, and licensing is smooth.

This option was evaluated by another vendor, and the CTO decided to transition and upgrade our solutions to be part of the Amazon Web Services family.

I would rate Amazon Q an eight out of ten. I chose eight out of ten because based on my observations, Amazon Q cannot be rated as a ten currently due to the migration, workforce methods, and automation agents' integration not being fully equipped within the DevSecOps cycle. If Amazon addresses these improvement areas, I could consider a ten out of ten. However, based on my exposure and the work environment I have built, it could always be more than seven, hence I gave it an eight.

The accuracy and reliability of Amazon Q's output depend completely on the architecture and structure of the application. Amazon Q serves as an add-on application to the holistic AWS stack and does not have its own native structure or development stack. The architecture is built by users, influenced by their business use case.

We use AWS and Oracle as our cloud providers.

My advice to others looking into using Amazon Q is that a robust architecture is needed, and understanding the basics of the AWS family environment can enhance capabilities and integration with other API calls, improving structure and visibility. My overall rating for this solution is eight out of ten.

On a day-to-day basis, I frame prompts and provide them to Amazon Q, and most of the time, I ask it to debug if there are any issues in my code.

For example, a recent instance involved working on a piece of back-end code that was not working or behaving as expected. I pasted the relevant code and explained the expected behavior, described the error I was seeing, and provided some context about the application. Amazon Q analyzed the code and suggested a few possible causes along with updated implementations, which helped me narrow down the issue much faster. Even when I did not use its solution exactly as provided, I was able to figure out where the issue was, and it reduced the troubleshooting time significantly.

A main use case for Amazon Q is that I use it on a day-to-day basis for coding assistance during my software development work. I primarily use it to understand or explain existing code that has been written by other people in my organization, wanting to understand it in a way that is more fruitful from the standpoint of learning. I can ask Amazon Q directly and validate the suggested solution before I implement it, which overall improves the way I work, helping me work more efficiently and speeding up my day-to-day development tasks.

The best features that stand out to me are code generation and code explanation, as well as debugging assistance. I also appreciate how it understands natural language prompts, which means I do not have to phrase everything in technical terms. Amazon Q quickly generates boilerplate code for me to get started, explains unfamiliar code, and suggests fixes for errors, saving significant development time.

Another valuable feature is its assistive capabilities in documentation, where it provides guidelines when I share documents with it, along with options when I ask for boilerplate or reference points, helping me manage my work effectively.

There is a noticeable impact on productivity because I spend less time searching through online search tools and documentation. I can provide Amazon Q with what I need, such as a starting point and my thought process, and it gives me existing code or debugs an issue. I review and validate the suggestions, allowing me to complete tasks more efficiently. I estimate that Amazon Q has improved my development productivity by around twenty to thirty percent on routine coding and troubleshooting tasks.

My experience with Amazon Q has been positive, but I think it would be better if it improved in some areas. Sometimes the generated code does not align with my project's existing coding standards or architecture, requiring me to manually review and refine it. While it helps with logic, sometimes the coding standards do not match, meaning I need to adjust it again. Additionally, I wish for more accurate suggestions for complex, project-specific codebases and clearer explanations for why particular solutions are recommended.

If I had to select one priority, it would be better to have context awareness for large codebases and development sessions, making suggestions even more relevant and reducing the need to repeat context.

I have been using Amazon Q for quite a long time.

I find Amazon Q quite stable; I did not face any issues or downtime at any point.

Regarding scalability, I think Amazon Q is quite good; it can efficiently add to multiple projects and handle increased workloads because it is an AWS-provided solution.

I have previously used GitHub Copilot along with traditional resources. GitHub Copilot was helpful, but I find Amazon Q to be an excellent addition to my development workflow for code explanation, debugging, and answering development-related questions.

I find it quite easy to get started with Amazon Q; the initial setup, while requiring permissions for data files and the need for context, was smooth. Overall, the onboarding process was productive, and I did not face many challenges.

Amazon Q integrates very seamlessly; I can add it as a plug-in, and it works once I have the credentials.

Although I do not have company-wide ROI figures, based on my experience, tasks such as understanding unfamiliar code and creating boilerplate implementations are noticeably faster, allowing me to spend more time on business logic and problem-solving instead of repetitive tasks.

Regarding pricing, setup cost, and licensing, I think it is worth the investment because it saves time on coding, and the productivity gains can justify the cost, especially for teams that use it regularly. I find the pricing fair enough; while I was not directly involved, I know it is not that cheap but also not overly expensive, depending on the team's budget.

I generally estimate the twenty to thirty percent improvement based on my day-to-day experience rather than formal KPIs or tracked metrics. Before using Amazon Q, I spent more time searching documentation and online forums and trying different approaches to solve problems. Now I get a starting point much faster, and the biggest improvement has been in repetitive tasks such as generating boilerplate code or understanding unfamiliar code and debugging, which I now assign to Amazon Q to generate something for me to review. Overall, I reduce the time spent on research, leading to an increased speed of around twenty to thirty percent in my development tasks.

Regarding Amazon Q's accuracy and reliability of output, I find that its accuracy is quite good, especially when I provide a clear and detailed prompt. For common development tasks, the code explanation, debugging, and responses are usually reliable and relevant. For more complex or project-specific scenarios, I treat Amazon Q's outputs as a starting point in my thought process for final answers, always validating the generated code before integrating it. In most cases, Amazon Q reduces the effort needed to reach a solution.

From my experience, Amazon Q handles complex coding tasks quite well and also helps with code implementation and debugging. However, for large projects or long development sessions, I find that I need to provide additional context again, as it relies completely on my prompts.

My advice for others looking into using Amazon Q is to spend time learning to write effective prompts, as that makes the biggest difference in output quality. Providing enough context, including relevant code, the expected behavior, and any error messages instead of asking general questions is also vital. Treat Amazon Q as a development assistant rather than relying on it blindly, and remember to review and test the generated code before using it. I would rate my overall experience with Amazon Q as a nine out of ten.

Our primary use case for Amazon Q was for document search as we have multiple documents. We use it as a document search with question-answer based QA pairs based on our documents for the end user. Instead of going inside the document, the end user will directly search within related documents and the information will appear through it.

In our primary use case to search within documents with Amazon Q, while searching within the documents, in a single prompt, we were able to search within three to four documents at a time. That's a good signal for us. At some points, it hallucinates at the moment and doesn't give us the correct results, but we are expecting 95% accurate results, and it is providing us that level of accuracy. That's good for us.

It's a good service provided by AWS, and we appreciate it because they are providing multiple connectors to data sources to connect with Amazon Q. It's easy for us to connect with any type of data source such as Jira, MongoDB, or Amazon S3 bucket. There are around 73 connectors. We have explored quite a few of them, and we find it best for our use case. Their system gives the answers accurately, and it is the solution that we are actually looking for.

The significant features of Amazon Q include their syncing platform, which means once you have your database updated, you can sync it, and the information gets updated in their platform as well. Additionally, setting guardrails and authentication is within that application, so we have used that to distinguish different documents for different users.

The benefits of Amazon Q are that you don't need to build any code base at the backend to develop your RAG system or AI LLM-based summarization systems to do question-answer sets on the documents. It's a pre-built system we get to use, which is a good advantage for us. We have tested it for one use case only as our primary focus was on that specific functionality.

There isn't such an issue we have faced with Amazon Q regarding speed increasing. Syncing and indexing takes a lot of time, and they need to improve upon that. Remaining everything is good for us, and that is also acceptable as we can set it as a nightly job. Once it's done, it takes around one hour max for any number of documents.

We were trying to address specific issues and challenges by implementing Amazon Q in our environment because currently, they don't provide any APIs directly. We find it difficult to integrate with our product. The second challenge is while connecting Jira, we need the ACLs to maintain our security, but it doesn't allow us to connect to Jira if our ACLs are on. We need to turn them off to connect to it. Even though we connected with the support team of AWS, they were not able to resolve our issue, so we were disappointed at that moment.

As a part of improvement, we don't see any improvement areas for Amazon Q at present. We first need to test that we can integrate it with our product. We need the APIs before we can suggest improvements.

I have worked on Amazon Q for around six months.

Amazon Q was working perfectly fine. There's no downtime or other issues.

We find Amazon Q scalable. We started with five documents, then increased it to ten. Then we increased it with four types of data sources. Simultaneously, we increased the document size as well as the data connectors. It's scalable from a user point of view.

The technical support for Amazon Q was average. On a scale of 1 to 10, I would rate it as six because we have not received any solutions from their end. Even though we connected to many team members from junior to senior, they weren't able to help us. We were very disappointed at that moment.

Neutral

We were looking for offline services, but as many of our services use AWS, we decided to go with Amazon Q itself. It was ready and we didn't have to build anything, but later on, we discovered that it doesn't provide any APIs to us. We have kept it on hold as of now. We have tested it completely, set the guardrails, used many of the data connectors, shared the URLs, added users, and shared that URL with the team. Many people have tested it, and we have received positive feedback from them. Unless they provide us the APIs, we are not sure that we can use it further.

The initial setup process of Amazon Q was straightforward for us. We have not faced any challenges. As long as anyone is familiar with AWS, knows how to sign up for the service, and how to opt-out for the service, then they can easily use it. There's no hesitation in that.

As a service, everything is fine for us with Amazon Q. It's good to use and anybody can opt for it. They need to work on the costing as it is too high. It has two plans, Business and Pro. There's an issue that it automatically switches from Business to Pro versions in the middle of your work. You need to keep track of that and keep an eye on everything to ensure that you are on the right subscription plan because it costs more than we were expecting.

We find their costing too high with Amazon Q because once we use its services, we need to give it to our end users as well. It should be quite decent. Even though we were planning to test the upgraded version of it, Amazon Bedrock, the upgraded version of Amazon Q, the same issue persisted that its costing was too high. We were not able to reach the point of that costing.

We are evaluating other products such as Landing AI and Azure AI Studio in comparison to Amazon Q. They provide us a similar kind of platform. There, all you have to do is give the document link or data source links. It's almost the same, but compared to Amazon Q, they are at a backward stage. Amazon Q is more upgraded, allowing us to set guardrails from a user perspective. I would recommend Amazon Q as a first choice if you are looking for any of those services.

If you are going for a specific task with Amazon Q such as QA setups or any information-related tasks within the organization or apart from the organization, it's a good choice because it can be quite frustrating to go through each document or each data source or any Jira tickets. You can easily do the natural prompting chat chatbot thing. It's great to use. My overall rating for Amazon Q is 9 out of 10.

Regarding the use cases for Amazon Q, my main intention is to explore the services as I am in college. Besides that, I mainly use it for code generation for AWS services, such as uploading to S3, creating a Lambda function, launching an EC2 instance, and connecting to DynamoDB. These are some basic use cases for me, such as automatically generating boilerplate code for common AWS tasks, such as writing Python code to upload a file to S3 using BOTO3 with error handling.

It instantly helps troubleshoot AWS errors by explaining cryptic error messages, such as what 'access denied' means in API Gateway and suggesting IAM policy fixes. Another use case is creating or troubleshooting CloudFormation or Terraform scripts to generate a CloudFormation template for a Lambda with an S3 trigger or fixing CDK Python code for deploying an ECS cluster.

I also find it useful for writing and testing Lambda functions, generating and optimizing AWS Lambda code for various runtimes, and providing IAM policy assistance. Quickly generating backend APIs using API Gateway plus Lambda is another significant benefit. I use it for learning and documentation support, summarizing AWS service documentation, and explaining best practices, which is great for me as a student. I also inquire about cloud cost optimization to find ways to reduce AWS costs based on my architecture.

I particularly appreciate that Amazon Q offers fast and context-aware responses because it understands the development context and provides relevant answers that save time. The AWS integration is excellent, as smooth interaction with AWS services makes it easy to manage cloud tasks directly from the IDE. The code suggestions provide intelligent recommendations and explanations, reducing debugging time and helping me write cleaner code. I appreciate the ability to ask questions in plain English and get technical responses without needing to search through documentation.

Amazon Q developer scales efficiently in terms of usage across different project sizes, teams, and workloads, as it works effectively for solo developers and has the potential for larger teams, especially when integrated into shared AWS environments. It supports multiple languages and frameworks, scaling across various stacks, ensuring consistent performance by maintaining responsiveness even in large code bases or complex AWS architectures.

Deeper IDE integration is necessary for Amazon Q Developer because it could be even more useful with better real-time integration with local debugging tools. While great for standard tasks, it sometimes struggles with more complex or multi-layered problems in large code bases. Enhancing user-specific customization, such as remembering preferred languages, frameworks, or AWS services, would improve long-term usability.

I have been working with Amazon Q for almost six to seven months and found Amazon Q Developer to be a powerful and efficient AI assistant that significantly enhances developer productivity.

I encountered a minor issue during the setup related to an authentication permission plugin not activating, and I discussed this with the technical staff.

Amazon Q Developer proves to be generally stable and reliable during daily development tasks. It maintains consistent performance, rarely crashing or lagging, even during prolonged use. The IDE integration runs smoothly inside VS Code and other supported IDEs without disrupting the workflow.

I have not encountered frequent bugs, misfires, or unexpected behavior, although there are a few areas for improvement. Occasionally, the plugin may take extra time to respond or require a refresh when internet connectivity fluctuates, and in rare cases, it might misinterpret complex prompts in deeply nested code bases. Based on this assessment, the stability rates between 8.5 and 9 out of 10, as it is stable for daily professional use. With slight refinements in memory handling and offline fallback, it could achieve full marks.

For improvement, I suggest enhancing admin control or original level settings, utilizing analytics, and sharing prompt or response history. In rating scalability, it deserves 9 out of 10.

I have had one experience communicating with the technical support of Amazon Q when the AWS tech support team reached me on LinkedIn while I was completing certifications. At that moment, I reached out to tech support regarding debugging access permissions, plugin installations, and unexpected behavior in the IDE because the response time was reasonable, and the support team was knowledgeable and professional. They helped resolve the issue I faced. It would be helpful if Amazon Q Developer could escalate and resolve queries directly.

When rating the technical support from 1 to 10, it rates 8 out of 10, as the support team was responsible and knowledgeable, which accounts for two points. The efficiency and effectiveness in resolving issues also earn two points, while clear communication merits another two points. Two points were deducted due to slight room for improvement in speed and direct integration with the Amazon Q developer interface, such as ticketing or automated help inside the IDE.

Before using Amazon Q, I explored Google Cloud Developer and other tools such as Google VEO3 and open AI agents. While working with Google Cloud, I encountered various services, and after gaining some security-related certificates, my mentor recommended exploring Amazon Q Developer for its deep AWS integration and developer-focused assistance. Comparing Amazon Q Developer with Google Cloud tools, Amazon Q Developer is stronger in its integration with AWS services, while Google Cloud tools feel slightly more polished due to their focus on collaborative features, making them better suited for data engineers and AI/ML use cases.

I explored Amazon Q with guidance from my college mentor on the setup process. My overall experience with Amazon Q Developer has been positive, as the installation and configuration process is mostly smooth. The plugin integrates with my IDE, and connecting it to my AWS account is straightforward, thanks to clear documentation.

The time taken for installing Amazon Q Developer is relatively quick and straightforward, totaling around 5 to 10 minutes. This includes steps such as installing the plugin extension in IDE such as Visual Studio Code, signing in with AWS credentials, granting permissions for account access, and configuring AWS profile and region preferences. There are no major delays unless network connectivity or authentication issues arise.

While using Amazon Q, I find it pricey, especially as a student struggling with finances; I have taken loans and received credits through my mentor to afford it. Many users share this view that it can be expensive, especially considering new tools such as ChatGPT's premium version that represents significant costs. However, Amazon Q Developer isn't prohibitively expensive when viewed in the context of its value for AWS users. Many use cases benefit from free tier access, significantly enhancing productivity to justify future costs. It ultimately reduces setup time, debugging hours, and support tickets, making its fees reasonable for those able to afford it; it's just a personal challenge given my financial situation.

Amazon Q Developer is a promising and evolving tool that is already valuable for day-to-day development tasks, especially within the AWS ecosystem. With a few refinements, it could become an essential part of every developer's workflow.

When rating Amazon Q on a scale from 1 to 10, it deserves a 9 out of 10 because it scales efficiently for individual developers and larger teams, handling both small and large AWS projects without performance drops while supporting a wide range of AWS services and workflows. What prevents it from receiving a full 10 out of 10 is the lack of team-wide admin tools, such as centralized settings and analytics, plus its ongoing maturity for enterprise rollout and collaboration features.

I have completed a project where the company required testing R&D on Kubernetes. I tested it locally by installing MiniKube, Kubernetes, and all the containers. I configured the Kubernetes MCB server to Amazon Q. Once the configuration was done, I could manage all the Kubernetes clusters using Amazon Q prompt. When I want to check any pods in the Kubernetes cluster, I do not need to use commands. I can simply write a prompt such as 'Please show me the Kubernetes pods and namespace and all.' Amazon Q automatically provides all the required details.

Once the configuration is complete, users can manage all Kubernetes clusters using Amazon Q prompt. When checking pods in the Kubernetes cluster, there is no need to use commands. Users can simply write a prompt such as 'Please show me the Kubernetes pods and namespace and all.' Amazon Q automatically provides all the required details.

While using Amazon Q, I faced some challenges, such as navigating the interface initially.

I have been using Amazon Q for a while now.

In terms of stability, Amazon Q is stable and performs reliably without major issues.

My impressions on the scalability of Amazon Q are positive; it efficiently handles increased loads.

The initial setup and deployment of Amazon Q are easy to do, and I didn't encounter any difficulties during this process.

I find Amazon Q easy to use, and I believe anyone can use it without needing extensive technical knowledge.

I would definitely recommend Amazon Q to other people; it's a great tool. I find it quite satisfactory.

On a scale of 1-10, I rate Amazon Q an 8.

We have been using AWS services for almost three years, with Amazon Q specifically for the last one and a half years.

We use Amazon Q for document-related use cases where we need to summarize documents related to GenAI and find differentiation between financial and legal documents. We are currently exploring integration of Amazon Q into our data analysis and analytics reports. Another use case involves creating a chatbot at the enterprise level where we can integrate all the company's knowledge base to serve as a chatbot for internal employees.

Regarding data querying, I am not certain because we have not implemented any particular use case with Amazon Q for this purpose. We have integrated it with our current knowledge base, where it functions effectively. Amazon Q has the potential to work with Amazon Quicksight or Athena, though we have not utilized these features yet.

For developers, Amazon Q's IDE integration is exceptional as it provides suggestions for code generation. Its SDK support is quite robust. The document summarization feature of Amazon Q is comparable to ChatGPT or OpenAI models. It can be easily integrated with Microsoft 365, Google Workplace, Slack, Notion, or enterprise tools such as Jira or Salesforce.

Amazon Q understands natural language queries effectively and interacts robustly with company-specific data. Setting up guidelines and context is easier compared to other LLMs, performing particularly well with a RAG approach-based bot. Amazon Q is highly customizable, making it simple to fine-tune with company-specific instructions, sources, and knowledge base.

A significant advantage is that company data is not used to train Amazon Q's foundation model, ensuring data privacy. It uses IAM roles, SSO, and group permissions. The auto-logging feature allows tracking of incorrect information or hallucinations, enabling us to identify where issues occurred in the Q activity logs.

In our organization, Amazon Q excels at document handling, differentiation, and chatbot applications. We developed an HR bot that accurately handled queries about pay structure and leave policies. It performs exceptionally well with text-heavy documents that don't contain images. The deep integration with AWS services is advantageous, allowing integration with Amazon S3 bucket for data storage and reference. Its natural language interaction makes it accessible for non-technical users. The enterprise-level licenses are robust, providing confidence in management with enterprise-grade security through AWS Bedrock, Titan, and Anthropic Claude model.

When updates occur in Anthropic models after implementing guard rails or instruction-based flows, we must revisit everything from scratch due to hallucination issues or unexpected outputs. Additionally, Amazon Q sometimes fails to follow specific output format instructions, instead providing summarized information in a different format.

The multimodal capabilities of Amazon Q are limited, lacking the ability to process or generate images. When attempting to generate enterprise-level reports requiring both text and images, it struggles to combine elements in the specified format despite clear instructions.

The integration costs are considerable, making the pricing structure less feasible for scalable solutions. After successful POCs, scaling at an enterprise level becomes cost-prohibitive. Developers have reported that Amazon Q plugins in IDEs consume significant CPU resources, necessitating high-end hardware that may not be available to all employees.

Data analytics and querying capabilities show limitations, particularly when handling Excel files and performing operations requiring accurate, non-hallucinated output. Advanced code generation features are lacking, including the inability to generate comprehensive unit tests or handle complex refactoring across multiple files. The platform doesn't automatically identify security or performance bugs in code.

Data cleaning and ETL tools are insufficient for enterprise-level analytics or visualization. Amazon Q struggles with parsing tables and understanding complex documents containing combinations of charts, numbers, and text. There is also no session awareness, meaning context is lost when sessions are closed and reopened.

Downtime has been minimal, with one notable instance last year when the LLMs were not functioning. The main ongoing challenge is managing updates from AWS or Anthropic, as there is no proactive solution to assess impact on production deployments before implementation.

We have been using AWS services for almost three years, with Amazon Q specifically for the last one and a half years.

The initial setup of Amazon Q presented some challenges. The Amazon team assisted with system setup, but region conflicts posed a significant issue. Using the Virginia region while complying with DPDP (Data Privacy and Data Protection) requirements created challenges for our heavily regulated company. The process of setting up the environment and integrating Amazon Q with various systems took three to four days to resolve. While the implementation across the organization for developers was moderately challenging, operations became smooth after the initial setup.

Scalability has been a strong point for Amazon Q due to its integration capabilities with other AWS services, including Amazon S3, EC2, and DC3. The integration capabilities have eliminated any significant scalability challenges.

Based on a scale where 10 is the highest, I would rate the customer service at 7.5 or 8. The support team was helpful, though there were challenges in setting up the environment that could have been streamlined better. This rating reflects the support provided to our company.

Positive

We have utilized GitHub Copilot and Replit. We are currently evaluating Google's Studio Firebase among other competitor tools to assess their capabilities.

For small projects such as HR bots or enterprise bots for internal employees, calculating ROI is challenging. In the Indian context, where employee costs are lower than in European or US countries, implementing Amazon Q for contact centers across India becomes substantially expensive due to high token costs from agent interactions and document references. The cost-benefit analysis shows neutral results, but we lose human sophistication in the process. Management remains skeptical about spending equivalent amounts while sacrificing human expertise. However, with increasing model sophistication and potential decreases in token costs, this may better align with business goals in the future.

Replit and Cursor offer notable alternatives. Replit excels in generating complete project requirements. When given clear instructions for developing an application with specific page structures, it automatically generates all necessary dependency files for various programming languages. It creates readme files, dependency files, Python files, and other required project files. Replit recently added domain purchasing capabilities and server deployment options, providing an end-to-end development journey. GitHub is developing similar features to compete in this space. This comprehensive approach reduces the need for repeated model calls for different project components.

With a review rating of 7 out of 10, I would recommend Amazon Q. A major advantage is the comprehensive AWS support and integration capabilities. The platform offers extensive integration possibilities with enterprise-level solutions such as Salesforce and others. Once the initial setup is complete, operations proceed smoothly, making it particularly suitable for POCs and small-level projects.

In my project, I have used Amazon Q in the enterprise version of a pro version. I have used it in Visual Studio and Eclipse as an add-on.

As a Test Automation Architect, I have utilized Amazon Q for building my project framework from scratch, seeking code suggestions, creating new test cases, and providing explanations for the test cases.

I also use it to generate README files when I post code on GitHub; it helps facilitate code pushing by providing Git commands for those who may not be familiar with Git. This significantly reduces the time spent on coding and test execution; tasks that originally needed a month are now completed in about two weeks. In my three-month POC, I noticed these benefits, including the quick explanations of existing code, which aid in knowledge transfer for new team members.

Working in testing, I encounter locators on webpages frequently. When elements change, I usually need to manually alter the XPath or other locators, which results in test failures. Instead, I have utilized Amazon Q to implement code changes that use API keys so that when an XPath fails, it automatically fetches the new locator from the page source and updates the code. This automation eliminates the need for manual changes and reduces execution time by around 50%.

Amazon Q aids my AI-driven data analysis projects significantly with self-healing capabilities, allowing me to handle issues with ease, which also reduces execution time by 50%.

Amazon Q offers valuable features such as documentation, which I find beneficial for KT sessions or for explaining large projects that cannot be covered in one sitting. By providing a README file, new personnel can understand the project better before we dive deeper in subsequent sessions. The explanation and documentation capabilities are excellent.

Additionally, the Git-related features allow me to inquire about any changes made weeks prior, providing not just explanations but also insights into the impact those changes have on the code.

If starting from scratch, it suggests new test cases and adds necessary validations or assertions on its own. The recent Agentic coding feature allows the tool to implement significant changes automatically, making it easier to maintain code by committing and pushing changes seamlessly while allowing for an easy undo option.

This significantly reduces the time spent on coding and test execution; tasks that originally needed a month are now completed in about two weeks. In my three-month POC, I noticed these benefits, including the quick explanations of existing code, which aid in knowledge transfer for new team members.

Regarding the initial setup and the deployment process of Amazon Q, I did not face any difficulties. My organization provided credentials, and there were no issues with the setup. However, I discovered that the application logs me out automatically after some time, which becomes problematic as I then lose access to my chat history. Each time I wish to return, I need to log back in and reauthenticate, which can be frustrating.

In terms of tools that can improve and speed up data processing in Amazon Q, I find that authentication keeps prompting me to log in, and it would be beneficial for history retention to be more efficient. Searching through history must be made easier because I often cannot find specific items when searching.

Aside from the logout issues we discussed, I would appreciate if Amazon Q could extend the login duration to at least 24 hours to make it more user-friendly.

I have been working with Amazon Q for three months, and for my POC, I have already worked three months, resulting in a total of six months.

Regarding the initial setup and the deployment process of Amazon Q, I did not face any difficulties. My organization provided credentials, and there were no issues with the setup.

Beyond the significant time savings I have already mentioned, I have not observed additional measurable benefits such as cost efficiency or ROI from the Amazon Q product.

Apart from Amazon Q, I generally use GPT as well, including the enterprise and open-source versions. However, I do not find them as helpful because Amazon Q requires fewer details when I input tasks; it is capable of understanding tagged inputs directly.

Before choosing Amazon Q, I evaluated other options, including GitHub Copilot. I found it to be less effective compared to the enterprise version of Amazon Q, particularly in code generation and providing helpful comments regarding assertions and validations.

As for disadvantages, in comparison to GitHub Copilot, one notable disadvantage of Amazon Q is that it requires a connection to update my code in Git directly, which is handled differently in GitHub Copilot.

I definitely encourage others to use Amazon Q, especially for code generation and knowledge sharing sessions regarding documentation. Particularly for professionals in the testing field, the self-healing feature is invaluable.

On a scale of 1-10, I rate Amazon Q an 8 out of 10.

The main use case is that I want to convert my code into another technology or upgrade code. For example, I am using Node.js version 18 and want to update to Node.js version 22, or I am using Next.js version 13 and want to update my code base to Next.js version 15. It comes in very handy when using Amazon Q, although it also needs many human touches, but it works absolutely fine if you have good knowledge of both versions.

I have been working with Amazon Q for around more than eight months, and it has been really engaging because it has context of all my code bases. My code base is huge, but it stores all the context and helps me significantly in doing heavy lifting. For instance, if I want to use cache, it understands the code base then implements cache, and it works fine, fabulous.

The best feature of Amazon Q is that it has knowledge of my entire code base, entire repository, and its flows. It is very useful when you have a very big project because if you want to change something, your AI assistant should know the context of that change. For example, if I am changing a variable name, it should know where this variable is used and also change those places. It is excellent in that regard that it has knowledge of my entire code base, and that is amazing.

While using Amazon Q, sometimes it gives unnecessary suggestions and tries to mimic the code bases, which is behavior that needs to be filtered out. Giving a suggestion every time is not a good choice; sometimes it is better to stay quiet. It also provides complicated code without any explanation or comments, and that could be improved. Additionally, it sometimes offers code that is not compatible with the current version of the project or libraries.

There are specific features I want to add to Amazon Q. For instance, if I want to write test cases for the project, there should be a command for that, and a command for generating documentation that works within the projects to document the code properly, not just creating a README file. Also, there should be a specific command for listing APIs and generating Swagger documentation to save time.

I have been working with it for around more than eight months.

When using third-party AI that syncs with the internet, there are security issues because we are not sure what we are using and what might happen to our data. However, using Amazon Q feels secure because as a trusted brand, I am not very concerned about it. Still, there should be configuration that specifies files Amazon Q should not touch.

I never used technical support because Amazon Q itself is a kind of technical support. I do not face many issues with Amazon Q, but there are some bugs when I start the developer Q chat mode. In the beginning, it cannot access my files, but that seems to take time; it might be an issue on my machine.

After some time, it starts referring to them.

Neutral

I used DeepSeek, which is also awesome.

Amazon Q is trained with good data, but it sometimes lags when I want to code for a specific task. DeepSeek is optimized for coding, although it does not have overall project context, while Amazon Q does; however, too much context can confuse it and lead to random results. DeepSeek tends to work well for specific parts of the code, which makes it optimized.

It is very easy to set up. Just install the extension and connect with your AWS account. Sometimes, you have to authenticate yourself weekly, but it is simple. Amazon Q even suggests if you are not authenticated, and you just click to authenticate; it redirects you to the browser. It is not hard if you are a developer.

I did not buy it; I just went there, started using it, and installed the extension. I authenticated my builder account, and then I just started using it. That is simple.

I have not explored AI-driven data analysis much. I mainly work on Node.js and MERN stack projects, so I have no idea about using AI in AI-related projects, but I guess it would work.

I know that if I am a project coordinator, I have a good idea about the project. If I left the company and a new developer wants to understand the architecture and flow, there should be a command to generate the project flow, an ER diagram and high-level design, integrating features such as Canva or Figma to visualize the code.

I would say you should have a good knowledge of your tech stack because AI is experimental. You cannot blindly trust any AI code editor because sometimes problems are subtle, and AI might not catch them. Debugging sometimes requires your knowledge, and it can only be done if you have expertise. AI is meant to support and accelerate your tasks, but it can give random results if you are not up to date.

On a scale of 1-10, I rate Amazon Q a 7 out of 10.