Amazon AWS Reviews

We use this solution to deploy our products.

Within our company, there are at least five people using this solution. Usually, they are technical people — some software developers and a couple of infrastructure managers.

Whether we decide to increase our usage with this solution depends on our business development.

It allows us to deploy a production environment using Oracle Database, an API integrator, or by using our development tools. 

It's easy to manage. We can use a wide range of technologies with AWS.

It's very easy to configure and to use the platform, but we would like to be notified about our consumption. The consumption is a critical point for us because we are not always using the platform, but sometimes we receive high charges — high amounts of money for services that we didn't even use during that month, for instance.

I would like to receive some alerts when my consumption is getting out of the normal range.

I have been using Amazon AWS for roughly two years.

It's pretty stable. We haven't had any problems with the platform. Overall, I think it's quite optimized.

Scalability-wise, haven't had any issues. We work with small to medium-sized solutions so we haven't really needed to test the limits.

We haven't really had to contact technical support. The documentation is very complete and easy to understand. 

We tried using a Google cloud platform, but we had some configuration problems with some programs like WordPress. 

The initial setup is very straightforward. I wasn't involved in the deployment, but I believe it took less than four hours.

The price could be lower. Currently, we spend between $300 to $1,000 dollars a month to use this solution. We try to avoid using a license if we can.

I would recommend AWS to other interested companies. It's a very stable platform. It's easy to use and you don't have to be an expert to deploy your first project. Obviously, you'll need to make use of some advanced features, but in that case, support is always available. 

On a scale from one to ten, I would give this solution a rating of eight. 

Public Cloud

Accelerates innovation through fast experimentation cycles in an agile, flexible, and scalable platform.

Enables fast prototyping, simulation, and rapid deployment of infrastructure configurations. Has low risk exploration of new architectural paradigms and technologies (FaaS, Containers, IoT, and Machine Learning) and is easy to integrate with current solutions.

Considering the rate of innovation of AWS and the vast range of services offered (over 15+ categories, 50+ services in 2017) the learning path of customers on the platform is something that can always be improved. Usability through simplification of the interface for the use cases chosen by the customer can be a possible improvement.

The current interface offers several options to select services, solutions, or learning paths. However, the ability to simplify the interface to focus on customer use cases could have an impact on productivity and ease of use.

This is a challenge that I’ve seen all cloud vendor share: Usability and different user experience on their platform is difficult when the span of services is so vast. However, some design thinking “persona” kind of approach could help offer alternative perspectives.

• Since 2012, in prototypes and proof of concepts
• Since 2015, in production applications, advise, and support to some clients.

I’ve never experiences issues with stability related to the AWS infrastructure. The services are very resilient and there are constant reporting and monitoring tools available, a open status dashboard, and a personal health dashboard to receive news on any issues being investigated or sorted out. Even if there have been outages reported in AWS history https://en.wikipedia.org/wiki/... their technical response capabilities have proven outstanding.

I’ve never experience issues with scalability. AWS services offer very flexible set of tools to architect solutions that give the best performance and economic advantages. Combined solutions using elastic computing capabilities, containers, APIs, and even more innovative server-less capabilities (FaaS) can be leveraged to tackle the most challenging use cases.

I previously favored RackSpace and Digital Ocean for simplicity and focus for certain use cases (development prototypes, proof-of-concepts, etc.). I prefer to concentrate investment and training on the same platform when solutions scale and require more complex setups. Leveraging the learning curve on the service offering is increasingly specialized.

The setup is easy and greatly supported by the learning paths offered through the platform. Expertise is required to take full advantage of AWS tools and continuous innovations.

Some customers can become overwhelmed by the range of services, so training and assistance from specialized third-parties is strongly recommended. Even experimented managed service providers can complement internal capabilities and help in the training of internal teams.

One of the advantages of AWS is their high rate of innovation. However, in order to leverage this, internal or external expertise is required. A good partnership is recommended.

On demand, pay-as-you-go pricing is powerful to optimize expenses, but it’s important to keep a technical cost controlling function aware of usage and scale patterns to choose the best pricing mix.

Massive migration to cloud without analyzing the right service for the right usage can lead to higher cost than expected. It is important to get the right advice to match each use case needed to the optimum cloud economics.

Even if a lot of decisions to go to the cloud are based in the promise of lower costs, the true power of cloud services is their flexibility, rate of innovation, and avoiding vendor lock-in if architected consciously.

Even if a lift and shift approach with short schedules can lead to mistakes in choosing services and paying more than optimum, the speed in which you can correct the mistake is not comparable to any other infrastructure option.

This is forcing even the traditional hardware vendors to reinvent their business models and develop financial offerings that include operating expense based financing (pay-as-you-grow) or services based agreements (pay-as-you-go) to make their private cloud offerings competitive.

The other aspect to consider is the managed service required to get the most of this platform. Don’t underestimate the quality of the advice and support required. But at the same time, consider your core business management time released by adopting a platform instead of managing the components internally.

