The primary use case of this solution is for hosting your infrastructure.
Founder & Chief Operating Officer at a tech services company with 11-50 employees
Stable, easy to use, with good support, and it is priced well
Pros and Cons
- "It's very easy to use."
- "Integration with in-house applications could be simplified."
What is our primary use case?
What is most valuable?
It's very easy to use.
What needs improvement?
The activation process can be improved. Sometimes, the activation takes a lot of time. There are many components of the infrastructure.
Integration with in-house applications could be simplified.
For how long have I used the solution?
We have been dealing with Amazon AWS for one year.
We are using the latest version.
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?
It's a stable solution.
What do I think about the scalability of the solution?
It is a scalable product. We have 30 users in our organization.
We plan to continue to use Amazon AWS.
How are customer service and support?
We have never had a problem with technical support.
How was the initial setup?
There is no installation for this solution. It's a cloud solution.
What's my experience with pricing, setup cost, and licensing?
There is a cost for any components you get.
AWS is not an expensive product.
What other advice do I have?
I absolutely recommend this product.
I would rate Amazon AWS an eight 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.
Full Stack Developer at a tech services company with 11-50 employees
Manages ELB with less configuration from the users' side.
What is most valuable?
Elastic Load Balancer: AWS completely manages ELB with less configuration from the users' side. Setting up the load balancer manually is really a headache.
How has it helped my organization?
Deploying to the elastic cloud is much easier now with AWS. This makes the go-live process easy.
What needs improvement?
Billing: They should make billing more simplified. It would be great if they could explain how deploying to elastic cloud is much easier now with AWS. Elastic beans command line interface [eb cli]: You can easily deploy code straight from your code IDE.
The billing calculator has lot of options which confuses the user. If they could provide some template for billing and directly execute those template, that would be great.
For example, the billing template for the standard WordPress Server with Load Balancer and S3 Connectivity: Users could just change the parameters inside the template and execute to see their estimated billing.
For how long have I used the solution?
We have been using this solution for three years.
What do I think about the stability of the solution?
I did not encounter any issues with stability.
What do I think about the scalability of the solution?
I did not encounter any issues with scalability.
Which solution did I use previously and why did I switch?
We were using only AWS.
How was the initial setup?
The setup was straightforward in all ways.
What's my experience with pricing, setup cost, and licensing?
Free tier is always there for demo and testing. Pricing is based on the usage.
Which other solutions did I evaluate?
We evaluated Microsoft Azure.
What other advice do I have?
AWS is good for any kind of requirements.
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.
Database Expert with 51-200 employees
Migrating to Amazon RDS
Having used AWS for a few years, there are numerous ways to get "your data" to the cloud. Usually the simplest is export/import (bias towards Oracle), but this process is usually slow when you start moving large data sets. There is the RMAN backup/recovery manager but this requires you to have the same instance version in the cloud - not good if you want to upgrade at the same time. Datapump is also available and is very useful as you can do Network data Pumps across database links - but again this can sometimes be slow.
I then looked into using Amazon's Advanced Data Migration Techniques (published Nov 13 2013) and decided to give it a go and have posted my walk through below (quite technical):
http://www.connecteddba.com/howto/MigratetoRDS.htm...
This was done from a local "data center" 100GB database, exported using datapump, copied to a M1.Xlarge EC2 in cloud and then copied further to the backend DATA_PUMP_DIR on the RDS instance (which you don't have access to). Then a datapump import into the RDS and job done - took me approx 12 hours in total (and that wasn't using Tsunami).
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical and Solutions Executive at a tech services company with 1-10 employees
User-friendly, scale as you require, easy to setup, and the support is good
Pros and Cons
- "It's very user-friendly."
- "The interface could be improved."
What is our primary use case?
I use this solution to build IoT products.
I am a customer and I have a reselling agreement.
How has it helped my organization?
We use this product to build our products and services, which is what we sell.
What is most valuable?
I like that all of the features are complimentary. I use all of the features together.
It's very user-friendly.
There is nothing that needs changing.
What needs improvement?
The interface could be improved.
For how long have I used the solution?
I have been using Amazon AWS for two years.
What do I think about the stability of the solution?
It is a very stable product.
What do I think about the scalability of the solution?
Amazon is based on scalability. You can scale as you require. We have no issues with scalability.
How are customer service and technical support?
The technical support is very good.
How was the initial setup?
The initial setup is easy.
What about the implementation team?
I completed the installation myself.
What's my experience with pricing, setup cost, and licensing?
Pricing is good. It's average.
Which other solutions did I evaluate?
I also evaluated Microsoft Azure.
What other advice do I have?
I would advise others to use the platform.
I would rate Amazon AWS an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: reseller
Cloud Architect at a tech vendor with 1,001-5,000 employees
Easy provisioning means quick time to market when a new environment is required
What is most valuable?
- RDS: Because of its auto-scaling, multi-zone availability, and its quick spin up of database servers.
- EC2 Servers: For the agility of server provisioning and the AMI automations.
- Lambda: Because of AI capabilities by writing functions that trigger on events.
- Route 53: For traffic engineering.
- WAF: For security and multiple other features of AWS.
How has it helped my organization?
Rolling deployments, quick time to market;
From one day deployment time, it came down to 15 minutes.
Easy provisioning means quick time to market when a new environment is required.
What needs improvement?
The console's UI could be a little better, a fluid User Experience is missing.
For example, in order to see the instance details properly, we have to scroll the description part up or down, which is not a recommended way of doing it.
For how long have I used the solution?
Three years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
No.
How are customer service and technical support?
Excellent. 10 out of 10 for this.
Which solution did I use previously and why did I switch?
IBM Softlayer and Azure. Both are not automated to the level that AWS is automated.
How was the initial setup?
Straightforward.
What's my experience with pricing, setup cost, and licensing?
Pay per use.
Which other solutions did I evaluate?
Yes, RedHat OpenShift.
What other advice do I have?
Migrate to AWS for speed and agility, combined with its security features.
Disclosure: My company has a business relationship with this vendor other than being a customer:
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?