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.

I generally EC2 workloads. We use it to host our applications and provide our software service on the cloud. We integrate with EKS (Elastic Kubernetes Service) to manage containerized applications.

EKS helps us manage our containerized applications on AWS. We use various AWS services for different functionalities, such as computing services, database storage, content delivery, etc.

AWS's security model, including IAM or security groups, has contributed to our organization's compliance. It manages authentication, permissions, and overall security posture, which helps us maintain compliance.

AWS has made our lives much easier. It simplifies workload management and operations.  

The cloud-based nature of AWS is crucial for scaling our resources effortlessly. It's a key reason we chose AWS.

We find EKS particularly helpful for its ease of use and management of containerized applications.

Faster API response times and an improved console experience would be better. Enhanced performance across APIs and the console would streamline our workflows.

In future releases, improved compatibility and minimal downtime during upgrades would be significant enhancements.  

I have been using it for seven years. 

I would rate the stability a nine out of ten. It's generally very reliable.

I would rate the scalability a ten out of ten. No problem with scaling this product.

There are around 300 end users in my company using this solution. 

AWS technical support is good in general.  

Positive

The features, quality, and support are likely comparable to other products.

The initial setup is simple. 

Pricing definitely isn't high; I would rate the pricing a five out of ten, with ten being expensive. 

AWS pricing is quite competitive. AWS is cost-effective because it saves time. Faster deployments and testing make it very valuable. Pricing isn't the main thing; it's more about getting things done efficiently. Then, engineers can discover additional savings within AWS itself.

So, it's more flexible. We save a lot of time thanks to AWS

Overall, I would rate the solution an eight out of ten. 

I build infrastructure from the ground up. VPCs, in-depth virtual machines, new websites, migrations from on-prem to AWS, or even between cloud providers. 

Recently, I started building chatbots using Amazon Connect, IVRs, and Lambda. Lambda is also used for the contact center's business logic.

Based on what I do, it's not one service; they're interconnected. For example, when migrating a website from one cloud provider to another, I use EC2, a database system, and Route 53 for DNS. They really depend on each other. 

Now, if I had to pick just one... I like EC2. I can spin up applications and shut them down. When I work on security groups, opening and closing ports, EC2 allows it.

There is room for improvement in cost. Everyone complains about AWS being expensive. The initial cost starts small but can skyrocket unexpectedly. That's why some people, like my friend, have moved to Linode. 

Linode tells you upfront: "This instance with this configuration will cost $20/month. That's it." There are no hidden fees.

With AWS, it might start at $20, but then it creeps up to $35, $40, $50, and so on. It's a big concern, and people are even moving back to on-prem infrastructure because of it. 

Cost is crucial, and I see it myself. It gets expensive over time. AWS needs to improve its cost transparency and offer more predictable billing options. 

The cost is what everyone is running away from. It gets expensive over time.

I have been using it since 2014. 

Stability is guaranteed because the stability depends on how you design your solution. 

AWS has what's called the shared responsibility model. It simply means there's the work of you, the customer, and the job of AWS as a cloud provider. They handle the physical infrastructure, but you, the customer, need to be able to set up the application in such a way that if anything breaks, you can stabilize it. 

If you're designing your infrastructure using, for example, there are several factors you need to consider when designing your infrastructure, like scalability, security, etc. There are about six of them. 

So, you need to take all of those factors into consideration when designing your infrastructure. Because if you don't design it well, it could fail. So you have to design it so that it shouldn't fail. 

The onus is not entirely on AWS for you to have a stable infrastructure. You need to design your infrastructure properly, and then AWS manages the physical side of things. But overall, it's a stable cloud provider. That's why they're number one.

It's highly scalable. It's guaranteed 99.99% uptime, and it shows you can scale up or scale out whenever you need more space. 

Scaling up means you can add more memory to your VM at any time or increase the size of your database. Scaling out means you can create multiple VMs in different regions if you want; that's where availability zones come in. 

