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.

The most valuable features of Amazon AWS are the EC2 instance for web applications with CDN Networks.

AWS Cloudfront is the official reference for the Global content delivery network (CDN) which significantly reduces latency or slow loading times.

There is a feature called Kinesis, which has to do with image processing. There are a few artificial intelligence tools that Amazon AWS should improve on.

I have been using Amazon AWS for approximately five years.

I have found Amazon AWS to be stable.

Amazon AWS is scalable.

The technical support has been challenging. I have found more tickets are being placed and the availability of the agents has been limited for some of the team members.

We selected Amazon AWS because it was the most mature at the time. It was the initial cloud provider. Then Google and Microsoft also came up with Azure and TensorFlow. TensorFlow is catching up with a few code web programming tools, and that is a point of interest as well as image processing.

In a future release, the solution could improve on the IoT integrations and API access.

The initial setup of Amazon AWS is complex due to how infrastructure is set up in different organizations.

For the initial 12 months, the solution is reasonably priced. On enterprise license contracts where you negotiate, have been reasonable too.

I would encourage the student package for someone who is starting out, they can get acquainted with the interface and the tools available.

I rate Amazon AWS a seven out of ten.

We are doing our own custom development, which is run on AWS.

We have done a lot of work using Amazon AWS.

All of our deployments are hosted on the Amazon AWS Cloud. Because many of our client requirements are on AWS, we have our own AWS development environment, and then we use GitLab to migrate it to the client environment.

We write a lot of Lambda functions for various services, as well as serverless functions.

We use Amazon S3 to store a large amount of data and images.

We also use Amazon DynamoDB Database for many of our developments.

Many of these features are already available on AWS. We're just getting started, and we're still learning a lot.

The performance is good.

We would like to see if AWS includes any inbuilt automation. Also, we are very interested in AWS's AI/ML features, as well as IoT, AR, and VR.

We have been using Amazon AWS for the last couple of years.

The stability of Amazon AWS is good. We have not had any issues.

It is easy to scale.

In our company, we have approximately 20 people who are using Amazon AWS, on a daily basis.

We have a few issues in the beginning during the setup, but we were able to resolve them ourselves.

We are satisfied with the technical support.

The development is primarily on Python, Node.JS, and Java technologies.

The initial setup was quite complex at first, but once we got the hang of it, it was simple.

It took a week to complete the installation from scratch.

Because it is a cloud product, it does not require a lot of maintenance. We have CloudWatch and some alerts set up, which is how we manage everything, including utilization.

We completed the installation internally.

The pricing is fair. We don't have any issues with the pricing.

I was evaluating different ways to incorporate RPA.

I would recommend this solution to others who are considering using it. 

It's very scalable and serverless. We are only charged for the functions that we use. This includes Lambda, which is a nice feature, in my opinion.

I would rate Amazon AWS an eight out of ten.

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 build our own service virtualization tools. We use Amazon AWS for cloud hosting. AWS has a lot of services that we use.

Everything in AWS is valuable? AWS itself is valuable in multiple ways. Whatever I use is valuable, which is the reason we use it.

It has a lot of new features that make our lives easier in terms of what we want it to do in the house.

I have been using Amazon AWS for four years.

Amazon AWS is quite stable, which is why it is used by many people.

Amazon AWS is highly scalable.

There's no tech support. AWS operates under a different model. There is no simple tech support available, as there is in other traditional methods. We have an enterprise account, so it's not like individual tickets; we have an enterprise client relationship, so it's very different.

It is easy to access them.

I've worked with a variety of service virtualization tools.we have not used anything from IBM. We don't use Azure, we use Amazon AWS. AWS as an IaaS or PaaS cloud solution.

The initial setup is straightforward. However, you can't give a broad overview of your setup as it depends on your use case.

There are numerous use cases, and the setup varies from complicated to very simple in some cases. As a result, I don't want to give a generic answer.

It's quite good, I would rate Amazon AWS a ten out of ten.

Amazon AWS has a better portfolio. They have an impressive technology and service portfolio.

The invoicing procedure of Amazon AWS needs to be improved. It can be difficult to manage.

I have used Amazon AWS within the last 12 months.

The technical support of Amazon AWS is good.

I have used Oracle previously, and I don't see any difference between Amazon AWS and Oracle from the stability and availability point of view.

Amazon AWS is a bit more expensive than Oracle.

I rate Amazon AWS an eight out of ten.