The internal expertise should evolve to understand how to use it best for the business outcomes pursued instead of the technicalities of how to make it. That’s where the right partnerships can be leveraged.

We evaluated Azure, RackSpace, Google Cloud, SoftLayer, DigitalOcean, and Linode.

Test drive it with prototype applications, reproduce development and testing environments, and standardize your stacks to be able to move them easily, if needed. The deeper that the infrastructure-as-code approach is part of your culture, the easier it will be to leverage hybrid opportunities and gain agility.

This solution has been consistently in the top of the IaaS market for the last 10 years.

The features which are most valuable are EC2, S3, and the networking functionality. EC2 allows me to provision new servers in minutes. S3 allows me infinite, redundant, easily accessible storage. The networking functionality (VPC, Security Groups, subnets, etc) allow me to create robust networks that make sense. Availability Zones allow me to design systems that are resistant to failure.

One example is our devops people can provision new products and systems almost immediately. They have set up an instance of GitHub Enterprise which has become our "source of truth." We have created proofs-of-concept in hours to days to test and evaluate new products across the enterprise. We have been able to leverage the agility of AWS to work faster and, in some cases, "fail fast" so we can get on to the next thing, which works.

Probably customer education and awareness, especially in the Cyber Security area. Many people are mistrustful of public cloud offerings or misunderstand how things work. We'd like to use AWS a lot more for various workloads, but gaining approval to do the things we want to do is currently our biggest roadblock. This isn't necessarily AWS's fault, but hopefully they have the capacity to gain acceptance in the broader Cyber Security community.

I have been using the product for two years.

Our main issues are learning how to deploy the most efficiently. We use Puppet and Jenkins to deploy. Other issues are employee awareness and training (which instance type to use, where to put things, which keys or security groups to use, etc).

No more than expected number of stability issues. We have the occasional EBS volume go down but we expect that.

None at all. AWS is infinitely scalable. Though on one occasion, our preferred instance type was not available in the Availability Zone we wanted it in.

Customer Service: AWS's customer service is ridiculously good. Back when I was admin of an account that only used a few hundred dollars a month, I got top-notch support from my account manager. He set up a couple of conference calls with Solution Architects with no hesitation. Now I preside over an account with significantly more usage, and the customer service remains great.Technical Support: AWS has some really smart people who can analyse my technical questions and give me a cogent, useful answer in short order. Their tech support is top-notch.

We have also use Terremark e-Cloud, but their cost and lack of features turned us off. I don't believe it was an either-or situation, though. We used both but are moving out of e-Cloud and are staying in AWS.

I was not with my current agency during the initial set-up phase.

The agency used a vendor team. I'm with that vendor team and I think we're pretty good, but I'm biased.

We don't calculate ROI, but AWS definitely helps us fulfull the agency's mission, which is how we measure things here.

I personally have evaluated Azure and Google Cloud Platform. Neither seemed as robust or mature as AWS.

Jump right in and make liberal use of AWS' technical support. Even now, I see people hesitating to ask and trying to figure it out for themselves. AWS is always ready to help. It's both complicated and useful enough that it's very easy to build things in a suboptimal way if you don't think things through and follow their guidance. So get all your hands-on staff to take the training they offer and don't be shy about asking for help. The training is big.

We use it to run workload applications, ERP systems, LISAP systems, etc. Everything is on the cloud, including our technical infrastructure for computing, storage, and networking. You can deploy applications like SAP or Oracle or run any website with applications on it.

You can build and release applications quickly with AWS instead of waiting for months to get the necessary hardware. That's the real benefit. The time-to-market for developing applications is much shorter. 

The most valuable thing about AWS is its ease of use and agility. You can quickly deploy it, and there are no upfront costs.

One problem is that the AWS public cloud doesn't have shared storage capabilities. The second thing is the cloud performance versus on-prem. I also have one suggestion that's solution-based. For example, if I want to deploy a medical solution, I would like to have a medical template, so I don't have to set up the infrastructure from scratch. They should provide everything in a pre-defined custom solution blueprint. 

We've been using AWS for four years.

AWS is generally reliable, but we've seen a lot of issues lately, so I would say they have some room for improvement. For example, if the user doesn't configure something correctly, it might fail. Even if AWS is reliable, that doesn't guarantee that all the users will be reliable. They need to make the design foolproof. 

AWS is a cloud provider, so the scalability is almost infinite. Our company currently has around 500 users on AWS. 

We have enterprise support, so they have different levels. If you have enterprise support, they have obligations they must meet. In our experience, Amazon support is above average. Sometimes we get good support. Sometimes we don't. I would rate it six out of 10. 

The AWS initial setup is seamless and straightforward. We set it up ourselves, and we have a 10-person team to manage and maintain the solution. Including design and planning, it took us about three months. 

I rate AWS seven out of 10. My advice is to watch out for the cost. A public cloud means you can use any resource, and there is no upfront cost. That means someone can use an expensive computing solution that might cost them tons of money. No one is holding your hand, so you can use it, but you need to be conscious of the cost before using the solution.

