Try our new research platform with insights from 80,000+ expert users
Data Center SME at Orange España
Real User
Top 5
Provides high availability and the ability to operate without downtime in case of disaster
Pros and Cons
  • "The best thing is scalability."
  • "In future releases, I would like to see more automation."

What is our primary use case?

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.

What is most valuable?

The best thing is scalability.

What needs improvement?

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.

For how long have I used the solution?

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.

Buyer's Guide
Amazon AWS
November 2024
Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,192 professionals have used our research since 2012.

What do I think about the scalability of the solution?

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

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
Kublai Gomez - PeerSpot reviewer
Senior Software Engineer at Userlytics Corporation
Real User
Top 10
A solution with a great uptime that needs to improve its pricing models
Pros and Cons
  • "The most valuable feature of the solution is that they offer everything around in just one platform."
  • "Price is an area with a shortcoming in the solution that has a scope for improvement"

What is our primary use case?

The use cases of the solution depend on your project. The project I am working on right now is using Amazon Rekognition heavily, along with S3 and EC2. There are a lot of instances involving EC2. The last one involved using a text-to-speech, of which I don't remember the name, but that was the project's main goal. The use cases depend on the circumstance of your project, so it is not the same for all.

What is most valuable?

The most valuable feature of the solution is that they offer everything around in just one platform. They have almost everything. For example, a couple of weeks ago, I was trying to build a server with RabbitMQ for some kind of real-time communication in an environment where I was working. Amazon already has a service named Amazon MQ, because of which you don't need to configure your server by yourself since you already have it integrated into the ecosystem. It's easy to ensure that the server is there for your system without any issues and allows you to run it in seconds instead of three or four days.

What needs improvement?

Price is an area with a shortcoming in the solution that has a scope for improvement. Amazon can improve in some areas related to its pricing. Amazon selected the pricing plans, and I had to choose one. In general, it is an expensive tool.

It is cheap when you are starting with the tool since they have this free tier. However, that is not the reality when you really start working with Amazon since you will end up paying a lot at the end of every month.

For how long have I used the solution?

I have been using Amazon AWS with different clients for six to seven years. I am a customer of the solution.

What do I think about the stability of the solution?

I believe that it's a stable product. I never had any issues with Amazon. I'm trying to remember, but I think that I have never faced any stability issues. It was working twenty-four hours and seven days a week all the time.

How are customer service and support?

I have contacted Amazon's customer support. It was just a couple of calls when I was working in Iceland on a project, and the servers were not reachable. There was some kind of issue at the country level, not an issue of Amazon specifically. There was some issue with the solution in Iceland.

How was the initial setup?

The initial setup is a thing that you need to learn. The setup part is not easy at all. Usually, in some companies, you have a person that works only with Amazon. You have one profile in your company just to work with the infrastructure services inside Amazon. You need a kind of specialized profile for that work.

What's my experience with pricing, setup cost, and licensing?

The solution's pricing depends on your traffic since they charge you based on the traffic, not the servers. The price can go into many, many thousands depending on the traffic.

The price also depends on your services since, if you are using Amazon Rekognition or S3 with a low tier price.

What other advice do I have?

Well, for a small company, normally, my advice would be that Amazon AWS is not the best option. If you are trying to use Amazon for the first time, it means you need a big project on your hands, and you already have an MVP running. If you are going to use Amazon for the first time, then you already know what you are going to deal with, so such people don't need my advice in that case.

The price is my concern, so I am searching for some other options to leave Amazon. It is not for quality-related reasons.

I rate the overall solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Amazon AWS
November 2024
Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,192 professionals have used our research since 2012.
Solution Architect at a tech vendor with 10,001+ employees
Real User
Top 5Leaderboard
Easy to use, manage and crucial for scaling our resources effortlessly
Pros and Cons
  • "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."
  • "Faster API response times and an improved console experience would be better. Enhanced performance across APIs and the console would streamline our workflows."

What is our primary use case?

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.

How has it helped my organization?

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.  

What is most valuable?

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.

What needs improvement?

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.  

For how long have I used the solution?

I have been using it for seven years. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

How are customer service and support?

AWS technical support is good in general.  

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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

How was the initial setup?

The initial setup is simple. 

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2335179 - PeerSpot reviewer
Manager at a tech services company with 11-50 employees
Real User
Offers integrated services and quickly spin up and shut down applications using EC2
Pros and Cons
  • "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."
  • "There is room for improvement in cost. Everyone complains about AWS being expensive. The initial cost starts small but can skyrocket unexpectedly."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using it since 2014. 

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

I have not personally contacted the support team. 

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1280193 - PeerSpot reviewer
Assistant to Vice President at a consultancy with 10,001+ employees
Real User
Top 5
Useful automation, learning resources easily available, and intuitive interface
Pros and Cons
  • "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."

What is our primary use case?

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

Many of my customers use many cloud services together.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Amazon AWS for approximately seven years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
Cloud Architect at a tech services company with 10,001+ employees
Real User
The most valuable feature is the backup ability
Pros and Cons
  • "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 backup 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."

