Amazon AWS Reviews

This solution has many use cases. Amazon AWS offers a lot of services, all of which are useful. How useful this solution will be for you depends on how it fits your business. 

Amazon AWS is easy to use and in the past two years, I've never had any issues with scalability or stability. 

This solution could be improved by a better licensing model, especially for third-party software. Amazon AWS could also potentially be improved by more free storage, but I think that it's okay when compared to competitors' products. 

I have been using Amazon AWS for more than two or three years. 

This solution is stable. I haven't had any problems with stability in the past two years. 

This solution is cloud-based, so it's scalable. It is elastic, so as soon as you want to increase storage, you do so without any issues. There are about four thousand to five thousand people using AWS in my organization. 

I have contacted Amazon's technical support and it was quite an easy process. You will have a solution within 24 hours. 

I didn't use another fast cloud solution before Amazon AWS. 

The initial setup is easy and you don't really need to install anything. If you understand cloud solutions, you can easily do it yourself. 

I implemented myself, with an in-house team. 

We need to pay for everything. If someone is a personal user, they get one year free. But if you are using this as a professional or enterprise solution, then your company has to pay. The license pricing is comparable to that of competitors'. 

I rate Amazon AWS a nine out of ten, primarily because I have a background in Java. Someone else with more experience in Microsoft technologies would probably prefer Azure. I recommend AWS to anyone considering implementing it because it's easy to use. 

I am using it for enterprise warehousing. I am using it for web development, data warehousing, and also for building apps.

I am using its latest version. In terms of deployment, it is a platform as a service.

Macie is great. It is a service that makes recommendations on a data layer for cybersecurity. It is a great service.

Its elasticity is good, and I haven't come across any problems with it. So far, everything has been good.

One thing that Azure offers that I think is good is Migrate appliance. So, Azure has a migrate appliance that allows you to run against workloads to determine the cost, preparedness, and scalability. I haven't found a similar feature in AWS. That kind of service would be great on AWS too if you could point it to the data center.

I have been using this solution for well over five years.

I have not had any performance issues.

It's very easy to scale. Its elasticity is good. If you want to scale up or down, you can. You can scale out. There is no problem at all. That's one of the features that I like about it.

We have less than 50 people who are using this solution.

I've not used their tech support yet.

We didn't use a different solution previously. They're the first.

You need to know what you're doing. I know they're trying to make it easy. Some things are easy. Some things you have to know what you're doing.

It seems to be reasonable. It's the first one that I've used as a cloud platform, so they've set the benchmark for me, and now, I'm comparing everything else to them.

I would advise others to just plan out what they are looking for in terms of use cases. 

I would rate Amazon AWS an eight out of 10.

We use it to host our e-learning platform.

AWS is a platform, wherein they give you a virtual instance of a server. So there is no version per se. They just give you a virtual server. The other software we use is free. We use it for conducting our exams and everything. We use a free, open source software, which is not a commercial software.

Remember, this is a plain vanilla platform. So we don't have to do any actual investment in servers and other things. That is the general advantage of cloud that everybody gets. You don't have to pay a lot of money. And at any point, if you feel you don't want to use it, you stop. It is as simple as that.

The features that I have found most valuable are their compute and their Relational Database Service.

The features that should be improved are that there should be better clarity on their invoicing. There are so many things they charge for - high line items in the invoice. I think there should be more clarity and more ease of use with their billing.

I'd like to see better ease of use with the billing console and a clear dashboard to understand the usage.

I have been using Amazon AWS for almost three years. We are continually using it.

Amazon AWS is very, very stable.

No maintenance is required.

Scalability is unlimited. From one to 10, it is 10.

We use it, but our training participants access it. A lot of people access it. In a year, at different points in time, 200 people might be using it.

I don't think we will be expanding usage because we purchased a little more than what we needed. We don't need to spend any money now. We only pay our monthly charges.

Technical support is good. If you raise a ticket, they're very good. Even with billing, if you have some issues they take care of it. If you are overbilled or you're not using it and then you turn one thing by mistake, and all of a sudden the bill has increased - they'll take care of it.

Previously, we were using general hosting, they even call it shared hosting. But it was not scalable and it was not fast.

The initial setup is all easy. It's very easy.

Our deployment took just a few clicks. You are talking seconds.

I had our technical team do it. But you need a technical person. It's not that anybody can do it or a person like me can do it. You need to have a technical person doing it.

We have seen a return of investment with Amazon AWS.

We are just a customer. We just pay monthly for the subscription cost. I mean, hardly $50. We are a very small company. 