You can add more VMs if needed, and if one shuts down for any reason, the other one comes up. This is where load balancers come into play. The load balancers automatically create new VMs to manage the load of traffic coming to your website or application. So, it's highly scalable.

I have not personally contacted the support team. 

The first time I used AWS was in 2014 for my first project on the platform. That was the first time I logged in to the console, created a VPC, and deployed a VM. Everything was new to me. I used Udemy to learn to learn about this product in 2014.

I actually learned as I went along on the project. I knew nothing about it before starting, and I figured it out along the way.  

The difficulty level for the setup depends on how inquisitive you are and how deep you want to learn. If you're not patient, you might miss things. 

You need to have that initial interest and drive to start, and that makes it easier. For me, it was very easy because I was on a project, and it had to be successful at all costs. So, there was pressure, and I had no choice but to make it work. So, it depends on the scenario. 

But overall, it should be easy for a new person to use AWS because there are so many resources available. There are tons of white papers, online courses, and documentation on GitHub, and AWS has a lot of documentation online as well. So, it makes it easy. There's a step-by-step guide on how to use the infrastructure. So, it should be easy for a beginner. 

Setting up a VPC takes less than three minutes. Then, for it to start loading in AWS, it may take an additional two minutes. Then, for the VM, after creating the VPC, it depends on what you want. Do you want a Linux VM, Amazon Linux, Windows, or Mac OS? Whichever one you choose, if it's already created with all the dependencies from the marketplace, spinning up a regular Linux server on an Amazon VM should take less than three to four minutes. It is easy and very straightforward.

I would rate the pricing a nine out of ten, with ten being the most expensive. It's pricier than Linode, which has a fixed price and it is still a pay-as-you-go service. While for,  AWS, over time, it gets expensive. 

Linode is much cheaper and good for small businesses. 

It's good for big players like Fortune 500 companies, but smaller companies struggle. My friend's company even left AWS due to costs. So, for smaller companies, it's expensive.

Use the AWS calculator to confirm resources and configuration. That'll give a budget estimate and insight. 

In cloud space, it is called TCO (Total Cost of Ownership). Before buying, ask:

1. How many VMs do I need?
2. Why am I moving to the cloud?

Write down those answers and your resource needs. Then, use the calculator to project costs over six months or a year. Remember, it's not perfect - there might be hidden costs. If it says $10,000, expect $12,000. So, add a buffer. Only then commit.  

My advice is to check the calculator first for an estimate, then research GCP and Azure to compare before deciding. Use data to make informed choices and decisions.

Overall, I would rate the solution a nine out of ten. Saving that one point for pricing.

The thing is, in case of disaster, then you really need to think about the disaster, which is less cost-effective. If I'm the customer and I have a midsized environment, I need to host a web application or a front-end application. Why should I go with this on-premises data center, the firewall, the hardware, and then monitoring, then administration? These are more cost-effective. 

So, I will go with the midsized and small-sized public cloud where I can have the opportunity for high availability with the region side. And secondly, in case of disaster, we have the product available without any downtime.

The style, the thoughts, and the people are still not convinced with this public. But they don't have any other options. It has been changed after the pandemic only.

The best thing is scalability.

Some people complain that customization is very difficult in AWS. So they think there are other options. If we have everything ready in AWS or any public cloud, if I have two deployments in bulk, then I will get automation. If automation is ready, then I can do everything in a single click.

In future releases, I would like to see more automation.

I started using this solution after the pandemic. So, it has been three years now. And one thing I have noticed is that after the pandemic, it is more recommended to move to the public cloud. 

Prior to the pandemic, people were thinking of expanding their data strategically with Cisco UCS. They thought in that way. But now the approach has changed.

I used Amazon AWS for a small business, like a midsized business that wants to build their environment in the public cloud. And they want to get high availability, and in case of disaster recovery, they can have other opportunities.

We don't have a much bigger environment. So we have a smaller environment, like 10 to 15 VMs.