What is our primary use case?

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. 

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

I have been working with Amazon AWS for three years. 

What do I think about the stability of the solution?

This solution is stable. 

What do I think about the scalability of the solution?

This solution is scalable. 

How are customer service and support?

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. 

How was the initial setup?

The setup process was quite simple. 

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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. 

Which other solutions did I evaluate?

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. 

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Managing Director at Erste Group
Real User
Good price, easy to set up and migrate, but could use some more integration
Pros and Cons
  • "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."
  • "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."

What is most valuable?

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.

What needs improvement?

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. 

For how long have I used the solution?

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

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Binoj BALAN - PeerSpot reviewer
Principal Solution Architect at StarOne IT Solutions
MSP
Top 5
Allow customers to easily manage their entire AWS infrastructure through code, and the managed services that handle the heavy lifting for us
Pros and Cons
  • "I like the auto-scaling functionality and compliance requirements, whichever they are requesting."
  • "One of the issues I'm facing is that my RDS SQL Server version 5.8 is reaching its end of life, and I need to upgrade it to a customer-wanted version. I want to do this on Graviton instances, but Graviton only starts with version 8.0 and currently doesn't support the 5.8 series. We've raised a Priority Feature Request (PFR) with AWS to have this functionality added for at least three months. This would give us enough time to upgrade our database to the 8.0 version without any issues."

What is our primary use case?

I use it to run our production workload.

What is most valuable?

I like the auto-scaling functionality and compliance requirements, whichever they are requesting. 

I also appreciate new setup services, which allow customers to easily manage their entire AWS infrastructure through code, and the managed services that handle the heavy lifting for us.

What needs improvement?

AWS could benefit from being more cloud-agnostic. This means allowing customers to easily migrate their workloads and applications built on AWS services to other hyperscalers if needed. Currently, the architecture feels closed, making it difficult for customers to move to different cloud providers seamlessly.

One of the issues I'm facing is that my RDS SQL Server version 5.8 is reaching its end of life, and I need to upgrade it to a customer-wanted version. I want to do this on Graviton instances, but Graviton only starts with version 8.0 and currently doesn't support the 5.8 series. 

We've raised a Priority Feature Request (PFR) with AWS to have this functionality added for at least three months. This would give us enough time to upgrade our database to the 8.0 version without any issues.

For how long have I used the solution?

I have been using it for the last two and a half years. 

What do I think about the stability of the solution?

The product is very stable and robust. I haven't experienced any issues so far.

What do I think about the scalability of the solution?

The scalability and elasticity are key advantages of AWS compared to other providers. This is one of the main reasons why hyperscalers like AWS are preferred.

If we need to add or remove workloads, the performance remains consistent.

More than 70% of our workforce uses this solution. So, there are more than 40 end users. 

How are customer service and support?

In situations beyond my expertise, I've contacted the engineers. They've been helpful in resolving issues, providing support with freezes, and offering guidance whenever needed.

The quality of the customer service and support depends on the engineer I interact with. 

However, in most cases, including my own, around 75% of the time, the engineers I've encountered have been knowledgeable, supportive, and flexible. 

While individual experiences may vary based on specific learning, I would generally rate the support as good.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

The specific reason my company chose this product was that whatever use case we were expecting, everything was readily available on the AWS cloud. We didn't want to reinvent the wheel. 

We just wanted to choose the right services that would be cost-effective, optimized, meet customer requirements, and offer elasticity, scalability, flexibility, and security. 

So, when we compared AWS to other cloud vendors like Azure or Google, AWS performed significantly better. Based on that, our leadership recommended going with AWS, and the business and technical teams supported that decision. So, by taking into account all the inputs from various departments, we decided to go with AWS.

How was the initial setup?

Setting up AWS was easy. I used Infrastructure as Code (IaC) with YAML codes to deploy the infrastructure quickly.

It took me about half an hour to spin up the VPC, security policy, launch instances, attach the Elastic Block Store (EBS) volumes, connect to the S3 VPN endpoint, and configure cloud-native services like CloudWatch and CloudTrail. 

However, it took me almost a week to prepare the IaC code beforehand. This code can be easily reused and modified for future deployments with any minor changes required by the customer's use cases.

What's my experience with pricing, setup cost, and licensing?

The pricing depends on the workload. For example, if your workload involves Windows technologies, AWS may not be the most cost-effective option. In that case, you might be better off with Azure. 

But if you're working with open-source technologies, then AWS can be a good choice. They have their own process called RabbitMQ, which is an on-premises architecture where you can recompile all your applications to run on your own infrastructure. This can significantly reduce your costs compared to other hyperscalers like Google, Oracle, or Azure.

So, it would be worth my money to go with Amazon AWS at the end of the day. However, if it's a Windows-based workload, I wouldn't recommend AWS.

What other advice do I have?

You can just go ahead with AWS with your eyes closed. You won't regret it.

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer:
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros sharing their opinions.