[jopsen]

IMO the best examæel is spinning up a DB with nightly snapshots. This is trivial in AWS. Doing it in your datacenter takes planning, decispline, skills and time.

Same goes for backups to S3 vs. setting up a SAN on the datacenter.

Managing AWS infrastructure isn't trivial, it's easy to forget what that instance does, if everything was provisioned with point and click. Cloudformation or terraform makes it doable. But technical debt is also something you can defer payment on :)

[NathanKP]

Yeah the DB example is particularly relevant. Amazon Aurora now has continuous point in time backups so in the event of something going wrong you can roll the database back to an arbitrary second: https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-tur...

Additionally Aurora has robust zero downtime self recovery from a variety of error conditions including disk failures, and you can test that out by running a SQL query that simulates disk failures for example: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Auror...

This level of operational excellence is incredibly hard to build yourself either on premise or even in the cloud if you are only using VM's. Time and time again you see companies that thought they had backups but then discover the backups don't work right. It's not because these companies are stupid, its because it is hard to do right, and building and testing this requires a lot of engineer time. When you do take the time to hire the right people who can do it right you end up finding it is way more expensive to do it yourself than using a cloud managed service. AWS is able to offer the service much cheaper because the cost of development and maintenance, etc is spread across a huge number of customers.