Amazon AWS Reviews

I use the solution in my company to use several services like ECS, EKS, and S3 while also making it easy to use its hosting services in our infrastructure. The solution is good for efficiently leveraging all the aforementioned services to host different products.

The cost of the product is an area of concern where improvements are required.

I have been using Amazon AWS for around six years.

The solution's stability is good. Stability-wise, I rate the solution an eight out of ten.

The product's scalability is good.

All the people in my company use the product. My company has engineers, software developers, site reliability engineers, and DevOps engineers who use the product.

The solution is used on a daily basis in my company.

For the purpose of scaling our company's operations, we host most of our applications on Amazon EKS. My company uses third-party open-source solutions for scalability purposes, so we are not completely dependent on Amazon AWS for autoscaling.

My company takes care of the problems related to the product. My company doesn't contact the product's technical support team. Though I have some previous experience with the product's support team, I haven't recently contacted them.

Previously, I worked with a tool on an on-premises model. I chose Amazon AWS since I wanted to use a cloud-based product.

My company is not dependent on Amazon AWS for deployment purposes since we use our own tools to handle the deployment area. My company uses Amazon AWS for the underlying platform but not for the deployment area since we have our own setup for it.

The initial setup phase may be pretty easy for those who learn to gain knowledge and expertise in Amazon AWS. At the initial stage, the product's users may look for more documentation on the tool, but I feel that the services under Amazon AWS are self-explanatory. I rate the product's initial setup phase a seven or eight out of ten.

I am a part of the team in my company that carries out the product's deployment in multiple regions.

The product's deployment process consists of a fully automated setup phase. Though my company had to be involved in a lot of engineering work in the initial phases, only around four to six members were required to take care of the deployment after the automation.

The solution can be deployed in around 10 to 15 minutes.

The tool is expensive.

As of now, our company does not need to leverage Amazon AWS for Amazon Big Data Analytics or Amazon Machine Learning. In the future, Amazon AWS can be used to leverage the benefits of Amazon Big Data Analytics or Amazon Machine Learning. Presently, my company plans to stick with the microservices model.

There is no need to maintain the product from our company's end since Amazon AWS takes care of the maintenance of the services the tool covers.

For cost saving, shut down instances when not in use and use spot instances while implementing step scaling policies. Doing regular audits, you will get to know what resources in your environment are leading to cost consumption.

AWS Global Cloud Infrastructure does not directly impact our company's application performance and availability. My company just consumes the services covered under Amazon AWS, after which we plan our application architecture. The impact is felt if Amazon removes support for some of its global products, as it may impact some legacy applications, but my company does not face many issues since we mostly upgrade such applications.

I rate the overall tool a seven or eight out of ten.

The product is easy to use. Its availability and support are its biggest strengths.

IAM must be made simple and straightforward. It is a little bit complicated compared to GCP.

I have been using the solution for three to four years.

The product is stable.

The product is scalable.

My company had signed up for professional support. We did not have any issues with support. It would be really tough to reach out to the support team on a personal level. For personal users, I rate the support a three to four out of ten. For professional users, I rate it a nine out of ten.

We are also using Google Cloud Platform. The choice of the product depends on people’s familiarity and their inclination toward using a certain product.

The tool’s pricing is reasonable.

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

The introduction of the ITD pipeline makes the development and operation cycle easier for the organization.

The solution also helps organizations to move applications to a containerized platform.

Instead of using some third-party solutions, Amazon should include them as part of its offering.

Currently, we are using some third-party services for various purposes. Amazon can acquire those open-source products and provide them with managed services.

I have been using Amazon AWS for about six years.

I rate Amazon AWS an eight out of ten for stability.

The solution's scalability is always high, and the customer can seamlessly scale up the solution. I rate Amazon AWS an eight out of ten for scalability.

The solution’s technical support is good.

Positive

The solution’s initial setup is very easy. Amazon AWS is the easiest cloud platform to learn and deal with compared to any other provider.

I rate Amazon AWS a nine out of ten for ease of initial setup.

Any service built on AWS is very easy and quick to deploy and does not take much time. Within 10 to 15 minutes, you can bring a server up and launch a website.

The pricing of Amazon AWS is high compared to any other cloud provider.

Amazon AWS was deployed on the cloud in my organization.

Overall, I rate Amazon AWS an eight out of ten.

We deploy our core application and our integrations platform on AWS EC2 instances. Both applications contain multiple containerized Python Django applications, which need to scale with how often and how intensely customers use the platform. 

We need a secure cloud environment to support our new self-service API, allowing customers to hit our services from outside an outside service. AWS provides the security, scalability, and flexibility to make this happen.

We also store large customer files on AWS S3 Buckets.

Without AWS, our organization simply would not exist. Our entire tech stack is served on AWS. Thanks to AWS, we have been able to save money. Thanks to AWS, we have been able to save time and utilize technical resources in other ways. Other ways include building out the front end of our application as well as the back end of our application. Without AWS, we would have to hire network/server engineers, which would take away from our overall speed of growth.

We have found the Elastic Cloud Compute service (EC2) as well as the simple storage solution (S3) to be the most valuable aspects of the solution.

We deploy our core application and our integration platform on AWS EC2 instances. These applications contain multiple containerized Python Django applications, which need to scale up and down dynamically. They also need to be secure to prevent unwanted bad actors from using our AWS compute instances for malicious activity.

Finally, we find the S3 buckets to be quite valuable. S3 allows us to securely store large customer files without fear of them being compromised, changed, lost, or corrupted.

I am not an expert in AWS, nor do I work in the dev-ops department, so I might not be the best person to ask this question. It could be made cheaper. I know we spend a lot of money each month on AWS.

We have been using AWS since the company was founded in 2017 - about five years.

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 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 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.