Amazon AWS Reviews

We are using it for certain business applications.

The scalability is a valuable feature. 

The improvement should be done as per business needs. 

I have been using Amazon AWS for five years. 

It is a stable solution. 

It is a scalable solution. Presently, 3,000 users are using the solution. 

The initial setup is straightforward. 

The pricing is expensive. 

Overall, I would rate the solution a nine out of ten. 

AWS is deployed into a public cloud. We have five lines and everything is autotomized. We are using several AWS solutions, including Containers, Pierre, Stargate, and Lambda. We have several projects in production, but I can't disclose more details because it's confidential. 

AWS is easier to implement than other solutions, and it's more reliable. 

It would be helpful for us if we could easily integrate Oracle RDS with AWS. That would work well with the solutions we have in place.

AWS is stable.

We can quickly add resources with AWS when necessary. Our company currently has 200 users working with AWS.

Amazon support could be better.

Deploying AWS is easy. The amount of time it takes depends on the application. I couldn't give a precise estimate of the number of minutes. We have four engineers to manage and maintain the solution.

We pay about $20,000 per month, and the license is all-inclusive. 

We are compared AWS with Azure and IBM Cloud, but in the end, we decided to work with AWS.

I rate Amazon AWS 10 out of 10. For me, it's perfect. AWS is effortless to configure and has high availability. 

Amazon AWS can be used for storage, networking, and for many of the services they have available, such as databases, new site launches, and quick deployments.

Amazon AWS has improved a lot on security and is very good. Additionally, You can integrate your own security into their AWS platform.

The reporting and analytics monitoring are very good features and we are using them extensively.

I have been using Amazon AWS for approximately seven years.

I have found Amazon AWS to be stable.

Amazon AWS is highly scalable.

We have previously used older servers solutions from Dell, HP, and IBM.

The installation of this solution is straightforward.

The amount of people we need for the deployment depends on the use case and what type of business operations you are running. You can start with one resource based on the requirements and you can add the people as you need them. The majority of the people you will need will be for DevOps and you can scale your team as per your requirements. You can start with one at the beginning stage but you could end up needing a hundred thousand people but this depends on the business growth and many factors.

The pricing model of Amazon AWS is very good because there is an option to pay for what you use only, you do not have to give any money upfront to use it. However, we have some instances where we are on a monthly plan.

When you compare Amazon AWS to Microsoft Azure, the pricing of both is almost the same. There are some instances when one is cheaper than the other in one area but it is difficult to pinpoint which one is cheaper because it depends upon a lot of factors, such as the use case. However, the overall price of both solutions could be reduced.

I have evaluated Microsoft Azure.

A lot of organizations are moving from on-premise solutions to the cloud. There are a lot of case studies already in the marketplace which you can go there and find case study solutions to your business requirements.

I would recommend this solution to others.

I rate Amazon AWS a nine out of ten.

We primarily use the solution to host our control panel for our IoT devices.

The solution has very good documentation.

The initial setup is simple and straightforward.

The solution is scalable.

The stability has been good.

We have found the technical support to be helpful and responsive. 

I cannot recall feeling there were any features missing.

There is a bit of a learning curve. That said, it's likely no different than learning any other cloud.

The pricing could be a bit lower, even though its costs are in the middle of the road.

I've used the solution for about half a year. It hasn't been 12 months yet.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's quite reliable. 

I would imagine the scaling is very good. It's advertised as quite scalable and everything points to that being the case. However, I have not personally attempted to scale. We're still building the application, and therefore we aren't at the point of scaling.

We have three people using the solution currently.

Technical support is very helpful and responsive. They have been good so far. We have no complaints and are quite satisfied with the support we receive.

We did not use a different solution. We chose Amazon due to its good documentation and middle-of-the-road costs.

While I wasn't a part of the initial implementation, it's my understanding that the process is very simple and straightforward. It's not an overly complex process. 

The cost is moderate. It's not overly expensive.

We are just customers and end-users. We don't have a business relationship with Amazon.

I'm not sure which version of the solution we're using. 

I'd recommend the solution. It's a good choice and one we stand behind.

I'd rate the solution at an eight out of ten. We are very satisfied with the product so far. Likely, if the price was lower, we would rate it higher.

We are a product cocktail service company, and we deliver identity-based solutions that customers can subscribe to. The back-end infrastructure is hosted in AWS.

It helps us by saving money. Having a physical server on our premises is, of course, quite expensive as compared to building an EC2 instance in the cloud.

We use AWS in-built services like EC2, ECS, Lambda services, CloudTrail, CloudWatch, etc. AWS is a very big platform that provides a lot of services.

