We use AWS for multiple purposes, such as developing APIs and API integration using API Gateway. We use API Gateway, Python Combinator, Lambda Glue, and ETL Process. We have used EMR for big data processing. If we need a tool for computing, we go with the Lamda DMS. There are many services available in AWS that meet our needs.
Senior Software Architect at USEReady
It covers a lot of services, including computing, networking, storage, IoT, and management
Pros and Cons
- "We use AWS for multiple purposes, such as developing APIs and API integration using API Gateway. We use API Gateway, Python Combinator, Lambda Glue, and ETL Process. We have used EMR for big data processing. If we need a tool for computing, we go with the Lamda DMS. There are many services available in AWS that meet our needs."
- "AWS has room for improvement on the Kubernetes side. I would like to go a little deeper into the Kubernetes target, Elastic, inner system, and all that. The EKS, target, and all these areas need to be improved, but that is not my key area because I am mostly working on the application side."
What is our primary use case?
What is most valuable?
The feature that's most valuable depends on your use case. Elasticsearch is good for testing and DynamoDb for database applications. There are so many things I could name, but you have to go with the service that is right for the use case you are looking for.
What needs improvement?
AWS has room for improvement on the Kubernetes side. I would like to go a little deeper into the Kubernetes target, Elastic, inner system, and all that. The EKS, target, and all these areas need to be improved, but that is not my key area because I am mostly working on the application side. However, I sometimes still need to work with Kubernetes container management.
For how long have I used the solution?
I've been using AWS for the last seven years.
Buyer's Guide
Amazon AWS
April 2025

Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
861,524 professionals have used our research since 2012.
What do I think about the stability of the solution?
AWS has "11 9s" service availability, which means the service is available 99.99999999999 percent of the time.
How are customer service and support?
I would rate AWS support four out of five. They're good. I can activate cases on the technical calendar through AWS development support. I've gotten a lot of support through AWS Blue.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment complexity depends on which template you're using: AWS Terraform or CloudFormation. It's easiest to deploy services via Terraform, so you can go with that. That is the most straightforward way, and you can do all automation within Terraform.
What other advice do I have?
I rate AWS nine out of 10. Everything is moving to the cloud now, and AWS covers a lot of services, including computing, networking, storage, IoT, and management, and they are good in every way.
They face competition from GCP and Azure, but Azure is entirely a Microsoft stack, so people will go with that when they're working with Microsoft solutions. It is a little cheaper than AWS. In the end, the cloud you choose depends on the use case. It's up to the customer.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer. Implementer

