Amazon Web Services
Updated April 08, 2015

Amazon Web Services

Doug Symes | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version


Modules Used

  • EC2
  • IAM
  • Route 53
  • AMI
  • RDS
  • SES
  • SNS
  • CloudWatch
  • VPC
  • S3
  • Glacier

Overall Satisfaction with Amazon Web Services

IT at Qualbe uses Amazon Web Services to do software development, perform testing and for production infrastructure supporting web servers, DNS and database applications.
  • Database Services
  • Virtualization of Windows and Linux instances
  • CloudWatch alarms are dropped when an instance is terminated and regenerated from an AMI. There is no way to transfer CloudWatch alarms.
  • Tag retention. There is no way to retain a set of tags so they can be applied to a new EC2. They die with the previous EC2.
  • Scalability is a major factor to our use of AWS. As we grow we can quickly spin up instances and AWS scales with our business. The upfront capital investment of computer hardware is avoided.
  • We can pay for just what we use. We don't have hardware sitting around collecting dust.
  • Reliability. Faulty hardware is no longer a concern for us.
We used to use Rackspace but switched because of the reasons I outlined...basically being responsible for the hardware.
Autoscaling is very handy with AWS EC2 instances for web servers. AWS is well suited to such scenarios. Software development is a great use for AWS EC2 and RDS instances. You can bring up servers and deploy different revisions of an application for testing and debugging.

Using Amazon Web Services

Support at AWS is great! The cost is low. Their business model is sound. They tend to benefit us.

Amazon Web Services Implementation