Overall Satisfaction with Amazon Elastic Compute Cloud (EC2)
I've used EC2 for both personal projects, as well as evaluation for moving my company's infrastructure to EC2. I used EC2 for hosting a pretty standard Node/Mongo/Angular/Nginx application. In EC2 we put up a few servers - the API was on one, along with Angular, mongo was a second server and the nginx server served as a proxy. We chose EC2 because it was simple to get up and running and we already have experience w/ it.
- Industry standard -- most people who've worked w/ cloud applications have used EC2.
- Easy self-service provisioning once you have IAM configured correctly.
- Lots of compute units with memory / CPU and storage differentiation, many ways to set up a cost-effective environment.
- Can't create custom compute units (specific RAM, SSD and CPU allotments).
- IO seemed to be slower than Google Compute Engine.
- IAM is not straightforward to configure.
- Sustained usage discounts help w/ total cost of cloud infrastructure.
- Tricky to figure out exact cost of infrastructure due to so many pricing levels (based on sustained usage).
We ended up not selecting EC2, we chose Google Compute Engine instead. Reason for us choosing GCE was due to:
- Ability to define custom compute units in GCE.
- More transparent pricing due to automatic usage discounts.
- Less expensive for equal compute unit classes.
- Better UX of the administration and console.