For a smaller project in Europe, we deployed Dell VXL for 35 sites. The customer has now invested in Dell VXL and is building 30 to 35 sites for Dell VX-ten. This is a huge investment, so they need to stay on this platform for five years. By the end of their standard support period, their hardware will be end of its life. In the meantime, they are exploring the public cloud to create a hybrid environment. Once their hardware becomes obsolete and offline, they will definitely consider the public cloud. Similarly, people who are still on-premises with legacy or Cisco systems will also consider the public cloud. They are in the existing environment and are just waiting for their hardware to reach the end of life. For the next expansion, they want to move to the cloud.

The initial setup is easy.

In a cloud environment, we need just to associate that business. If I have to build approximately 10 to 15 VMs, we have the templates. We have the AMI. We have everything in place. We need to just automate and place everything in the dashboard. It is very easy to customize.

I will recommend you to use it, at least explore what services they are offering, what features they are offering.  

Overall, I would rate the solution an 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.

We build business applications for our customers using Amazon AWS in 15 different industries.

Many of my customers use many cloud services together.

The most valuable features of Amazon AWS are the high level of capabilities, cloud-native environment, developer-friendly, intuitive interface, and automation. The solution overall is easy to learn from the resources available.

The customization could improve. However, it depends on the customization needed. 

To enhance its capabilities, Amazon AWS should improve its integration with other digital security platforms and solutions, especially those used by companies in domains, such as banking, financial services, and insurance. While Amazon AWS has its own solution, there are many other initial vendor companies that perform exceptionally well. Therefore, it is crucial for Amazon AWS to have better integration with those platforms and solutions, including how to host and integrate them with the rest of the Amazon AWS services. Although Amazon AWS has its strengths, it doesn't always work seamlessly for customers, making it a significant obstacle to migrating applications to Amazon AWS. Rather than focusing on developing new features, Amazon AWS could better serve its customers by supporting these existing solutions in the digital security space.

There are many excellent encryption solutions available, along with many other solutions. By supporting these solutions and offering easy integration, Amazon AWS can create a win-win situation for its customers.

I have been using Amazon AWS for approximately seven years.

When you have complex deployments, such as with more than two availability zones, there are reliability, and resiliency options that are complex to implement and expensive. Providing stability or more complex deployments is possible, but very expensive.

I rate the stability of Amazon AWS a nine out of ten.

We have more than 50,000 users using this solution in my organization. Everyone in our company is using the solution.

The solution is highly scalable.

I rate the scalability of Amazon AWS a ten out of ten.

The support provided by Amazon AWS is highly responsive. We have a strong alliance with Amazon AWS, and we regularly interact with their teams. They conduct knowledge-sharing sessions for us and keep us informed about new features. They are always available to support us. They have helped us from the inception phase of any large engagement up to providing help in troubleshooting some problems. They are extremely helpful.

I rate the support of Amazon AWS a ten out of ten.

Positive

I have worked with Google Cloud Services and Microsoft Azure.

Amazon AWS is known for building many industry platforms, and companies often look to all three hyper scalers to help them build such platforms on Amazon AWS. Large consortia of companies collaborate on such initiatives. However, Google and Azure are more interested in partnering with and supporting industry-level consortiums and technology initiatives, while Amazon AMS sees it more as an engineering capability and expects developers to build everything from the ground up. Therefore, Amazon AMS may need to adjust its approach slightly in comparison to its competitors.

The simplicity of Amazon AWS depends on the engineering processes implemented by the client's organization. Setting up these processes may take some time, but the AWS SDK provided by Amazon is helpful. Moreover, integration with other tooling is also necessary.

Once the processes and platforms are configured, the execution becomes automatic. This has been successfully accomplished in many engagements where pipelines are run for tasks, such as provisioning new infrastructure and making multiple releases.

For a business with a small deployment and with minor features needed the process of implementation can take 30 minutes and in some instances less than 15 minutes. However, if it's a large release with multiple features, including verifications, it can take up to one and a half hours maximum. The more features added the longer the implementation will take.