Senior Manager (Engineering Department) at a comms service provider with 10,001+ employees
Easy to use, multiple payment options, and highly reliable
Pros and Cons
- "The most valuable features of Amazon AWS are ease of use, deployment, and short lead time. If you are using an on-premise solution, you need to wait for the hardware, and nowadays it is very difficult, the lead time becomes very long. We propose to our customers to use Amazon AWS because it is very easy, no need to wait for hardware delivery."
- "If Amazon AWS can offer more self-paced learning tools, on their website, on CBT, it'll be easier for more people to familiarize themselves with their service. Especially when they are delivering new services from time to time. Educational tools that can help users familiarize themselves with their service. It would be great."
What is our primary use case?
The customer can deploy their application on Amazon AWS instead of taking care of their infrastructure.
What is most valuable?
The most valuable features of Amazon AWS are ease of use, deployment, and short lead time. If you are using an on-premise solution, you need to wait for the hardware, and nowadays it is very difficult, the lead time becomes very long. We propose to our customers to use Amazon AWS because it is very easy, no need to wait for hardware delivery.
What needs improvement?
If Amazon AWS can offer more self-paced learning tools, on their website, on CBT, it'll be easier for more people to familiarize themselves with their service. Especially when they are delivering new services from time to time. Educational tools that can help users familiarize themselves with their service. It would be great.
I know they have a Free Tier service, but they need to register their credit cards. Some of my colleagues have concerns. If the usage exceeds a certain value, they exceeded the Free Tier usage time and they will start charging your credit card. My colleagues forgot about the usage and credit card payments. They needed to pay for the additional amounts which they used on top of the Free Tier usage. If Amazon AWS could improve the free service model to be more user-friendly in a way of not using a credit card, that would be great.
For personal learning, you also need to register your credit card. You need to be careful or you will have to pay.
For how long have I used the solution?
I have been using Amazon AWS for approximately two years.
What do I think about the stability of the solution?
Amazon AWS is stable. However, they have had a few outages but nothing very serious.
What do I think about the scalability of the solution?
Amazon AWS is quite scalable. And they have a lot of auto-scaling functions for their VMs.
How are customer service and support?
I don't have direct information of the support from Amazon AWS because sometimes we are relying on Amazon's partner, not directly contacting Amazon AWS support teams. We need to have some support plan with Amazon AWS, otherwise, they will not provide direct email or technical support.
How was the initial setup?
The length of time and difficulty of the implementation depends on the scale and the complexity of the project.
What about the implementation team?
For the implementation of Amazon AWS, having two to three engineers focusing on it would be ideal. Small to middle size companies, don't have dedicated teams or engineers for a particular service.
What's my experience with pricing, setup cost, and licensing?
Amazon AWS is offering different pricing, and saving plans, it's very easy for a customer to consider the Amazon AWS service.
Amazon AWS charges based on the user usage and some software license, such as the OS are included in their monthly charge. The transparency is quite sufficient, the customer knows what they're paying for.
The usage fees are an OPEX and they are offered monthly or annually.
Which other solutions did I evaluate?
I have evaluated Microsoft Azure and Google Cloud.
What other advice do I have?
I would recommend Amazon AWS to others.
Amazon AWS are the market leaders in the public cloud service and after them, we have Microsoft Azure, and maybe Google Cloud.
I rate Amazon AWS an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Buyer's Guide
Amazon AWS
April 2025

Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
861,524 professionals have used our research since 2012.
Senior Sales Account Manager at a tech services company with 51-200 employees
Organization visibility, great support, and highly scalable
Pros and Cons
- "We have many projects where we can resolve a lot of issues with Amazon AWS. It has given customers a lot of visibility with their data. Many customers do not know what they can learn from their data and I provide them with this using useful information using Amazon AWS."
- "The difficulty of the implementation depends on the project. We have a lot of very complicated and complex project which make the implementation more difficult. However, a small project can be very simple to implement. In general, over 90% of the project tend to be complex implementations."
What is our primary use case?
We used Amazon AWS when we work on a lot of projects in different situations or scenarios. We have done migrations from on-premise to cloud computing, projects involving data analytics, artificial intelligence, and machine learning.
Many of our customers use the website application that is hosted by Amazon AWS.
What is most valuable?
We have many projects where we can resolve a lot of issues with Amazon AWS. It has given customers a lot of visibility with their data. Many customers do not know what they can learn from their data and I provide them with this using useful information using Amazon AWS.
The Redshift features are very useful for large amounts of data.
For how long have I used the solution?
I have been using Amazon AWS for approximately two years.
What do I think about the stability of the solution?
The solution is very stable.
What do I think about the scalability of the solution?
Amazon AWS is scalable and it is very important for our customers.
We have a lot of customers using this solution and our largest customer has approximately 16,000 users using the solution.
How are customer service and support?
The technical support is very good.
How was the initial setup?
The difficulty of the implementation depends on the project. We have a lot of very complicated and complex project which make the implementation more difficult. However, a small project can be very simple to implement. In general, over 90% of the project tend to be complex implementations.
What's my experience with pricing, setup cost, and licensing?
We are on an annual subscription for Amazon AWS.
What other advice do I have?
We create some processes to resolve some questions the customers have. They want to improve and have more visibility of their data, and how to extract information about their data. We help them with this problem.
Amazon AWS is the most important provider in the market. They have helped many of my customers.
I rate Amazon AWS a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
IT Solutions Architect at Canvia
Control Tower enables us to organize the different accounts our clients have
Pros and Cons
- "It's a very flexible and customizable service"
- "Monthly costs can be high if you don't maintain your usage"
What is our primary use case?
All of our clients look to migrate their workloads to the cloud and we propose the use of AWS depending on the technology of the client or the workload they want to migrate. Our primary use cases are workloadmigrations, infrastructure as a service (IaaS), sometimes platform as a service (PaaS) and software as a service (SaaS). We use different AWS services, Elastic cloud compute, Web application firewall, AWS firewall, LAMBDA, CloudTrail, and others.
What is most valuable?
AWS has a lot of services that are very good. One of the services I use is AWS Transit Gateway. This service allows me to communicate between different networks in different accounts. It's good for network communication. The other service I use a lot of is "Control Tower", it's a service used to organize the different accounts our clients have.
What needs improvement?
With regards to improving the service, I don't see any room for improvement at this time. I love the technology, it is a very good public cloud offering with very good services. Until now, there are no services that I don't like.
One other aspect, it would be good to see the basic service level improved with regards to response time. They don't offer 24-hour support.
For how long have I used the solution?
I have been using Amazon AWS for around two years.
What do I think about the stability of the solution?
AWS is very stable. They have an SLA of 99.99%.
What do I think about the scalability of the solution?
AWS is very scalable.
How are customer service and support?
My experience with AWS support is very good. There are four types of support: basic, free, business and premium. It depends on the level of support you have which determines how quickly they can respond about an incident, ticket or request you have.
How was the initial setup?
It's very easy to set up services in AWS. Depending on the solution you need to deploy it can be very quick. A virtual machine can be deployed in 5 minutes.
What about the implementation team?
Our company is a partner with Amazon, we implement in-house.
What's my experience with pricing, setup cost, and licensing?
What is hard with the public cloud service like AWS, is ensuring you maintain a good budget. Plan the monthly consumption properly. If you don't have the expertise in the cloud, your monthly cost can go very high. It's also very easy to set up services in AWS.
I would also suggest companies look for a good partner that has the necessary experience to deploy the services when moving to the cloud. It's very simple, but you need to design a very good architecture for cost optimization and performance.
What other advice do I have?
The solution is good for integration. It's very flexible and customizable with other services, public, cloud and on-premise.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer.
Integration Architect at a retailer with 10,001+ employees
The learning curve is shorter, but it needs better tools for monitoring performance and use
Pros and Cons
- "I like AWS for its scalability, reliability, and availability, and it's much more mature and user-friendly compared to some other cloud providers. The learning curve and time for deployment are also shorter."
- "Amazon needs to develop better tools for troubleshooting network traffic, application insights, performance, and even some aspects of integration mapping. I'm hoping AWS implements something like Azure's Network Watcher and a log analytics solution where a can pull logs from various services and present them in a single dashboard. I want to summarize the performance and usage of every service and application."
What is our primary use case?
You can design and customize solutions with AWS. It has so many options, including storage, computing, database, notification, and messaging solutions. It depends on what the application team designs.
What is most valuable?
I like AWS for its scalability, reliability, and availability, and it's much more mature and user-friendly compared to some other cloud providers. The learning curve and time for deployment are also shorter.
What needs improvement?
Amazon needs to develop better tools for troubleshooting network traffic, application insights, performance, and even some aspects of integration mapping. I'm hoping AWS implements something like Azure's Network Watcher and a log analytics solution where a can pull logs from various services and present them in a single dashboard. I want to summarize the performance and usage of every service and application.
What do I think about the scalability of the solution?
All cloud solutions are scalable. It depends on the design, but most of them scale well. There are tens of thousands of users working on the solution.
How are customer service and support?
Amazon technical support is great.
How was the initial setup?
Deploying AWS could be straightforward or complicated depending on the use case. If it's a simple application, you can deploy it within a day. If it's very complex and your team isn't experienced, it can take months.
The amount of maintenance needed depends on your application and how you define support and maintenance. Some staff will handle things internally and others will be responsible for the cloud applications.
What was our ROI?
I would say AWS is balanced. Cloud solutions are not cheap, and the ROI could vary widely according to your usage.
What's my experience with pricing, setup cost, and licensing?
The cost depends on the usage and applications. If you're hosting thousands of applications, you'll be paying tens of thousands of dollars. In addition to usage fees, you have to factor in the costs of development teams and the staff you need to support the applications. These are the three costs you need to kind of calculate to decide on the budget.
What other advice do I have?
I would rate AWS 7.5 out of 10. There are a lot of options in this space, and Microsoft is also good. We are evaluating the data on each. We would rate Azure close to eight, so they're both great solutions.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Director Of Sales Marketing at a energy/utilities company with 10,001+ employees
Many merits regarding stability, scalability, and availability
Pros and Cons
- "Amazon AWS has many merits, in terms of scalability, stability, and availability. I have loved using this tool."
- "Amazon AWS could be improved with cheaper licensing costs."
What is our primary use case?
My primary use case of AWS is cloud computing. I have been using the EKS, EFS, S3, and Lambda. I have a lot of experience with the Kubernetes cluster service, as well as AWS, Azure, and GCP.
This solution is cloud-based.
What is most valuable?
Amazon AWS has many merits, in terms of scalability, stability, and availability. I have loved using this tool.
What needs improvement?
Amazon AWS could be improved with cheaper licensing costs.
For how long have I used the solution?
I have been using Amazon AWS for more than four years.
What do I think about the stability of the solution?
This solution is stable.
What do I think about the scalability of the solution?
This solution is scalable.
In my organization, there are approximately 500 to 1,000 users of Amazon AWS.
How are customer service and support?
Amazon's technical support is excellent. I am very satisfied with their support.
How was the initial setup?
The initial setup was very simple. I have been using Terraform as an infrastructure as code tool, and with Terraform, it's very simple. Within one day, I can provision the AWS Infrastructure as a Service tool and install our platform based on the cloud and data analytics.
What's my experience with pricing, setup cost, and licensing?
From a cost perspective, Amazon AWS is excellent. You need to pay for a license to use AWS, and the license could be cheaper, but in each of the cases and instances I've used AWS, there has been a good chance to save money.
What other advice do I have?
I rate Amazon AWS a ten out of ten. I usually recommend AWS because I have loved using this tool. Most of the time, I recommend it as a real-time information and patching service with Lambda.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Devops at a computer software company with 5,001-10,000 employees
Easy deployment and integration with good pricing
Pros and Cons
- "Easy to deploy through the channel model for serverless architecture and easy to integrate through the organization model."
- "Some services which were easy to use through shortcuts are now more complicated to use."
What is our primary use case?
I've used it to create some internal projects for my organization, particularly for designing the infrastructure of those projects.
What is most valuable?
One feature I find most valuable is the easy deployment by using the channel model for serverless architecture. Another feature I find valuable is the versatility of the service S3 because it allows you to give permissions to describe the users from their own accounts, from external users, or external accounts.
What needs improvement?
On the console, they used to have some shortcuts making this solution easier to work with, but now we have been dealing with so many problems on the console, and some of the options are not very useful in my perspective, so they should bring back those options that make things easier to run some of the services.
Most of the time the options are pre-selected, or you have to go with the default settings, but from my perspective, there are some services which are now more complicated to use than before.
An additional feature I'd like to see in the future is more integration with public repositories, though some use their own repositories for security purposes, but I think it'll be easier to deploy services through public repositories.
For how long have I used the solution?
I've been using this solution for almost four years now.
What do I think about the stability of the solution?
This solution is stable. I've been using it for a long time and have only seen an outage in one of the regions. It's a good solution.
What do I think about the scalability of the solution?
The scalability of this solution is good.
How are customer service and support?
The technical support of AWS is very good. When I need something, they reach out to me fast.
How was the initial setup?
The initial setup was straightforward. The complexity of the setup will depend on the number of services e.g. it's something that involves a lot of services, it could get complex, but for a complex setup, you could use things like transformation or Terraform because they will enable you to use infrastructure as a code to make it easier. There's a lot of things to configure.
What's my experience with pricing, setup cost, and licensing?
Licensing of this solution is paid on a yearly basis.
Which other solutions did I evaluate?
I evaluated Microsoft Azure.
What other advice do I have?
This was deployed on the cloud. I don't remember which version because I didn't deploy it. I was not the person running the project of implementing AWS, but I know the client used it, but I don't know which version.
It's not so difficult to use because there's a lot of tutorials.
I'm not completely sure about the number of AWS users in our organization. We have a partnership with them so we have some accounts, but we don't completely have our load on AWS. We are mostly on Azure. Our main server is on Azure. On AWS, we mostly have some internal projects and services, but most of the main load is on Azure.
We have a small workload on AWS. Sometimes we use it to deploy some of our best projects. We use it on some internal projects. It's a random thing so it could be 1,000 users or 50 users. I'll say approximately 200 to 500 users.
We don't require too many people for deploying this solution because our projects are proof of concepts. Up to ten people from different departments would be needed for deployment if it's a business requirement e.g. people from Approvals and Projects, etc.
As for increasing AWS usage, the organization sometimes thinks of moving some of the load to AWS because of good pricing, because currently, our main streams are on Azure, but it's not a sure thing.
I'm unsure if there's any additional cost aside from the need to pay the license annually because I don't directly manage it.
My advice to organizations looking into implementing AWS, especially if they're going to use it on a big scale, is to take advantage of AWS' organization model to make integration with their policies easier. It will also make administration easier for the different accounts, departments, and structure of the organizations thinking of moving to AWS.
I would rate this solution a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Researcher at a computer software company with 10,001+ employees
Stable, scalable, and reduces overhead costs
Pros and Cons
- "Cost-effective and tolerant."
- "Setup is somewhat complex."
What is our primary use case?
My primary use case was as a place to migrate legacy systems.
How has it helped my organization?
AWS has reduced our costs and maintenance requirements. It also allows us to control our load in peak times and automatically increases or decreases your capacity as required.
What is most valuable?
The features I have found most valuable are S3 buckets and Lambda services.
What needs improvement?
An area for improvement would be API creation - a lot of tools are provided, but there can be issues with integrating them. There is also a cost underlay, in that at the end of the day, some costs are not in the picture, so AWS needs to improve its costing toolset.
For how long have I used the solution?
I have been using this solution for two years.
What do I think about the stability of the solution?
The stability of AWS has improved over time and can now be well managed.
What do I think about the scalability of the solution?
This solution is scalable to any limit.
Which solution did I use previously and why did I switch?
I previously used Rackspace Openstack but switched because it required more manpower than AWS, and AWS is more cost-effective and tolerant.
How was the initial setup?
The setup was somewhat complex. It was done in three phases over a year.
What was our ROI?
This solution reduced our overhead cost by 30-40%.
What's my experience with pricing, setup cost, and licensing?
Technical support is expensive to use.
Which other solutions did I evaluate?
I evaluated Oracle Cloud, but it was more complex to use and provided a smaller toolset than AWS.
What other advice do I have?
This solution is one of the top tools available for legacy migration. I would rate this solution as eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros
sharing their opinions.
Updated: April 2025
Popular Comparisons
Microsoft Azure
Red Hat OpenShift
Oracle Cloud Infrastructure (OCI)
Akamai Connected Cloud (Linode)
Google Cloud
VMware Tanzu Platform
SAP Cloud Platform
Salesforce Platform
Pivotal Cloud Foundry
Alibaba Cloud
Google Firebase
IBM Public Cloud
Nutanix Cloud Clusters (NC2)
SAP S4HANA on AWS
Heroku
Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Gartner's Magic Quadrant for IaaS maintains Amazon Web Service at the top of the Leaders quadrant. Do you agree?
- PaaS solutions: Areas for improvement?
- Rackspace, Dimension Data, and others that were in last year's Challenger quadrant became Niche Players: Agree/ Disagree
- Does anybody have experience negotiating the terms and conditions with AWS?
- Which would you prefer - Amazon AWS or IBM Public Cloud?
- Do you have an Amazon AWS certification, and do you think it is important to earn one?
- Would you recommend Amazon AWS to cloud computing beginners?
- Which Amazon AWS features and services do you use the most often and why?
- How does Amazon compare to alternative cloud solutions?
- What are some smart ways to streamline AWS data transfer costs?