My advice to anyone considering Amazon AWS is that they should plan properly for their spending and they should have good control over their technology team. Otherwise, if the technology team doesn't know enough and they keep on creating more services, you'll be surprised with the invoice. Technology and finance should work very, very closely in the cloud.

On a scale of one to 10, I give Amazon AWS a 10. It's a really good product.

We use Amazon AWS for provisioning and the majority of our deployments.

We support and provide services for our clients who lean towards using AWS.

Amazon AWS is easy to use.

It scales well and is flexible.

When compared to Google Cloud Platform or Microsoft Azure, it has almost all of the features.

As a result of the competency, I believe that most people are now leaning toward Azure rather than AWS. That is also according to Gartner's forecast, more people are turning to Microsoft Azure.

The price could be better.

We have been using Amazon AWS for more than three years.

We are always using the latest version.

Amazon AWS is a stable solution.

It is a scalable product.

When the number of users increases, the bandwidth automatically increases, and when the number of users decreases, the bandwidth decreases.

We have a large organization with over 3,500 users, and more than 60 customers.

Our organization has an AWS center of excellence that increases our usage.

I personally have not contacted technical support. 

We contact our own center of excellence team, who would then contact the AWS support team for any information we required. That is the order in which we must proceed. It's the hierarchy that we must adhere to.

I am also, familiar with Splunk.

The initial setup is straightforward.

The installation is done through the AWS Cloud and is so simple that it only took me 15 minutes to create instances, possibly even less than 10 minutes.

We have 200 engineers who are responsible for both the development tasks and the maintenance.

I was able to complete the installation myself.

When compared to GCP, Google, or Azure, the price could be lower.

As a company and a platinum sponsor, we know exactly where management will make a decision on getting the best price for us.

A monthly fee is a good option for a startup company or an individual, and it is paid yearly for larger organizations.

I would recommend this solution to others because I am not familiar with Azure and only have experience with AWS.

We don't have any issues with this product. I would rate Amazon AWS a ten out of ten.

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.

I was using Amazon AWS in the medical market in my previous employment.

Amazon is a really good solution with high performance. They offer more connectors than some of their competitors, such as Microsoft Azure.

Amazon AWS could improve by being more secure and adding more features.

I have been using Amazon AWS for approximately six years.

Amazon AWS in my experience has been more stable than Microsoft Azure.

The solution is scalable.

We have approximately 50 customers that are using the solution.

We have moved from Amazon AWS to Microsoft Azure. I have found that both solutions perform very well. The main reason we switched was to allow us to manage where the data was to be stored. We wanted a data storage solution in France which most of our customers were requesting. Two years ago, Amazon did not have any solution to provide any storage in France. 

The level of difficulty for the installation of Amazon AWS is similar to Microsoft Azure. They are very difficult.

We have a five-person team of DevOps and architects that do the implementation and maintenance of the solution.

If I was going to compare the cost of Amazon AWS to Microsoft Azure, they are approximately the same.

I would recommend this solution to others.

I rate Amazon AWS an eight out of ten.

We have migrated all of our on-premise production environments to the Amazon AWS cloud and we use many AWS services.

The solution could improve by being more secure.

I have been using Amazon AWS for approximately six months.

Amazon AWS has proven itself as the market leader in the cloud solution environment and is highly stable.

The solution is scalable.

All of our production environment is hosted on Amazon AWS and we have approximately 12,000 users that use it.

We have enterprise-level support that is very good from the AWS team.

We use other solutions, such as Microsoft Azure for UID and Google Cloud services for DCP.

The initial setup is not difficult and it did not take us more than one day.

We have a managed service provider that helped us with the implementation of the solution.

We have a 60 person team that manages our data operations and infrastructure. The team consists of many levels, such as system engineers, architects, and managers.

We have a monthly subscription for Amazon AWS.

I would recommend this solution to others.

I rate Amazon AWS an eight out of ten.

My primary use case is to set up an end-to-end application to deliver a business case involving data ingestion, processing, transformation, and checking, followed by outputs to other functions and processes in AWS and also to external systems.

We are using Step Functions as a core automation tool and it offers great power through its simplicity. It is quite easy to use, although there is a learning curve when using the Step Function scripts. Once mastered, after a week or so, the flows can be built quickly and effectively, allowing us to link a custom business process to multiple other AWS service automatically. 

That done, most business cases can be delivered easily and quickly, all in a serverless and cost-effective way. 

AWS has improved my organization by:

