We use AWS for the development of applications and websites for our customers. We produce web applications.
Associate Director at a tech services company with 11-50 employees
Highly available, good documentation, and comprehensive APIs
Pros and Cons
- "The documentation is very good."
- "Not all of the functionality is available in Europe and our customers in France want to be able to use features that are only available in the US."
What is our primary use case?
What is most valuable?
This is a highly available solution with a good API.
The documentation is very good.
What needs improvement?
Not all of the functionality is available in Europe and our customers in France want to be able to use features that are only available in the US.
For how long have I used the solution?
We have been using Amazon AWS for six years.
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.
814,649 professionals have used our research since 2012.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
Amazon AWS is scalable. We develop projects for our clients, so the number of users grows each easy client. At this point, there are several hundred users and we plan to continue increasing our usage.
How are customer service and support?
We don't use technical support very much, so I can't properly evaluate them. What I can say about Amazon is that they do not have a larger support team in Europe or even France. If we compare them to others, for example, Google has more support in our country.
Which solution did I use previously and why did I switch?
AWS is the first cloud provider that we used.
How was the initial setup?
The initial setup is very complex.
The first time we deployed this product, it was long. It took several weeks. Now that we have deployed it for several clients and have more experience, it only takes a couple of days.
What about the implementation team?
We completed the deployment ourselves but there is a lot of documentation so it's possible, but it's better to have a consultant because it's difficult to know how to do it well the first time.
No staff is required for maintenance.
What's my experience with pricing, setup cost, and licensing?
We pay monthly licensing fees.
Pricing is an area that can be improved because it is very complicated. It considers the number of processes, bandwidth, and different kinds of usage. This makes it difficult to predict. When we receive an invoice, there are always surprises. Now that we have used it for a long time, we have more information and are better able to estimate it.
What other advice do I have?
My advice for anybody who is implementing this solution is to have a strategy for calculating or monitoring the price. For example, have some alerts set up.
I would rate this 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: I am a real user, and this review is based on my own experience and opinions.
Senior Devops at a computer software company with 5,001-10,000 employees
Easy deployment and integration with good pricing
Pros and Cons
- "Easy to deploy through the channel model for serverless architecture and easy to integrate through the organization model."
- "Some services which were easy to use through shortcuts are now more complicated to use."
What is our primary use case?
I've used it to create some internal projects for my organization, particularly for designing the infrastructure of those projects.
What is most valuable?
One feature I find most valuable is the easy deployment by using the channel model for serverless architecture. Another feature I find valuable is the versatility of the service S3 because it allows you to give permissions to describe the users from their own accounts, from external users, or external accounts.
What needs improvement?
On the console, they used to have some shortcuts making this solution easier to work with, but now we have been dealing with so many problems on the console, and some of the options are not very useful in my perspective, so they should bring back those options that make things easier to run some of the services.
Most of the time the options are pre-selected, or you have to go with the default settings, but from my perspective, there are some services which are now more complicated to use than before.
An additional feature I'd like to see in the future is more integration with public repositories, though some use their own repositories for security purposes, but I think it'll be easier to deploy services through public repositories.
For how long have I used the solution?
I've been using this solution for almost four years now.
What do I think about the stability of the solution?
This solution is stable. I've been using it for a long time and have only seen an outage in one of the regions. It's a good solution.
What do I think about the scalability of the solution?
The scalability of this solution is good.
How are customer service and support?
The technical support of AWS is very good. When I need something, they reach out to me fast.
How was the initial setup?
The initial setup was straightforward. The complexity of the setup will depend on the number of services e.g. it's something that involves a lot of services, it could get complex, but for a complex setup, you could use things like transformation or Terraform because they will enable you to use infrastructure as a code to make it easier. There's a lot of things to configure.
What's my experience with pricing, setup cost, and licensing?
Licensing of this solution is paid on a yearly basis.
Which other solutions did I evaluate?
I evaluated Microsoft Azure.
What other advice do I have?
This was deployed on the cloud. I don't remember which version because I didn't deploy it. I was not the person running the project of implementing AWS, but I know the client used it, but I don't know which version.
It's not so difficult to use because there's a lot of tutorials.
I'm not completely sure about the number of AWS users in our organization. We have a partnership with them so we have some accounts, but we don't completely have our load on AWS. We are mostly on Azure. Our main server is on Azure. On AWS, we mostly have some internal projects and services, but most of the main load is on Azure.
We have a small workload on AWS. Sometimes we use it to deploy some of our best projects. We use it on some internal projects. It's a random thing so it could be 1,000 users or 50 users. I'll say approximately 200 to 500 users.
We don't require too many people for deploying this solution because our projects are proof of concepts. Up to ten people from different departments would be needed for deployment if it's a business requirement e.g. people from Approvals and Projects, etc.
As for increasing AWS usage, the organization sometimes thinks of moving some of the load to AWS because of good pricing, because currently, our main streams are on Azure, but it's not a sure thing.
I'm unsure if there's any additional cost aside from the need to pay the license annually because I don't directly manage it.
My advice to organizations looking into implementing AWS, especially if they're going to use it on a big scale, is to take advantage of AWS' organization model to make integration with their policies easier. It will also make administration easier for the different accounts, departments, and structure of the organizations thinking of moving to AWS.
I would rate this solution a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
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.
814,649 professionals have used our research since 2012.
Flexible, scales well, and offers good stability
Pros and Cons
- "The solution scales very nicely."
- "The pricing is something you have to watch. You really have to constantly optimize your costs for instances and things like that. That can become a job in itself to manage just from a budgeting standpoint."
What is our primary use case?
Customers can use it for the web-based management of the product. We also store and retrieve data for their network connections. Also, we use the AI/ML portion called SageMaker to calibrate the algorithms and basically drive automation into the customer's use case. Typically our use cases are in hotels, public transportation, convention centers - anywhere where you are sharing internet connections. For example, hotels, conventions centers - anything where you might have people jockeying for a shared internet connection with possible oversubscription or network congestion. We also have enterprise Work-From-Home users due to the pandemic and they need to continue to provide access to those remotely into their own data center, corporate network, and public cloud.
How has it helped my organization?
Flexible fast way to bring up servers and network infrastructure with variable costs.
What is most valuable?
We use the AI/ML Sagemaker to help us build models.
We use several feature services on AWS, including Lambda, S3 database, RDS database, Alexa Voice Services and Cognito Gateway. They are all excellent in terms of offering great functionality.
They're pretty good about taking customer feedback and are generally able to productize the requested feature.
The initial setup is straightforward, especially if using Lightsail to start.
The solution scales very nicely.
The stability is good with a large number of Availability Zones WW.
Technical support is helpful and responsive but you must pay for a tiered support plan to ensure response.
What needs improvement?
The pricing is something you have to watch. You really have to constantly optimize your costs for instance, storage, IP's and things like that. That can become a job in itself to manage just from a budgeting standpoint if you are a moderate to heavy user. However, that's true for Azure or GCP as well.
If they did more automation on alerting you to cheaper pricing or automated volume pricing based on time/use or even porting you on to on-demand instances automatically, that would be kind of cool. That's something that I haven't seen yet. They could just automatically optimize for your workflow and put you onto a lower-priced instance to save you money. you Maybe allow you to pick an economy setting, or a performance setting, by time of day etc. something like that. That would be great. Then you don't have to think about it as much as you do in the current iteration.
It would be interesting to have a cost optimized accounting service so that they would come in and help remediate and give suggestions on how to cut costs. I know it's probably antithetical to their bottom line, but that said, obviously, if you take the high road there, you're going to probably keep people, and keep people from switching for lower costs. A lot of times, they can architect a better solution or a similar solution for lower cost and that would lead to customer retention--or maybe a longer term retention discount if youve stayed with them for awhile. That would be helpful if they had that. They have solutions architects, to consult however, they're usually just trying to design the best technical solution as opposed to the most cost-optimized solution.
For how long have I used the solution?
We've been using the solution for about four years at this point.
What do I think about the stability of the solution?
Services are pretty good stability-wise. They've got great redundancy. The one thing I would tweak them is when you're within the region or zone, they make it more difficult for you to do redundant zones, without carrying the IP addresses over seamlessly. That is a little bit of a sticking point, so you could have remote redundancy with the addressing there with it even outside of the AZ's. That would be a lot easier than having to go through the programming of it.
What do I think about the scalability of the solution?
The scalability is great. You can go from one small instance to GPU, very powerful instances, clusters. There is not any problem with scaling if you can afford it. If you've got the volume, you certainly can scale.
We have maybe a dozen or so customers that will use the product and then access the UI and the management system through the cloud. Then, of course, as developers, we have about 10 to 25 employees that have to use it to varying degrees to support the customers and do development.
How are customer service and technical support?
I like the tech support. It varies by level in that you've got to pay more to get the immediate response time. Generally, I'd say it's pretty good. Literally phone rings minutes after you log a trouble ticket. They're usually pretty good about escalations and helping. Out of AWS, Azure, and GCP, I'd give them the number two ranking. Azure has good support, however, it's expensive. GCP probably is number three I'd say, of the top three.
Which solution did I use previously and why did I switch?
We also occasionally use the Google Cloud Platform and Azure, although we tend to use AWS the most. GCP is a little bit cheaper overall, however, then you've got the cost of management that is typically a person so you do need to invest in that.
We started with Amazon and we've pretty much stayed with them. We've switched to Google and done some work on Azure that was customer driven, however, pretty much our prime public cloud has been AWS.
How was the initial setup?
The initial setup is not overly complex. It's pretty straightforward.
It's pretty easy to get started. However, you do have to make an investment and learn the different cloud platform's nomenclature. Most of our guys now are cloud practitioners and architects now that they've taken the training. We had to bite the bullet even though we've been users for four years. There is an investment that you have to make on the OPEX side. That's the case for any of the public clouds. Although once you know one, you can pretty much pick up the other ones pretty quickly.
What about the implementation team?
In-house
What's my experience with pricing, setup cost, and licensing?
Have to watch price/billing creep, but there are tools to watch and monitor your usage and billing.
Which other solutions did I evaluate?
Azure. GCP
What other advice do I have?
We're a software development group building specialty LAN/WAN optimization solutions, so we don't use a lot of canned products per se.
We do tend to sue reasonably new software versions of the OS...whatever is the latest LTS selections.
If you already have your workload ready, that's helpful, as you can actually trial it under a free tier and then see what the cost is, and extrapolate what the ongoing cost is. In the end, that's what gets you. Being able to do some benchmark testing on how much it's going to cost for your particular workflow across the three public clouds is definitely something you probably want to do. Especially if you're going to scale, as, obviously, it can suddenly creep up to not just tens or hundreds of dollars a month, but thousands a month, depending upon what you're doing. I definitely would recommend doing some reference testing of your workflows before deciding on a solution.
I'd rate the solution at an eight out of ten. They're pretty solid. You've got all the services that you can imagine, and then some. There's a very broad breadth of products and services. We haven't had too many SLA issues for recovery or downtime. Maybe we've just been lucky or good so far...
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.
AGM, Enterprise Solutions at Omgea Exim Ltd
A highly scalable solution that helps organizations to move their applications to a containerized platform
Pros and Cons
- "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."
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Amazon AWS for about six years.
What do I think about the stability of the solution?
I rate Amazon AWS an eight out of ten for stability.
What do I think about the scalability of the solution?
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.
How are customer service and support?
The solution’s technical support is good.
How would you rate customer service and support?
Positive
How was the initial setup?
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.
What about the implementation team?
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.
What's my experience with pricing, setup cost, and licensing?
The pricing of Amazon AWS is high compared to any other cloud provider.
What other advice do I have?
Amazon AWS was deployed on the cloud in my organization.
Overall, I rate Amazon AWS an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Engineer at a tech services company with 51-200 employees
Great EC2, simple storage, and good security
Pros and Cons
- "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."
- "It could be made cheaper. I know we spend a lot of money each month on AWS."
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using AWS since the company was founded in 2017 - about five years.
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.
Consulting Chief Information Officer at Tippingedge
Good performance, but it can be costly, and the setup could be simplified
Pros and Cons
- "In general, Amazon's performance is good."
- "When I try to enter the multi-cloud, they provide very poor support. Support is a concern with Amazon."
What is our primary use case?
We have applications that are running on the PaaS platforms.
In the healthcare environment, we use Amazon AWS to run healthcare and hospitalization applications.
The end-user is largely unaware of how the backend works, so some of the services are provided by Amazon. So, where we are, some of the applications have been running since the beginning, and we have been using them. And some of the services are required by the packages we are running, so they use Amazon PaaS as a service.
What is most valuable?
In general, Amazon's performance is good.
What needs improvement?
When I try to enter the multi-cloud, they provide very poor support. Support is a concern with Amazon.
For how long have I used the solution?
I have been using Amazon AWS for a few years.
What do I think about the stability of the solution?
Amazon AWS is a stable solution, it is far more stable than some others.
What do I think about the scalability of the solution?
Amazon AWS is scalable, depending on the platforms and services that are used.
In our company, we have 50,000 employees who use this solution.
We intend to increase our users based on how the new releases go, and if the economics work out better than Google and Microsoft, we will definitely look to Amazon because Amazon can be extremely competitive at times.
How are customer service and support?
It should be faster. Unlike Google's and Microsoft's support, Amazon's support should be faster.
Which solution did I use previously and why did I switch?
We have used other PaaS clouds previously.
The hospitals were available on Amazon. We have certain hospitals that were part of the group when it first started, but there are a lot of hospitals that are in the process of being acquired. Once the setup is acquired, it is extremely difficult and time-consuming for them to bring it through one enterprise architecture. Now, it is not necessary to have services from only one cloud service provider; instead, we can have services from multiple providers, and we are working to integrate the multi-cloud.
How was the initial setup?
Essentially, you must design and optimize the architecture. It is not the most straightforward process to install. You must first design your architecture and then optimize it in relation to the services.
Earlier I used to work there, and we had a real skill shortage because we needed people who could understand and work in the cloud. When we developed centers of excellence and core competencies, people were required to work across multiple platforms, which is a challenge that we are currently working on. As a result, the real challenge now is for a team to have a multi-cloud. Now, if we can develop this talent organically, that will be fantastic. We'll spread out the support team we require. Another initiative that is being worked on is automation, automating scripts, and new technologies, which are assisting us greatly with serverless and cloud computing.
What's my experience with pricing, setup cost, and licensing?
It can get quite pricey at times. Because of the patterns we're attempting to use, it becomes very expensive. Where we can save money by using Google components or Microsoft components, we can go much cheaper.
You must pay a licensing fee, which is based on the usage.
Essentially, it is determined by how we use the services. There are sometimes are a soft service, sometimes we pay yearly, and sometimes we pay as we use it.
What other advice do I have?
Yes, I would recommend this solution. If we compare the three, I would rank Google first, Microsoft second, Amazon third, and the rest would follow.
I would rate Amazon AWS a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CTO & Product at a financial services firm with 11-50 employees
Easy to use with a good performance and decent technical support
Pros and Cons
- "Technical support has been great."
- "I'd like the solution to be more plug-and-play."
What is our primary use case?
This is a service solution for architecture. It's a cloud solution basically for anything you need.
What is most valuable?
I'm happy with the solution.
It's very easy to use.
The stability and performance are great.
The scalability of the product is great.
Technical support has been great.
What needs improvement?
I'd like the solution to be more plug-and-play.
For how long have I used the solution?
I've been using the solution for about ten years at this point. It's been a while.
What do I think about the stability of the solution?
The stability is very good. The performance is great and it's quite reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
AWS scales well. It's not a problem to expand it.
We have 100 users using the solution at this time. They are end-users and clients.
Our plan right now is to increase usage in the future.
How are customer service and support?
I've used technical support in the past. I don't have any complaints about their services. They are quite good overall.
Which solution did I use previously and why did I switch?
We did use a different solution, however, the company decided to move to AWS.
How was the initial setup?
There's no installation involved. It's a very straightforward product.
As there is no installation process, you don't need a technical team and you don't have to do any maintenance.
What's my experience with pricing, setup cost, and licensing?
There is a license fee that you need to pay. There are flexible payment options. For example, you can pay monthly if you want to.
What other advice do I have?
I do recommendations for the development of cloud solutions.
I would rate the solution at 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: I am a real user, and this review is based on my own experience and opinions.
Senior Product Manager at a tech services company with 501-1,000 employees
You can scale it up and down as you need, which is much easier than adding and provisioning new servers
Pros and Cons
- "The environment is a rich playground, and if you tried to do the same things on-premises that you do on AWS, it would be a lot more challenging to execute. You can open up a virtual machine on AWS, run some experiments, and be done with it. It's much easier than buying new servers, provisioning them, etc"
- "You'll probably experience some sticker shock with AWS. You attempt to understand the cost, but you don't realize what you're paying until you get your first bill. I don't know if Amazon does that on purpose, but costs can get out of control quickly if you don't have someone who specializes in AWS cost management."
How has it helped my organization?
The most valuable feature of AWS is that you can scale it up and down as you need. The environment is a rich playground, and if you tried to do the same things on-premises that you do on AWS, it would be a lot more challenging to execute. You can open up a virtual machine on AWS, run some experiments, and be done with it. It's much easier than buying new servers, provisioning them, etc.
For how long have I used the solution?
Most of the companies that I've worked for deal with AWS.
What do I think about the stability of the solution?
I don't know how many servers they say they have, but AWS is a highly reliable platform. I'm sure they've had outages because it's all over the news when they do, but it's stable overall.
What do I think about the scalability of the solution?
Cloud solutions like AWS are supposed to have near-infinite scalable. That's the point. You can just keep going and make them as big or small as you need.
What's my experience with pricing, setup cost, and licensing?
AWS is like all the other cloud providers. They're all like vacuum salesmen, where they come in, and they say, "Do you want to buy this hose or this vacuum?" And you're like, "Yeah, it's not that expensive. It's a hose." And then they say, "How about these extra bags?" And you're like, "Okay. I'll buy the bags. It's not that much." Then, at the end of the day, you've bought an entire vacuum store's worth of stuff. You don't know upfront what it will cost, but they have cost calculators and other things like that.
You'll probably experience some sticker shock with AWS. You attempt to understand the cost, but you don't realize what you're paying until you get your first bill. I don't know if Amazon does that on purpose, but costs can get out of control quickly if you don't have someone who specializes in AWS cost management.
I don't even know how many microservices they have now. It seems like hundreds, so what do you do. What would you tell them to do with Aurora compared to their other stuff? There's just so much there that it's tough to get a comprehensive understanding of what you're getting into with AWS. And that's just the nature of AWS. It's a giant ecosystem. Azure is the same. I'm not familiar with GCP, but I'm sure it's the same. They do their best to make it as clean as possible from a sales perspective, but the AWS sticker shock is real.
I'm not sure about the exact costs. When I used to do stuff with Commvault and stuff, I knew the ingress and egress fees and the data cost for storage on AWS, but that was a long time ago.
What other advice do I have?
I guess I would rate Amazon AWS eight out of 10. AWS works as advertised, but they're expensive if you don't know what you're doing. I'm not sure if I can knock them for not being transparent about pricing. Cloud costs are challenging. There's an entire industry popping up for managing cloud costs with consultants who can tell you how to get the most out of your AWS allocation.
I don't have a lot of advice. If you're planning to implement a cloud solution, just pick one. I mean, if you're a Microsoft shop, it probably makes more sense to go Azure. If you're not, then I would recommend AWS. It depends on what you're looking to get out of it.
There are references, architectures, case studies, and a million other things that would off better advice on whether to go with AWS or not. But if you're looking to go to the cloud, AWS is as good as everybody else. AWS is probably better than Azure and GCP, but that's a tricky thing to pin down. It depends on what your goals and requirements are. My best advice is to evaluate your goals before making a decision.
I hope that people take what I say about AWS with a massive grain of salt because it's like asking an ant about an elephant. What's an ant going to know about an elephant? It's just too big for any one person to know.
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.
Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
Microsoft Azure
Oracle Cloud Infrastructure (OCI)
Red Hat OpenShift
Akamai Connected Cloud (Linode)
Mendix
VMware Tanzu Platform
Google Cloud
SAP Cloud Platform
Salesforce Platform
Pivotal Cloud Foundry
Dell ECS
Google Firebase
Alibaba Cloud
IBM Public Cloud
SAP S4HANA on AWS
Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Gartner's Magic Quadrant for IaaS maintains Amazon Web Service at the top of the Leaders quadrant. Do you agree?
- PaaS solutions: Areas for improvement?
- Rackspace, Dimension Data, and others that were in last year's Challenger quadrant became Niche Players: Agree/ Disagree
- Does anybody have experience negotiating the terms and conditions with AWS?
- Which would you prefer - Amazon AWS or IBM Public Cloud?
- Do you have an Amazon AWS certification, and do you think it is important to earn one?
- Would you recommend Amazon AWS to cloud computing beginners?
- Which Amazon AWS features and services do you use the most often and why?
- How does Amazon compare to alternative cloud solutions?
- What are some smart ways to streamline AWS data transfer costs?
I recently started using Amazon AWS for my business and I have to say I'm impressed! The platform is incredibly user-friendly, even for someone who isn't very tech-savvy like myself. The range of services and features available is quite extensive, and I found everything I needed to build and run my application.
One of the things I appreciated the most about AWS is the level of security they provide. The platform is built with security in mind, and they offer a variety of tools and features to keep my data and applications safe. I also liked the pay-as-you-go pricing model, which meant I only paid for what I used, and I didn't have to worry about any hidden fees or unexpected costs.
Overall, I would definitely recommend Amazon AWS to anyone looking for a reliable and secure cloud computing platform. The level of support and resources available is top-notch, and the platform has been a game-changer for my business.