I’ve spent a lot of the past couple of days setting up storage buckets, static web site and attempting to bolt-on https with a load balancer/CDN on AWS and then Google Cloud. Here are some comparison thoughts and notes:

  • I like that AWS is offering free https certificates for their services
  • Both providers’ instructions are very self-specific
    • I get that on the one hand, but on the other hand it can be a bit frustrating on the learning curve trying to do the same thing with two different vendors
    • For example, I get why Google would want to encourge their own tools, but I know it’s possible to use AWS cli against Google’s Cloud Storage, and I already have it installed, so couldn’t they make it a little less hard to figure out how to make it work by providing some examples?
  • Google seems to offer load-balancing without CDN
  • AWS seems to bundle CDN and load balancing together in CloudFront without the ability so separate them.
  • AWS Elastic Beanstalk seems to not work against S3 bucket http as back ends and requires VMs
  • It would be nice to be able to throw out a small, static storage bucket with https ability, but both services require setting up a load balancer / CDN to do it
  • I like Google’s docs better. They aren’t perfect, but I really like that each example offers how-tos for UI, command-line, XML API and JSON API
  • I also like Google’s in-browser Cloud Shell, especially along with the gsutil and gcould command examples in the docs
  • In contrast, the AWS docs I’ve read don’t seem to mention the API or CLI at all. I’m sure the AWS docs are there, but I’ll have to go back later and search them out, but with Google docs I know I can go back to the same link and tab over to the alternate examples.

This is not intended as “one is better than the other”. I expect to be using the three major cloud vendors, so I’m interested in learning the differences and similarities for particular purposes. So far my focus is in using storage buckets as back ends for static https sites and also looking out for alternate routings and redirect configurations.