- saving us time, cost, and difficulty by allowing us to use serverless services

- enabling us to assemble complex applications with the minimum of boilerplate and plumbing

- allowing us to pay-as-we-go, so we can rapidly prototype, test, and then deploy to a production application setup

We can run advanced demos with our own data very quickly, showing potential clients the value of our services when we assemble apps for them.

We can show customers clear cost benefits and clearly effective solutions when assembling AWS services together. 

The security has great IAM, roles, and carefully partitioned permissions that allow us to fine-tune control across our applications. External intrusion attempts will never get past application boundaries, which increases trust.

The composition of apps has everything wrapped according to function and applications. We can assemble services as we go. This speeds delivery times by orders of magnitude.

The price forecasting and billing dashboard by service, with billing budgets and alerts, have helped us shut down resources that were accruing costs that we no longer needed, saving us money.

The service's power lies in its simplicity. It is great in that respect. 

The UI is constantly being improved and the billing dashboard has been improved.

Previously, we asked for more end-to-end workshops, examples, and tutorials and these have been added and improved. 

Recently, AWS has been adding improvements across services, documentation, tutorials and we have now got workshops with real-world scenarios which are tremendously useful It makes me a very happy user. 

AWS and the cloud is a space for constant learning and AWS has increased their output in that respect. 

I have been using AWS since 2014.

The solution is very stable. The only errors I encountered were my own. Some services took a few minutes to refresh and propagate across my environments, and once these had propagated, the solutions were rock solid.

The scalability is excellent. At no point have I hit scalability limits with AWS services and features. 

Customer service and tech support were excellent a few years ago when I needed them.

My general process is to explore and check options and run from a tutorial or AWS workshop. If this doesn't get me results, I then do a web search, and I generally find either further AWS docs or a specific example I can use to solve my issue. Within the last few years, my colleagues and I have been able to deliver as required. 

We did previously use a different solution when building AWS Lambda cloud functions. I could compare them directly with Azure Functions and Google Cloud and have found that the AWS Lambda solution is simpler, clearer, deploys quicker, and is generally much more simple and effective to use.

In terms of documentation, AWS is the clear leader. Their end-to-end examples and workshops are much more effective.

AWS services in many cases are deployed to AWS after being validated in Amazon.com's operations. This is evident in the ease-of-use and simplicity of many of the service features, and also in the excellent options offered for more complex services like AWS Forecast, where, for example, a checkbox and drop-down allows the user to add holidays for the country they work in when doing forecasts.

AWS has a stronger focus on business solutions than either GCP or Azure, and in many of the solutions, I have used. This is why in many cases I have switched from using other clouds, to AWS. 

The setup in AWS is a whole service in and of itself. To set up AWS applications, AWS offers a full service, CloudFormation, with some added features that allow us to automate the deployment of the full solution stack.

This makes setup complex, in that one must modify the CloudFormation template one requires and validate it. An external resource was required to check the templates. 

Once this is done, the full solution stacks are automatically deployed. 

I handled the initial setup in-house and by myself.

A recently deployed Step Function automation fulfilled all the needs of a workflow automation engine while remaining below the free operation per month, so we were able to deliver a fully automated application approval process without paying for any workflow automation engine license fees or any server hardware or infrastructure costs.

I would advise others to work from an architecture overview. 

Be aware of the very powerful schema-less data services in the cloud. They can help remove the need for data warehouses - e.g. multi-TB datasets - can be read, joined, queried and made to output daily reports within minutes, on temporary clusters, and that cost less than USD1000 per month. This is compared to the hundreds of thousands of USD for data warehouse licensing costs, plus the schema design time and ongoing DevOps they require.

Moving to serverless operations in the cloud frees up your people to deliver business services rather than spend days and days on administering data centers and the associated concerns that come with them.

I also looked at Azure and it was deemed less reliable than AWS as AWS has not had as many outages and uptime concerns as Azure has had of late. Azure Function Apps, Data Factory, Managed SQL.

Besides Azure, I looked at GCP and VMs, Cloud Functions, Speech-to-Text transcription, BigTable, and BigQuery.

Empower your in-house people to start building and running their workloads in AWS. 

Let them learn as they go. There are multiple online courses for a few dollars that can assist with specific, individual AWS services, as well as running through the AWS workshops. 

Incentivize AWS certifications. Involve your tech people with business solution prototyping. 

Tag your resources, name them well, and set budget thresholds. Assign people to tune the resources being used. Incentivize communications and publish the AWS services and features being used to deliver your business capabilities.