The main reason why we use EC2 is because we are not dependent on maintaining the hardware inside our premises. Also, we have full control over the infrastructure, and we can modify it as per our own requirements.

It is stable and scalable as well.

Installation is quite easy.

Monitoring still needs to be improved.

Better support for Windows Operating Systems would be appreciated. It is good for Linux but needs to improve for Windows.

I've been dealing with Amazon AWS for more than four years now.

We are experiencing 99.9% uptime already, so we have had no issues with stability.

It is scalable. We have configured our Auto Scaling options there, which enables us to install as the requirements increase. It auto scales the server.

Technical support is okay. I will not rate it too high, but I think it might be because it is part of a basic plan. We do not have the enterprise support plan.

You don't require much technical expertise to have an instance, so the initial setup is quite easy.

On a scale from one to ten, I would rate Amazon AWS at nine.

We use Amazon AWS as an IaaS Cloud for our e-commerce sites.

Because of the stability and scalability AWS provides, our team can now focus on how to engage and delight our customers instead of constantly being fixing production issues.

We have not had any problems at all. 

In the 4 years that we have been using  IaaS services from Amazon, we have not had any issues.

It's a great IaaS cloud. They are the leaders. No cloud provider can match Amazon right now.

Other providers are improving year over year, but Amazon is still ahead at least two years.

Working with AWS requieres your organization to invest in training your team to better use and take advantaje of all that AWS has to offer.

We have been using this solution for 4 years.

AWS provides without a doubt the most mature and stable IaaS cloud in the market.

We have thousands of customers who are going to our websites to purchase goods and it takes a matter of minutes to scale the infrastructure both horizontally or vertically.

Great services, assistance and response time from the AWS team

It depends on how complex is the architecture of the solution to be deployed, in our case because Magento is sort of "native" for AWS it has been straightforward.

We implement through a vendor team specialized implementing and managing Magento on AWS

I would rate Amazon AWS a ten out of ten.

We have a financial services application that's a very broad purpose API set. There are rest APIs for executing financial transactions and maintaining financial data. We also have a series of applications built on top of that.

Every aspect of the product is excellent. We have no complaints.

The reporting aspects of the solution are excellent. 

The documentation that is on offer is very good.

The initial setup isn't too complex. A company shouldn't have any problems implementing the solution.

The stability is very, very reliable.

The payment structure is very good.

The scalability is excellent. There aren't really any limitations

The security right now needs improvement. It's not bad, per se. It's just that there's always room for improvement in security.

I'd love to see guarding duties enhanced.

The pricing could be a bit better. It's something that can always be improved upon.

I've been using the solution for years. It's been a while.

The stability is tremendous. There are no bugs or glitches. It doesn't crash or freeze. It's extremely reliable. The performance is excellent.

The scaling is phenomenal. We use a lot of auto-scaling. It's really fantastic. If a company needs to expand, it can do so easily.

In our organization, we have 15 users of the product.

It is very seldom that we have had to contact technical support. That said, when we have, it's been very responsive. We are quite satisfied with the level of service provided. It's been very good overall.

The initial setup is pretty straightforward. It's not too complex. A company that would like to implement it themselves shouldn't have any problems doing so.

The solution is set up as a pay-as-you-go. It's very convenient.

The pricing could always be better, but it's pretty darn good. We're looking into some options for some pricing improvements through some Amazon partners.

There are not any additional costs to the standard licensing fees.

We did look at other clouds, however, ultimately, we chose AWS. We've been extremely happy with it.

We are just a customer and end-user.

I've been an enormous fan of AWS. It does exactly what I need it to do. It would be hard to convince me to use anything else.

I would recommend other potential users to absolutely do it. It cannot be beaten. I'll never run a data center again.

I'd rate the solution nine out of ten. We're very happy with the product overall.

I am an AWS Certified Solution Architect Associate as well as a Certified Cloud Practitioner, and I am currently pursuing the development specialty. I mainly use AWS to develop cloud solutions for clients.

As a Solution Architect Associate with focus on development, my clients typically ask me to help them personalize AWS services as they pertain to the client's business. For example, I will often work with AWS SQS queues, ETL jobs, APIs and storage, and other services offered by AWS in the cloud.

Generally, my work has more to do with development rather than architecture, and other AWS services that I use include EC2, S3, Lambda, API Gateway, Amazon Connect, Alexa, DynamoDB, ECS, and EKS.

