We primarily use the solution for the infrastructure. We use it specifically for hosting the infrastructure and hosting our analytics database.
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?
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.
Buyer's Guide
Amazon AWS
January 2025
Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,265 professionals have used our research since 2012.
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 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
Buyer's Guide
Amazon AWS
January 2025
Learn what your peers think about Amazon AWS. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,265 professionals have used our research since 2012.
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.
Platform Technologies Lead Engineer at a energy/utilities company with 1,001-5,000 employees
Good performance, robust, and scales well
Pros and Cons
- "The technical support is good."
- "It is difficult to hand over legacy applications when migrating them to the cloud."
What is our primary use case?
We use Amazon AWS to store and run cloud-based applications in the cloud, such as databases, virtual machines, and dockers.
What needs improvement?
The price could be reduced.
It is difficult to hand over legacy applications when migrating them to the cloud. It's a challenge.
For how long have I used the solution?
I have been working with Amazon AWS for approximately eight years. It's been a long time.
We are working with the latest version.
What do I think about the stability of the solution?
We have no issues with the stability of Amazon AWS.
What do I think about the scalability of the solution?
Amazon AWS is a scalable solution.
We are providing applications at a global level. This solution is used by 1,000 users.
How are customer service and support?
The technical support is good.
How was the initial setup?
The installation can be challenging when migrating legacy applications to the cloud.
What about the implementation team?
Most of the time, I require the assistance of some technicians.
What's my experience with pricing, setup cost, and licensing?
It is very expensive, you have to be very cautious.
Licensing fees are paid on a monthly basis.
What other advice do I have?
I would recommend this solution to others who are interested in using it.
I would rate Amazon AWS 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.
Service Engineer at a tech services company with 201-500 employees
Provides valuable features like Cloud Management, but the hybrid cloud could have better support
Pros and Cons
- "Cloud Management has been a valuable feature."
- "In some scenarios, Azure will support hybrid cloud better while AWS offers direct connection."
What is our primary use case?
I am an integrator.
We get some courses and communications from the technology, so we update our knowledge about how to use that kind of technology for the cloud.
What is most valuable?
Cloud Management has been a valuable feature. It depends on how we meet our business challenge head-on with the cloud computing services because sometimes you find that the computing is working fine with Google, and sometimes it's Azure, and sometimes it's Amazon.
One customer is going to work with Azure, and the next year they'll change everything and work with AWS because in our environment the most sensitive data is kept in the on-premise environment the majority of the time. It's more frequent that you can find an environment that has hybrid implementation.
What needs improvement?
I think in some situations the key difference between Azure and AWS is how they support the hybrid cloud. In some scenarios, Azure will support hybrid cloud better while AWS offers direct connection. Azure provides security by offering information on the whole account where AWS security provides an easy find row. It depends on what the customer wants to have in the environment or how they want to work with that or what is the customer's budget.
Most of the issues are that because it's a hybrid environment, the configuration is restricted with the firewalls. The most common issue that they have found is generated by the person who administers these kinds of solutions.
It would be great if you could find a way to make an architect design and just click one button and put that in the cloud.
For how long have I used the solution?
I have been using this solution for more than six years.
How was the initial setup?
It's simple because the customer will get familiar with the technology. The customer has to know his company. He has to know it's a new technology and everything gets complicated if the person doesn't adapt to changes. It depends on how they approach all the adoption from this kind of multi-cloud solution.
What other advice do I have?
I would rate this solution 7 out of 10.
My advice is to read about the solution. All of the learning is logical, and you can follow it and put it in practice. I believe it's a great product and great technology.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PKI Policies Manager at a tech vendor with 201-500 employees
Stable, scalable and flexible
Pros and Cons
- "I especially like the flexibility and scalability of the solution."
- "While feasible, custom configuration will be more time consuming than standard."
What is our primary use case?
While I cannot say for certain, I believe that we are using the latest version.
We primarily use the solution to rent servers for storing certain commercial applications.
What is most valuable?
I especially like the flexibility and scalability of the solution. It is totally scalable.
What needs improvement?
While feasible, custom configuration will be more time consuming than standard, although we have not encountered many instances which required us to seek support or advice.
For how long have I used the solution?
I believe we have been using Amazon AWS for more than 10 years.
What do I think about the stability of the solution?
The solution is absolutely stable. This is one of its best features.
What do I think about the scalability of the solution?
The solution is absolutely scalable.
Amazon allows us to scale up and then down, something important to one of our customers who was in need of temporary increases in the throughput provided to the servers. This allowed us to meet the client's needs for the days or weeks that they required more dynamically located servers, after which we were able to scale down. This we were able to do through Amazon. This was difficult to accomplish beforehand, as the client had private servers for which he was forced to buy machines which he would subsequently keep.
How are customer service and support?
I cannot comment on Amazon's technical support, as we have not made use of it.
Which solution did I use previously and why did I switch?
We did use other solutions prior to Amazon AWS. We made use of local service and dealt with projects involving Google and Microsoft. We also used Microsoft Azure.
Not long ago we used Microsoft Azure, though this is necessary with some of our projects. We have different projects which vary with the customer's specifications. Some utilize Azure, although most require the use of Amazon.
When comparing Microsoft Azure with Amazon AWS, I do not see much disparity. It really comes down to a business choice. If the customer is familiar with Microsoft, then the testing team maintaining the product will need to be acquainted with it as well and its ongoing use is required. Similarly, Amazon will continue to be employed if this is already the case. As such, the difference betwen the solutions does not come down to considerations of a technical nature as they are largely similar. The primary consideration is one of business, the use of one solution and provider over another.
How was the initial setup?
When it comes to standard configuration, the installation is quick, usually taking one or two days to complete. Custom configuration, while feasible, takes somewhat longer. So far, we have not had many instances in which we required support or advice concerning custom configurations.
The technical team would be in a better position than I to address any technical issues involved in the setup. From my perspective as a project manager, I feel what we have to be sufficiently good. There is much advertising, information on the advantages of the product and guides available.
What about the implementation team?
Installation was carried out by our own internal integration team, not externally outsourced. I did not handle it myself. It was done by a team specialist.
The technical team responsible for the deployment consists primarily of engineers.
What was our ROI?
I cannot comment on whether we have seen an ROI, return on investment, as I do not possess this information.
What's my experience with pricing, setup cost, and licensing?
The licensing cost varies with the project involved. Certain projects run around $6,000 per month, some less and others more. We handled many projects, each with its own complexities and specifications. The price ranges of the licenses varies with the complexity of the project.
What other advice do I have?
Broadly speaking, there is a need to rely on specialists for properly setting up one's accounts and addressing his needs. This is not specific to Amazon, however, but is something prevalent with all providers.
I have assumed the role of both customer and integrator. In the past, I worked as a project manager with different projects employing Amazon products, services and software.
For the most part, the solutions I used have been public, not private, such as AWS cloud.
The number of users of the solution varies with the individual project. This can range from 20 to 200 to 500 users.
Our teams have undertaken every role, be them architecture, development, design or testing. They are all internally integrated.
I am a fan of Amazon products and generally recommend them to others. Of course, we employ Azure and Google products when the customer specifically requests these.
Since all products have room for improvement, even when this is not apparent to me, I rate Amazon AWS as a nine out of ten.
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.
Software Architect at AIOPS group
Very stable and scalable, but could use more integration
Pros and Cons
- "One of the most valuable things about it, besides the stability, is that you can forget about infrastructure because you're just doing it on AWS. I remember the times before AWS and other cloud solutions existed, and it was a huge pain to get real hardware, put it inside, configure everything, report everything, and do a scale. It was very, very difficult compared to how it is now. Not even just AWS, but what all these cloud providers are doing, I would say, is a huge advancement in technology."
- "AWS could be improved with more integration, but I can see that they're developing these features and working very hard on their platform."
What is our primary use case?
Our primary use case of AWS, for most projects, is for hosting on AWS and developing locally, as well as testing some AWS environments. We are mostly using this platform from a developer point of view. AWS is our cloud platform by choice.
What is most valuable?
One of the most valuable things about it, besides the stability, is that you can forget about infrastructure because you're just doing it on AWS. I remember the times before AWS and other cloud solutions existed, and it was a huge pain to get real hardware, put it inside, configure everything, report everything, and do a scale. It was very, very difficult compared to how it is now. Not even just AWS, but what all these cloud providers are doing, I would say, is a huge advancement in technology.
What needs improvement?
AWS could be improved with more integration, but I can see that they're developing these features and working very hard on their platform.
For how long have I used the solution?
I have been working with AWS for a few years.
What do I think about the stability of the solution?
Amazon AWS is very stable.
What do I think about the scalability of the solution?
One of the major points for AWS is the scalability that comes with it. You can monitor it really well, and you can even adjust down, or sometimes up. What this technology allows is very nice.
AWS is predominantly used in most of the projects that we have. In my organization, there are thousands of users who are using AWS.
How are customer service and support?
I have never personally contacted tech support.
How was the initial setup?
There isn't really an installation for AWS, but you will need certain certificates to download the interface. I generated some certificates, put them on my machine, and then used them to connect to AWS services.
It depends on the project, but there is usually only one guy needed for deployment. For bigger, more complex platforms, you may need two or three guys to deploy AWS.
What about the implementation team?
I implemented AWS myself.
What's my experience with pricing, setup cost, and licensing?
You pay for a license, and that's how you get your own account. These are usually not individual licenses, but rather for a group of people. I think these licenses come at some volume, but I don't know many details about the licensing.
What other advice do I have?
I rate AWS a five out of ten, but it's mainly because I don't feel very experienced in AWS. I have gone to the console many times and seen many features that I have never used. I'm sure I can learn quickly, though, because there is a lot of information shared on the internet about how to use it—there are a lot of resources that you can use to learn, and there are a lot of features available on AWS. They're working very hard on their platform, and I can only see their usage growing in the future.
I would certainly recommend AWS to others.
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: January 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
F5 Volterra
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.