Amazon AWS Reviews

The solution is a critical part of modern retail architecture. There are as many as 3,000 different use cases, and each client uses it differently.

This video explains the whole microservice architecture of which AWS is a key player: (3) Microservice POS Design - YouTube Enjoy

It's been a while since I've looked at the AWS model, however, just at a high level, of course, being able to build a microservice architecture, that's the heart of modern retail. That's where they have to go. COVID has driven everybody to realize that's what you got to do. That's one of the key components of AWS. The cloud piece is a nice supporting concept and it's necessary to make the microservices features work and make the whole architecture really agile. That's a critical component of it as well.

Of course, being able to figure out how you want to coordinate services - that whole service management piece - is critical. You could have thousands of services and I'm pretty sure you'd just be overwhelmed due to the fact that you've lost track of everything and you're back to the way things were when you had the big monolithic models.

The stability is excellent.

The solution has good speed. It's very fast.

The execution is fantastic.

I haven't delved down deep enough into the solution in order to come up with an answer for what may be lacking.

The only real downside to AWS is they can easily shut you down if they want to.

Clients ask us "Well, what happens if I go and put this on AWS and they don't like me for some screwy reason and all of a sudden they shut me down, they've killed my entire company?"

While AWS often is at the top of my list to recommend to people, I always have to tell them, "Hey, you got to be careful because if they don't like you, they can shut you down in a heartbeat. And they can kill an entire company by doing that."

I've had a good understanding of how AWS works for a while. It's likely been about three or four years.

The stability is excellent. It doesn't crash or freeze. There aren't bugs or glitches. It's reliable.

The solution is extremely scalable. You can be a small company or a multi-billion dollar company and it will work for you. It's number one on my list of recommendations due to its scalability.

I've never reached out to technical support in the past. I can't speak to how knowledgeable or responsive they are.

I didn't actually set up an operating AWS model on my computer. Therefore, it would be difficult to discuss the initial setup.

I tell clients to use it, however, I don't go into building one on my own. I don't have a need for it here, and I don't have applications to run on it. In my case, it's more an architectural world rather than a physical world.

I work on the technology side, I don't work on the financial side. Therefore, I really don't have any clue how much it costs.

I'm just a consultant. I don't have a partnership with AWS or any other company.

AWS is a key part of the whole microservice cloud computing.

I would recommend the solution to other organizations.

However, if I'm a multi-billion dollar retailer and I need to depend on something, how do I trust a company that can shut me down on a whim? That's a real problem. That moves AWS down and it moves Azure up just on my recommendation list.

From a technology perspective, it's well-proven, it's extensive, it covers just about everything you want to do. That's what I talk about with clients mostly, is the technology side.

While I used to rate the solution ten out of ten, the fact that Amazon can just kill a company on a whim makes me lower my rating. Currently, I'd rate it at an eight out of ten. It's great in almost every way. However, a company needs to understand that AWS can kill your company in a moment if it feels like it.

We do have quite a lot of AWS deployments and clients in certain countries.

We use it for spinning up environments, using infrastructure as code. We use it for disaster recovery and high availability for creating BMs for testing. Mainly on the service side, we use it for setting up environments and spinning up environments.

The monitoring is the most valuable aspect of the product.

Technical support is available if you need it.

The solution is stable.

The scalability is okay. It's similar to what you would get with Azure. 

The interface needs a bit of work. It's not intuitive.

The solution's initial setup can be complex. 

I've been using AWS for about 15 years. It's been a very long time. 

The stability is fine. I haven't had issues with crashing or bugs or glitches. 

The solution's scalability is pretty good. These solutions are pretty well known for not being able to scale well. They behave very differently at scale. I wouldn't say it's any better or worse than Azure is; it's probably on par.

Internally, we have about 500 people using the solution right now. 

I have never used technical support myself, although it's my understanding that our team does from time to time. We do all the first line ourselves. Anything that escalates to the third line, we have contracts in place to help us get assistance.

I found the initial setup to be pretty complex. It's just getting more and more complex, with the infrastructure as CodePipelines and that sort of thing. On a scale of one to five, one being the worst and five being the best in terms of complexity, I'd say it's a three.

I have no idea what the operational side does in terms of maintenance. It's not an aspect that falls under my responsibilities. 

I don't handle the licensing side of things and therefore cannot comment on the price of the solution.

We also looked at Azure DevOps.

I'm a customer and an end-user.

We use various deployments, including on-premises, public, private, and hybrid clouds. The deployment is dependent on the customer, the solution, and the service level agreements that we have. We use all of those models. We make our choice based on the requirement.

I'd advise potential new users to actually do a shootout between the different products based on your use case and choose the right one.

I would rate the solution seven out of ten. I'd rate it higher, however, the UI needs improvement first.

We are both a user and a provider of services to some of our clients. We are not official partners, but we provide regular services to set up our clients' infrastructure on AWS. We deploy their projects there with their own account so that we can hand over technical ownership whenever they need it. As a result, they can continue to provide their services to other consultants. we offer these services to set up their systems and their services.

We use Amazon AWS mostly for typical hosting for applications, some emails, queuing services, and databases most of the time.

I am not sure what features they'd like.