In comparison to Google Cloud Platform and Microsoft Azure, the database offered by Amazon AWS is relatively expensive. However, the database also offers rich features.

I rate the price of Amazon AWS a six out of ten.

If you compare Amazon AWS with other hyper scalers, such as Microsoft Azure and Google Cloud Platform, Amazon AWS is the most sophisticated cloud development platform.

The amount of people for the maintenance of the solution depends on the engagement we have with our customers. Some of our customers are sophisticated with modern infrastructure and can handle most of the maintenance themself.

The engineering team responsible for development also handles maintenance, upgrades, and support without any differentiation. However, some customers still follow an older mindset, where a separate ops team is responsible for platform maintenance and operations.

One approach is to have a centralized model where a team of 20-30 members manages all the applications, including operations and maintenance. Alternatively, a distributed model may be used, where four or five different teams manage different aspects. However, on average, the team size for the entire IT organization is typically around 20-30 people.

I strongly recommend this solution to others.

I rate Amazon AWS an eight out of ten.

I gave my rating of eight because the price of the feature is more expensive than the competitors.

One of the most common use cases is people using the solution for hosting. Many people use it to backup their on-premises solution to the cloud. This is the most common use case I know of. 

The most valuable feature is the backup ability. Most people are used to one type of backup solution that they're using, but most of these solutions have features that make it difficult to transfer to the cloud. I know that Veeam now gives people the opportunity to backup some on-premises solutions to the cloud. This feature is something that a lot of people are looking for. 

I'm not an expert on the product, but if I had to suggest one improvement, I know a feature that would allow a person to back up his on-premise solution to the cloud directly with one click would be useful. This solution should be agnostic because sometimes a product that was backed up with Veeam is highly compatible with Commvault. I think it would be better if these backup features were agnostic. 

Viewing a build could also be improved. It's not easy to follow up on your consumption and see how much you're paying and how much you will be paying. Viewing the build could be more clear. 

I have been working with Amazon AWS for three years. 

This solution is stable. 

This solution is scalable. 

Two years ago, I was working on proofs of concept and I got in touch with their support. It was okay and they handled it. 

The setup process was quite simple. 

My company implemented through an in-house team. My company also provides the maintenance for this product. 

Amazon AWS is on the cheaper side, as their pricing is more competitive. There are no additional costs besides the license. However, Azure sells Microsoft licenses, so they have an advantage. 

I was aware of Google Cloud and Microsoft Cloud, but I chose Amazon because they have better products and more features. At the moment, Amazon is the leader in everything. 

I recommend trying Amazon AWS. You have nothing to be afraid of, as long as you're clear that you can handle your build. 

This product is suitable for any company, whether small, medium, or large. 

I would rate Amazon AWS an eight out of ten, just because there's always room for improvement. 

I'm not the developer, so I cannot judge the services provided by AWS, but we run our mobile banking application on AWS. Database-wise, it's heavily based on Elasticsearch, so this is probably one of the main features that we find most valuable. Aside from that, I'm not familiar with which AWS services we are using.

It's too early to say what needs to be improved, as we went live only at the beginning of this year. We started last year and went live at the beginning of this year, so it's still a work in progress. In terms of additional features we'd like to see, the one thing that comes to mind is better integration with Oracle. We have a lot of Oracle databases, and there is no other option to either migrate to PaaS, stay on-prem, or use Oracle Private Cloud. So better integration with Oracle is something we are looking into. It's the same story with AWS or Azure. 

We introduced AWS in production last year, so it's a relatively new development.

Setting up AWS was pretty easy. It was straightforward to set up, and it took us a year to develop and migrate our mobile banking solution to the AWS cloud. Our migration experience was quite positive.

The pricing of AWS was attractive for us, so that's something that's okay at least for this transaction-based system. However, we still have some concerns about more data-driven applications or those that involve a lot of heavy uploading and downloading. So our whole data warehouse is still something that would not go into the cloud because of the pricing model. So if you stayed pretty much in the cloud, that's fine.

I would rate Amazon AWS seven out of 10. We're really satisfied.