My daily activities are essentially focused around implementing AWS services for clients who want to migrate their existing computing infrastructure to the cloud. For example, if a data center is on-premise, our solution is to bring that data center to the cloud. This kind of migration includes moving all the applications that a company uses to the cloud in progressive steps. We also work to enhance their applications with extra code and the advanced features that the AWS cloud offers, like Lambda for instance. 

The clients that I work with — which include large organizations like universities — also use cloud providers other than AWS, including 3Cloud, Google Cloud Platform, and Microsoft Azure. I, however, specialize only in AWS and Azure.

Here is an example of how AWS has helped one of our clients: With Amazon Connect, we can track all activity in the past and in real-time, so we can know how many calls are in progress and if there are any problems. With a student payment system, for example, if a student has a problem because their credit card was rejected, we're able to trigger an SMS notification to somebody so they can contact the student to make a payment with a different form.

The university is thus able to offer a streamlined payment service with automatic fallback options (e.g. receiving payments with a card reader in person) and all of this is automated thanks to AWS Lambda, which lets us handle customized metrics automatically and in real time.

The AWS feature that I most enjoy is Lambda functions. I primarily use serverless components because they allow you to process things without having to compromise on resources like when running EC2 instances or virtual machines. With minimal effort, you can scale up an unlimited number of processes, even concurrently, to process things. I frequently work with web APIs, so I use Lambda a lot in this area.

Recently we had a long conversation about functionality that is missing in Alexa — in Mexico, specifically. Alexa for Business is a service and platform that Americans can use to make a call to an Amazon Echo device or a telephone via the app. But in Mexico, we are not allowed to use that technology. This is a significant disadvantage of AWS for those living in Mexico.

I also think that Amazon Rekognition could be improved. For example, I have used Rekognition to label things like trucks, buses, etc. Then we put a camera in front of a bus, so that we can send notifications if the bus driver overtakes another car on the wrong side of the road. However, it seems that Rekognition's machine learning doesn't yet have the capabilities needed to make this kind of labeling and recognition system work properly. Thus, we've had to resort to alternative solutions.

And in terms of how easy it is to learn, Amazon doesn't have the most friendly educational platform. It is very obtuse, in fact. I have wasted a lot of time and effort studying through the official channels, so now I mostly use Udemy courses instead. They are very practical and much simpler, but I would still prefer to learn from the official educational platform if it were improved.

I have been using AWS for about five years now. 

The stability of AWS is very good. 

I work with AWS Lambda all the time and I never have any problems with scaling. Recently, Lambda launched a new billing system, which is cost per millisecond. Before, we would get cost per hundred milliseconds, as the minimum, and now if we use only 10 milliseconds, then the cost for 10 milliseconds is exactly how much we have to pay. So that's great, because now I can scale my functions with a precise cost calculation.

I currently have several issues with Amazon Connect because we can only obtain two telephone numbers by default. With this scenario, there was a very difficult process to let Amazon know that we are not working for ourselves in our console, and that we offer our services as a third party, in terms of SaaS and IaaS, to our customers.

I'm not directly involved in the creation of accounts, and I just use them once they are created on the company or client's side. But in Amazon Connect, when we needed to add more users, the time response from Amazon was two or three days. We are subscribed to the developer support plan, and I think two or three days is a lot of time.

Either my company or the clients usually have the console already set up when I start work on it, so there's not much in the way of setup that I can comment on.

With the AWS projects that I lead for clients, it's basically just me that works on deployment, implementation, and maintenance.

When it comes to professional certification in AWS, I implore others to study hard before your exams because $300 is a painful waste of money if you fail.

With AWS products, there is a steep learning curve and I think there are so many aspects because it is really an ecosystem. If you are committed to reducing costs, or increasing performance, or optimizing in any manner, you have to know the solution really well.

I think the best way to achieve this is by experience, but if you don't have any experience, studying hard is the next best thing to do.

The two alternatives I've considered are Microsoft Azure and Google Cloud Platform. However, because I am only certified in AWS, I don't know the difference between, for example, Microsoft functions in Azure and AWS Lambda functions in a commercial sense.

In a technical sense, though, AWS seems to be more comprehensive in the programming languages that it supports. For example, with AWS Lambda functions I can program in Python, PHP, Go, and many others, but with functions in Azure, you are limited to fewer options.

To our client, it's neither here nor there, because they're typically not involved in the actual development, but if you use Azure architecture then you're going to be limited to the programming languages that Microsoft supports.

If you want to take advantage of all the benefits that AWS offers, then it's best to take the time to learn how the entire ecosystem, and each part of it, works. 

I would rate Amazon AWS a nine out of ten.