Public Cloud

Amazon Web Services (AWS)

We are primarily using the solution for evaluation purposes.

The functionality and the UI are both very straightforward.

The initial setup is straightforward.

The stability is good.

Technical support is quick to assist.

The pricing could be better. It's a bit expensive. 

The availability could be better.

I've been using the solution for about two years.

I haven't had any issues that would bring stability into question. there are no bugs or glitches. It doesn't crash or freeze. 

I can't speak to the scaling. It's not something I've attempted. I just use it myself.

I can't say that there are plans to increase usage right now. 

Technical support has been great. They are helpful and responsive. They are very fast.

This is my first cloud product. I did not use something previously.

The initial implementation process is not difficult or complex. It's straightforward. It's basically having the computing power, the storage, S3, and the database.

The implementation was handled in-house. We did not use an external integrator, reseller, or consultant.

It's a costly product.

We pay a monthly licensing fee. It's below $100 a month.

I haven't done any evaluations or comparisons with other products.

We are customers.

We are using the latest version of the solution.

I'd rate the solution at an eight out of ten.

Public Cloud

Amazon Web Services (AWS)

We use Amazon AWS as a data platform.

The features that I have found most valuable are its cloud storage and compute services.

Amazon AWS could improve on its data warehousing appliance.

Its only cons are on the data warehouse side. AWS' data warehouse Redshift is not as good as it should be.

In terms of what should be in the next release, I would say nothing much other than that AWS has a lot of services doing similar work. If they could consolidate and make sure that the services are defined appropriately, that would be an improvement. Currently, there is a duplicacy of work.

I'm working with AWS for almost five years.

The stability is very good.

You do not need tons of people for maintenance, because a lot of automation will be brought in by AWS, and you can have one or two people to manage the platform.

Amazon AWS' scalability is very good.

There are a lot of features that require scaling - the scale up and scale down aspects of load balancer, Spot Instances, On-Demand Instances, and all those things. You can configure your limits, and based on that, the computer infrastructure can be scaled up.

There are tons of users using it. Whatever the project I work on, there are almost 200 users using it.

There are lot of data engineers, data scientists, and business users using it.

Customer and technical support are very good.

The initial setup is straightforward.

The licensing costs are all similar. All charges are similar in nature, such as storage cost, compute cost, VM cost, or VP costs, and all those things. Two advantages on this point here are whether you take Spot Instances or if you reserve for long term usage, then you'll get a lot of benefit.

If you want to use any third party services you have to pay from the Marketplace, but the other things are all pay-as-you-go kind of a model.

Amazon has a great customer base and lot of success stories. That is one advantage that AWS has, whereas the others are catching up. Recently they have more case studies, but for overall breadth of the industry and breadth of the customer experiences, AWS has more customers. AWS has more services than the other competitors.

My advice to anyone thinking about using Amazon AWS is that they need to set up the foundation well, and they need to choose the right partner to do the implementation. The more experience the partner has, the better the implementation will be.

On a scale of one to ten, I would give Amazon AWS an eight.

Public Cloud

Amazon Web Services (AWS)

We usually use Amazon AWS to implement data lake solutions. We extract data from an AWS project that we implement, or we extract data from databases and centralize them with AWS components in AWS services. So, we create an infrastructure for our clients to consume their data. I like the components we use, like Amazon DMS or Database Migration Services, F3, and Amazon Athena. I think that these are the main components or the main services that we use.

I like that the products are specific and objective. We can resolve a problem using a simple configuration. It's so easy to implement a solution and solve a problem using AWS solutions. AWS has a lot of specific solutions for different use cases. I think that this is the most important thing that made us consider using AWS.

It would be better if there was a way to see which components were still on. We have some situations where I forget that some components are turned on. We forget some components are on, and we only see that these components are on when we see the bill at the end of the month.

It would also be better if AWS had specialized firewalls or integrations with leading products. For example, a specialized firewall with content filtering. We were looking for some firewall tools, and we saw that AWS doesn't have any specialized firewall tools in its services portfolio. So, we are looking for other tools like FortKnox, Forcepoint, and Check Point because we didn't find the solutions in AWS services.

I have been using Amazon AWS for about three years.

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

Public Cloud

Amazon Web Services (AWS)

We are customers of Amazon AWS. 

This solution is very easy to use and it has a professional interface. It's easy to access and is secure, two important features. 

The cost of the solution could be improved, it's quite expensive. I find the networking to be overly complex. 

I've been using this solution for four years. 

Amazon AWS is a stable product.

The solution is scalable. 

The initial setup was complex because of the networking setup we needed to create. This could have been a problem with the networking site. 

We currently use Azure as well. AWS offers a very good platform mask and is easy to use. Azure is good for creating virtual machines and creating VLANs is very easy with the Azure site.

I rate this solution an eight out of 10. 

Public Cloud

Amazon Web Services (AWS)