We advise our clients on using AWS services. It has many applications; in health care with regard to patient medical history. Some use it for hosting, SAP and V-ware. Those are the most common uses for our clients. We are resellers and I'm the operations director.
Regional Business Manager - North Latam - Public Sector - Amazon Web Services (AWS) at a tech services company with 10,001+ employees
Offers a very valuable machine learning service
Pros and Cons
- "Machine learning is a valuable feature."
- "The solution could be more user-friendly."
What is our primary use case?
What is most valuable?
I think machine learning is one of the most used and most valuable services, especially in scientific research. The solution is evolving all the time.
What needs improvement?
Some of the services are hard to use so I think a more user-friendly interface would be helpful.
For how long have I used the solution?
Buyer's Guide
Amazon AWS
February 2025

Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is very scalable.
How are customer service and support?
Amazon offers different support plans. We have enterprise support and they generally get back to us within half an hour. The escalation process is very fast, because they know that there is a critical platform involved. They generally offer a high level of support.
How was the initial setup?
The initial setup is not too complex but it's not straightforward either, somewhere in the middle. In terms of deployment time, it can be anywhere between a few minutes and a week, depending on what you need.
What other advice do I have?
Training is critical before implementing the solution. There are very good AWS certifications like the certified practitioner, and there's a lot of free training on the AWS webpage that customers can use. Most of the training is hands-on so you can experience how things would be done in a work environment. AWS recently deployed 100 free courses on amazon.com to help people better understand their products. I would recommend looking at those.
I rate this solution nine out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer:
AGM, Enterprise Solutions at Omgea Exim Ltd
Scalable, robust, and offers many unique services
Pros and Cons
- "They provide cutting-edge features compared to other cloud vendors."
- "Some extensions are better than others."
What is our primary use case?
The solution is useful in many ways. If you want to invest in on-prem infrastructure, it is going to be a huge cost. If you could add auto-scaling features and load balancing features on AWS Cloud, the e-commerce site can use the autoscale feature to handle any traffic threshold or additional workloads. I have two, three customers who are using this feature and they are getting benefits out of it.
What is most valuable?
Amazon, in terms of cloud infrastructure, is really robust.
The product is scalable.
They provide cutting-edge features compared to other cloud vendors.
They offer many services that are unique to AWS.
The availability is a good feature. They have certain criteria. For global virtualization, if you want to scale and operate across the world, AWS can provide the infrastructure without limiting the performance. They have those provisions such as availability.
In terms of latency and other things, AWS is great.
The online knowledge base is very helpful and has a vast amount of information for users.
What needs improvement?
The solution could always have better performance.
Some extensions are better than others.
We'd like it if the solution was more secure.
For how long have I used the solution?
I've been dealing with the solution for over three years. It's been a while.
What do I think about the stability of the solution?
The solution is robust and stable. The solution is reliable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
The solution is highly scalable, especially for the storage part. They have storage called S3 Object Store, which is virtually unlimited. You can scale it to an unlimited amount. It's great.
How are customer service and technical support?
For AWS, if I compare it to Huawei, Huawei support, Huawei is better compared to AWS, however, AWS is better compared to Google and Oracle or SAP and all of those other clouds. Due to the fact that AWS has a very good knowledge base, you can easily find answers to any issue you might have.
Which solution did I use previously and why did I switch?
I've also used similar solutions such as Oracle and Azure. I've also dealt with Huawei.
How was the initial setup?
As a cloud-based solution, there isn't really an installation process.
What's my experience with pricing, setup cost, and licensing?
While some clients will take a monthly subscription, we tend to do an SLA reseller with them for a one-year or three-year contract.
What other advice do I have?
I'm a reseller.
As a cloud-based solution, we're always on the latest version. We don't have to manually update it.
I'd rate the solution at a ten out of ten. Even compared to other solutions, such as Oracle and Azure, it is much better.
I've been a specialist for AWS for installation, however, I recommend solutions based on the company's requirements. However, it will help them in many ways.
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:
Buyer's Guide
Amazon AWS
February 2025

Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
IT Architect at Orbis Data
A scalable and stable solution
Pros and Cons
- "I am very impressed by the solution's stability."
- "The response time of technical support could be better."
What is our primary use case?
In my role as an IT architect, I design solutions for many clients. We use the solution in mobile applications with a back-end solution
What needs improvement?
The response time of technical support could be better. It is not so good. While this can likely be attributed to our lack of a premium support contract, they should still show more consideration in their response time towards first time clients.
Moreover, as things grow, the solution will need the scalability of Amazon services for it to be very secure. More scalability will be essential. It will be important for us to incorporate certain architecture-based ideas or configurations of the signature that would need to be included in our solutions or designs.
As an example, we developed a mobile application that will reach 10,000 users of Amazon services within its first year. The following year, it is projected to reach around 100,000 users.
For how long have I used the solution?
I have been using Amazon AWS during the last 12 months.
What do I think about the stability of the solution?
I am very impressed by the solution's stability.
What do I think about the scalability of the solution?
The scalability is very good, although having good security will require that its growth be in line with that of Amazon service.
How are customer service and technical support?
Technical support is not so good.
How was the initial setup?
Use of the four quarters service posed a problem for us during the initial setup. The setup of the initial quarters of service should be more transparent and clear to the user. Certain limits should be set up to match the varying needs of the users.
What's my experience with pricing, setup cost, and licensing?
There are no additional costs beyond the standard licensing fees.
What other advice do I have?
I feel the solution has been working very well.
We have worked with around eight companies over the past year involving a variety of solutions. For some of these we implemented solutions that will be utilized by a large clientele.
My role is that of an integrator. Editors and designers are other roles. As of now, we do not have a partner relationship with Amazon.
I rate Amazon AWS as a nine 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: Integrator
Head of Data Projects at Cognitivo
An on-demand cloud computing platform that has a lot of specific solutions for different use cases
Pros and Cons
- "I like that the products are specific and objective. We can resolve a problem using a simple configuration. It's so easy to implement a solution and solve a problem using AWS solutions. AWS has a lot of specific solutions for different use cases. I think that this is the most important thing that made us consider using AWS."
- "It would be better if there was a way to see which components were still on. We have some situations where I forget that some components are turned on. We forget some components are on, and we only see that these components are on when we see the bill at the end of the month. It would also be better if AWS had specialized firewalls or integrations with leading products. For example, a specialized firewall with content filtering. We were looking for some firewall tools, and we saw that AWS doesn't have any specialized firewall tools in its services portfolio. So, we are looking for other tools like FortKnox, Forcepoint, and Check Point because we didn't find the solutions in AWS services."
What is our primary use case?
We usually use Amazon AWS to implement data lake solutions. We extract data from an AWS project that we implement, or we extract data from databases and centralize them with AWS components in AWS services. So, we create an infrastructure for our clients to consume their data. I like the components we use, like Amazon DMS or Database Migration Services, F3, and Amazon Athena. I think that these are the main components or the main services that we use.
What is most valuable?
I like that the products are specific and objective. We can resolve a problem using a simple configuration. It's so easy to implement a solution and solve a problem using AWS solutions. AWS has a lot of specific solutions for different use cases. I think that this is the most important thing that made us consider using AWS.
What needs improvement?
It would be better if there was a way to see which components were still on. We have some situations where I forget that some components are turned on. We forget some components are on, and we only see that these components are on when we see the bill at the end of the month.
It would also be better if AWS had specialized firewalls or integrations with leading products. For example, a specialized firewall with content filtering. We were looking for some firewall tools, and we saw that AWS doesn't have any specialized firewall tools in its services portfolio. So, we are looking for other tools like FortKnox, Forcepoint, and Check Point because we didn't find the solutions in AWS services.
For how long have I used the solution?
I have been using Amazon AWS for about three years.
What other advice do I have?
On a scale from one to ten, I would give Amazon AWS a nine.
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.
CTO at a hospitality company with 501-1,000 employees
Stable with great performance and good pricing
Pros and Cons
- "The performance of AWS is excellent."
- "The overall convenience and the ease to use could be improved."
What is our primary use case?
We primarily use the solution for the infrastructure. We use it specifically for hosting the infrastructure and hosting our analytics database.
What is most valuable?
So far, the stability is the solution's most valuable aspect. It's one of its great selling features.
The performance of AWS is excellent.
The cost-effectiveness is something we appreciate. It isn't too expensive for us to leverage AWS.
What needs improvement?
The overall convenience and the ease to use could be improved. Right now, for example, we still have an integrator that helps us. They help us do the so-called hand-holding to get us started. Once we start, we can train up staff and we can manage most of the operations ourselves. It's just that first little bit that's difficult to handle alone.
For how long have I used the solution?
We've been using the solution for a few years at this point.
What do I think about the stability of the solution?
The stability of AWS is excellent. We don't have to worry about it crashing or freezing. There aren't bugs or glitches to contend with. It's reliable and we've enjoyed its stability thus far.
What do I think about the scalability of the solution?
The scalability of the product is very, very good. It's one of the great benefits of the cloud. You don't really have to worry about hitting a wall. It can expand pretty well as much as you need it to.
We have about 30 or so people on the solution right now. They are mostly our analytical team and some business users.
We have plans to continue usage and we may also increase usage in the future.
How are customer service and technical support?
Our team has used technical support in the past. I haven't myself, personally, however, my team called them for technical questions. We tend to use either AWS or our system integrator when it comes to answering some troubleshooting issues.
The support could be better. It's my understanding that they need to take some sort of certification, and that there is a bit of a learning curve. They're not bad, however, as I mentioned, they could be more proficient. While some seem to be certified, others need to polish their skillsets.
Which solution did I use previously and why did I switch?
We did use another solution previously. We used Horizon before. We also use some other data pipeline, however, they were more of a niche market cloud provider, unlike Amazon, which is more widespread and has a broader scope.
How was the initial setup?
We are using it on the cloud basis. We don't have any integration on-premises. We found the installation, in that sense, somewhat easy, although there were some moving parts that we still needed a bit of help with.
What about the implementation team?
We had an integrator help us a bit. They did some hand-holding to make sure everything got up and running properly.
What's my experience with pricing, setup cost, and licensing?
The pricing of the solution is quite good. It's very reasonable and very affordable.
That said, I don't deal with billing and licensing directly and therefore don't have the exact numbers in relation to how much we pay.
What other advice do I have?
We're using the latest version of the solution. The cloud is instantaneously upgrading us to the latest version.
I'd recommend the solution to other organizations. We've been pretty happy with the product so far.
Overall, I would rate it at an eight out of ten. If it offered better support and had a more user-friendly setup I'd likely rate it higher.
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.
Technology Competency and Solution Head at LearningMate
Helpful support, stable, and the integration is good
Pros and Cons
- "The technical support is good."
- "They should have a better big data stack."
What is our primary use case?
We have been using AWS for our own product. We are not direct users. Rather, our customers are using our product, which is hosted on AWS.
What needs improvement?
The cost should be reduced.
They should have a better big data stack.
For how long have I used the solution?
We have been dealing with Amazon AWS for the last six years.
What do I think about the stability of the solution?
This product is stable and we plan to continue selling it in the future. All of our products are tightly integrated with AWS.
What do I think about the scalability of the solution?
AWS is a scalable platform.
How are customer service and technical support?
The technical support is good.
How was the initial setup?
There is no installation for AWS, as it is a cloud product.
What's my experience with pricing, setup cost, and licensing?
AWS is expensive and the cost should be reduced.
What other advice do I have?
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: My company has a business relationship with this vendor other than being a customer: Reseller
Cloud Expert | DevOps | Oracle Consultant at confidential
It provides full IaaS and PaaS for any company with a perfect price
What is our primary use case?
Hands-on experience with more than five implementation projects, working on different projects that are related to cloud with different vendors. AWS features exist to make your life easier.
How has it helped my organization?
AWS provides full IaaS and PaaS for any company with a perfect price, with features that exist in this vendor I don't see in any other vendor.
What is most valuable?
- Lambda.
- Alex development edge.
- CloudFormation.
All of these features I've used heavily provide the best solution for any client.
What needs improvement?
- I would like to see Lambda (code storage management), which means being able to increase our code storage limit through support.
- Another example which is Simple Queue Service (SQS) event for Lambda: to be able to see support for SQS message events with Lambda.
For how long have I used the solution?
More than five years.
Which solution did I use previously and why did I switch?
Regarding to my work i am dealing with different cloud vendor all the time, but i never switch one solution to another.
What's my experience with pricing, setup cost, and licensing?
AWS pricing Reasonable & affordable by any business size, Small, Medium or large.
Which other solutions did I evaluate?
None
What other advice do I have?
None
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Independent Analyst and Advisory Consultant at Server StorageIO - www.storageio.com
Cloud conversations: Gaining cloud confidence from insights into AWS outages
PART I
In case you missed it, there were some public cloud outages during the recent Christmas 2012-holiday season. One incident involved Microsoft Xbox (view the Microsoft Azure status dashboard here) users were impacted, and the other was another Amazon Web Services (AWS) incident. Microsoft and AWS are not alone, most if not all cloud services have had some type of incident and have gone on to improve from those outages. Google has had issues with different applications and services including some in December 2012 along with a Gmail incident that received covered back in 2011.
For those interested, here is a link to the AWS status dashboard and a link to the AWS December 24 2012 incident postmortem. In the case of the recent AWS incident which affected users such as Netflix, the incident (read the AWS postmortem and Netflix postmortem) was tied to a human error. This is not to say AWS has more outages or incidents vs. others including Microsoft, it just seems that we hear more about AWS when things happen compared to others. That could be due to AWS size and arguably market leading status, diversity of services and scale at which some of their clients are using them.
Btw, if you were not aware, Microsoft Azure is more than just about supporting SQLserver, Exchange, SharePoint or Office, it is also an IaaS layer for running virtual machines such as Hyper-V, as well as a storage target for storing data. You can use Microsoft Azure storage services as a target for backing up or archiving or as general storage, similar to using AWS S3 or Rackspace Cloud files or other services. Some backup and archiving AaaS and SaaS providers including Evault partner with Microsoft Azure as a storage repository target.
When reading some of the coverage of these recent cloud incidents, I am not sure if I am more amazed by some of the marketing cloud washing, or the cloud bashing and uniformed reporting or lack of research and insight. Then again, if someone repeats a myth often enough for others to hear and repeat, as it gets amplified, the myth may assume status of reality. After all, you may know the expression that if it is on the internet then it must be true?
Have AWS and public cloud services become a lightning rod for when things go wrong?
Here is some coverage of various cloud incidents:
Huffington post coverage of February 2011 Google Gmail incident
Microsoft Azure coverage by Allthingsd.com
Neowin.net covering Microsoft Xbox incident
Google’s Gmail blog coverage of Gmail outage
Forbes article Amazon AWS Takes Down Netflix on Christmas Eve
Over at Performance Critical Apps they assert the AWS incident was Netflix fault
From The Virtualization Practice: Amazon Ruining Public Cloud Computing?
Here is Netflix architect Adrian Cockcroft discussing the recent incident
From StorageIOblog Amazon Web Services (AWS) and the Netflix Fix?
From CRN, here are some cloud service availability status via Nasuni
The above are a small sampling of different stories, articles, columns, blogs, perspectives about cloud services outages or other incidents. Assuming the services are available, you can Google or Bing many others along with reading postmortems to gain insight into what happened, the cause, effect and how to prevent in the future.
Do these recent incidents show a trend of increased cloud outages? Alternatively, do they say that the cloud services are being used more and on a larger basis, thus the impacts become more known?
Perhaps it is a mix of the above, and like when a magnetic storage tape gets lost or stolen, it makes for good news or copy, something to write about. Granted there are fewer tapes actually lost than in the past, and far fewer vs. lost or stolen laptops and other devices with data on them. There are probably other reasons such as the lightning rod effect given how much industry hype around clouds that when something does happen, the cynics or foes come out in force, sometimes with FUD.
Similar to traditional hardware or software based product vendors, some service providers have even tried to convince me that they have never had an incident, lost or corrupted or compromised any data, yeah, right. Candidly, I put more credibility and confidence in a vendor or solution provider who tells me that they have had incidents and taken steps to prevent them from recurring. Granted those steps might be made public while others might be under NDA, at least they are learning and implementing improvements.
As part of gaining insights, here are some links to AWS, Google, Microsoft Azure and other service status dashboards where you can view current and past situations.
AWS service status dashboard
Bluehost server status dashboard
Google App status dashboard
HP cloud service status console (requires login)
Microsoft Azure service status dashboard
Microsoft Xbox service status dashboard
Rackspace service status dashboards
PART II
There is good information, insight and lessons to be learned from cloud outages and other incidents.
Sorry cynics no that does not mean an end to clouds, as they are here to stay. However when and where to use them, along with what best practices, how to be ready and configure for use are part of the discussion. This means that clouds may not be for everybody or all applications, or at least today. For those who are into clouds for the long haul (either all in or partially) including current skeptics, there are many lessons to be learned and leveraged.
In order to gain confidence in clouds, some questions that I routinely am asked include are clouds more or less reliable than what you are doing? Depends on what you are doing, and how you will be using the cloud services. If you are applying HA and other BC or resiliency best practices, you may be able to configure and isolate from the more common situations. On the other hand, if you are simply using the cloud services as a low-cost alternative selecting the lowest price and service class (SLAs and SLOs), you might get what you paid for. Thus, clouds are a shared responsibility, the service provider has things they need to do, and the user or person designing how the service will be used have some decisions making responsibilities.
Keep in mind that high availability (HA), resiliency, business continuance (BC) along with disaster recovery (DR) are the sum of several pieces. This includes people, best practices, processes including change management, good design eliminating points of failure and isolating or containing faults, along with how the components or technology used (e.g. hardware, software, networks, services, tools). Good technology used in goods ways can be part of a highly resilient flexible and scalable data infrastructure. Good technology used in the wrong ways may not leverage the solutions to their full potential.
While it is easy to focus on the physical technologies (servers, storage, networks, software, facilities), many of the cloud services incidents or outages have involved people, process and best practices so those need to be considered.
These incidents or outages bring awareness, a level set, that this is still early in the cloud evolution lifecycle and to move beyond seeing clouds as just a way to cut cost, and seeing the importance and value HA, resiliency, BC and DR. This means learning from mistakes, taking action to correct or fix errors, find and cut points of failure are part of a technology maturing or the use of it. These all tie into having services with service level agreements (SLAs) with service level objectives (SLOs) for availability, reliability, durability, accessibility, performance and security among others to protect against mayhem or other things that can and do happen.
The reason I mentioned earlier that AWS had another incident is that like their peers or competitors who have incidents in the past, AWS appears to be going through some growing, maturing, evolution related activities. During summer 2012 there was an AWS incident that affected Netflix (read more here: AWS and the Netflix Fix?). It should also be noted that there were earlier AWS outages where Netflix (read about Netflix architecture here) leveraged resiliency designs to try and prevent mayhem when others were impacted.
Is AWS a lightning rod for things to happen, a point of attraction for Mayhem and others?
Granted given their size, scope of services and how being used on a global basis AWS is blazing new territory and experiences, similar to what other information services delivery platforms did in the past. What I mean is that while taken for granted today, open systems Unix, Linux, Windows-based along with client-server, midrange or distributed systems, not to mention mainframe hardware, software, networks, processes, procedures, best practices all went through growing pains.
There are a couple of interesting threads going on over in various LinkedIn Groups based on some reporters stories including on speculation of what happened, followed with some good discussions of what actually happened and how to prevent recurrence of them in the future.
Over in the Cloud Computing, SaaS & Virtualization group forum, this thread is based on a Forbes article (Amazon AWS Takes Down Netflix on Christmas Eve) and involves conversations about SLAs, best practices, HA and related themes. Have a look at the story the thread is based on and some of the assertions being made, and ensuing discussions.
Also over at LinkedIn, in the Cloud Hosting & Service Providers group forum, this thread is based on a story titled Why Netflix’ Christmas Eve Crash Was Its Own Fault with a good discussion on clouds, HA, BC, DR, resiliency and related themes.
Over at the Virtualization Practice, there is a piece titled Is Amazon Ruining Public Cloud Computing? with comments from me and Adrian Cockcroft (@Adrianco) a Netflix Architect (you can read his blog here). You can also view some presentations about the Netflix architecture here.
What this all means
Saying you get what you pay for would be too easy and perhaps not applicable.
There are good services free, or low-cost, just like good free content and other things, however vice versa, just because something costs more, does not make it better.
Otoh, there are services that charge a premium however may have no better if not worse reliability, same with content for fee or perceived value that is no better than what you get free.
Additional related material
Cloud conversations: confidence, certainty and confidentiality
Only you can prevent cloud data loss (shared responsibility)
The blame game: Does cloud storage result in data loss?
Amazon Web Services (AWS) and the Netflix Fix?
Cloud conversations: AWS Government Cloud (GovCloud)
Everything Is Not Equal in the Data center
Cloud and Virtual Data Storage Networking (CRC) – Intel Recommended Reading List
Some closing thoughts:
Clouds are real and can be used safely; however, they are a shared responsibility.
Only you can prevent cloud data loss, which means do your homework, be ready.
If something can go wrong, it probably will, particularly if humans are involved.
Prepare for the unexpected and clarify assumptions vs. realities of service capabilities.
Leverage fault isolation and containment to prevent rolling or spreading disasters.
Look at cloud services beyond lowest cost or for cost avoidance.
What is your organizations culture for learning from mistakes vs. fixing blame?
Ask yourself if you, your applications and organization are ready for clouds.
Ask your cloud providers if they are ready for you and your applications.
Identify what your cloud concerns are to decide what can be done about them.
Do a proof of concept to decide what types of clouds and services are best for you.
Do not be scared of clouds, however be ready, do your homework, learn from the mistakes, misfortune and errors of others. Establish and leverage known best practices while creating new ones. Look at the past for guidance to the future, however avoid clinging to, and bringing the baggage of the past to the future. Use new technologies, tools and techniques in new ways vs. using them in old ways.
Disclosure: I am a customer of AWS for EC2, EBS, S3 and Glacier as well as a customer of Bluehost for hosting and Rackspace for backups. Other than Amazon being a seller of my books (and my blog via Kindle) along with running ads on my sites and being an Amazon Associates member (Google also has ads), none of those mentioned are or have been StorageIO clients.
[To view all of the links mentioned in this post, go to:
http://storageioblog.com/cloud-conversations-gaining-cloud-confidence-from-insights-into-aws-outages/ ]
Some updates:
http://storageioblog.com/november-2013-server-storageio-update-newsletter/
http://storageioblog.com/fall-2013-aws-cloud-storage-compute-enhancements/
Disclosure: I am a real user, and this review is based on my own experience and opinions.

it_user6186Independent Analyst and Advisory Consultant at Server StorageIO - www.storageio.com
Top 20Consultant
AWS EFS (Elastic File Service) is now available with AWS clouds.

Buyer's Guide
Download our free Amazon AWS Report and get advice and tips from experienced pros
sharing their opinions.
Updated: February 2025
Popular Comparisons
Microsoft Azure
Oracle Cloud Infrastructure (OCI)
Akamai Connected Cloud (Linode)
Google Cloud
Alibaba Cloud
Google Firebase
SAP S4HANA on AWS
Nutanix Cloud Clusters (NC2)
DigitalOcean
SAP HANA Enterprise Cloud
Equinix Metal
Google Compute Engine
NTT Cloud
Skytap Cloud
Tencent Cloud
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?
Amazon Web Services is a very helpful platform because of its attractive interface that allows me to obtain and configure capacity information, with minimal friction, that perfectly suits our company. Moreover, it helps me to take complete control of my computer resources and helps to reduce the time required to obtain and to boot new servers, as well. Apart from this, it provides tools to be build-failure resilient applications and to isolate them from common failure scenarios, in a very efficient manner.