AWS has large community support. You are never stuck with anything if something doesn't work in time.

We don't have any issues for the time being, because I intend to use this in a limited, not exhaustive, manner. For the time being, we're fine with whatever we're doing.

The billing should be more competitive.

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

As AWS is online we are always using the most current version. We have some virtual machines that you create based on the version when you initialize them, but the services that you use on a daily basis are always the most recent version.

We have a limited number of users and use standard services.

There have been no issues. The support is good.

There are no issues at the moment.

We were hosting on bare metal servers. Then we moved on to VPS servers, which were managed by our technical staff. And now we're utilizing cloud services.

That technical management part for the multiple VPS, as well as for ourselves and our client, is taking a long time to maintain and everything. As a result, we went to manage services.

These are some additional options. I've seen that Azure has the best cloud dashboard, but the billing and other features are very difficult to use. The same as any other cloud service. The documentation is far superior.

The installation is straightforward.

Cloudflare and other services are developing more affordable solutions. They provide a much cheaper alternative to Amazon's S3 storage buckets. That's something that could be improved.

This should be comparable to the other options on the market.

Billing for cloud services can be difficult at times. In the VPS, you only have quota-based billing management, but in the cloud, it's as if every bit and byte and every I/O operation is metered, and your bills can be surprisingly high when you've published something that can attract a lot of traffic, which is one catch.

We researched Microsure and Google Firebase, but we are not using these solutions.

I'm not an expert. I don't have any advice at the moment, but whenever they're looking to host some applications, when there's a lot of traffic or bandwidth, they should think about it carefully. 

I would rate Amazon AWS a seven out of ten.

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.

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.

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.

I've been using AWS for the last seven years.

AWS has "11 9s" service availability, which means the service is available 99.99999999999 percent of the time. 

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. 

Positive

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.

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.

The customer can deploy their application on Amazon AWS instead of taking care of their infrastructure.

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.

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.

I have been using Amazon AWS for approximately two years.

Amazon AWS is stable. However, they have had a few outages but nothing very serious.

Amazon AWS is quite scalable. And they have a lot of auto-scaling functions for their VMs.

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.

The length of time and difficulty of the implementation depends on the scale and the complexity of the project.

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.

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.

I have evaluated Microsoft Azure and Google Cloud.

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.

We have applications that are running on the PaaS platforms.

In the healthcare environment, we use Amazon AWS to run healthcare and hospitalization applications.

The end-user is largely unaware of how the backend works, so some of the services are provided by Amazon. So, where we are, some of the applications have been running since the beginning, and we have been using them. And some of the services are required by the packages we are running, so they use Amazon PaaS as a service.

In general, Amazon's performance is good.

When I try to enter the multi-cloud, they provide very poor support. Support is a concern with Amazon.

I have been using Amazon AWS for a few years.

Amazon AWS is a stable solution, it is far more stable than some others.

Amazon AWS is scalable, depending on the platforms and services that are used.

In our company, we have 50,000 employees who use this solution.

We intend to increase our users based on how the new releases go, and if the economics work out better than Google and Microsoft, we will definitely look to Amazon because Amazon can be extremely competitive at times.

It should be faster. Unlike Google's and Microsoft's support, Amazon's support should be faster.

We have used other PaaS clouds previously.

The hospitals were available on Amazon. We have certain hospitals that were part of the group when it first started, but there are a lot of hospitals that are in the process of being acquired. Once the setup is acquired, it is extremely difficult and time-consuming for them to bring it through one enterprise architecture. Now, it is not necessary to have services from only one cloud service provider; instead, we can have services from multiple providers, and we are working to integrate the multi-cloud.

Essentially, you must design and optimize the architecture. It is not the most straightforward process to install. You must first design your architecture and then optimize it in relation to the services.

Earlier I used to work there, and we had a real skill shortage because we needed people who could understand and work in the cloud. When we developed centers of excellence and core competencies, people were required to work across multiple platforms, which is a challenge that we are currently working on. As a result, the real challenge now is for a team to have a multi-cloud. Now, if we can develop this talent organically, that will be fantastic. We'll spread out the support team we require. Another initiative that is being worked on is automation, automating scripts, and new technologies, which are assisting us greatly with serverless and cloud computing.

It can get quite pricey at times. Because of the patterns we're attempting to use, it becomes very expensive. Where we can save money by using Google components or Microsoft components, we can go much cheaper.

You must pay a licensing fee, which is based on the usage.

Essentially, it is determined by how we use the services. There are sometimes are a soft service, sometimes we pay yearly, and sometimes we pay as we use it.

Yes, I would recommend this solution. If we compare the three, I would rank Google first, Microsoft second, Amazon third, and the rest would follow.

I would rate Amazon AWS a seven out of ten.

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.

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. 

I have been using Amazon AWS for approximately two years.

The solution is very stable.

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.

The technical support is very good.

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.

We are on an annual subscription for Amazon AWS.

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.

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.

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.

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. 

I have been using Amazon AWS for around two years.

AWS is very stable. They have an SLA of 99.99%.

AWS is very scalable.

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. 

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. 

Our company is a partner with Amazon, we implement in-house. 

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.  

The solution is good for integration. It's very flexible and customizable with other services, public, cloud and on-premise.