Until that server goes down.
I wonder what percentage of all sites hosted at AWS are actually ready for a zone to fail.
From OVH VPS. Funny thing it's 666 today. YMMV
# uptime 01:47:03 up 640 days, 6:53, 2 users, load average: 2.39, 2.62, 2.73
From hetzner dedicated server. YMMV
# uptime 01:48:11 up 482 days, 20 min, 2 users, load average: 1.53, 2.10, 2.78
From leaseweb dedicated server. YMMV
03:48:56 up 238 days, 15:04, 1 user, load average: 0.00, 0.01, 0.05
Having run a simple web server + database on both EC2 and Digital Ocean I disagree. The two services are nearly identical at that scale.
In fact I don’t see any significant differences between any of the proper cloud providers at this level. The cost & functionality are very nearly the same.
This seems backwards to me - running a simple VPS on something like OVH/DigitalOcean/Linode is a matter of creating the instance, setting the size, and setting up your server software. Super simple, and likely about the same complexity as setting up a dev environment.
Setting the same thing up on AWS requires slogging through the documentation of their many services, deciding what makes the most sense for you (EC2? ECS? EKS? Lambda? Fargate?), and then configuring more options with less-friendly UI than any other provider I've seen. If you can fully wrap your head around all those services, create a stack that makes sense, and maintain it long-term, you're probably well on your way to being qualified for a DevOps engineer job. I can spin up a quick DigitalOcean droplet for a new project in less than half the time it'd take me to set up an EC2 instance, configure the exact amount of storage I need, and pull up 2 additional browser windows to determine the specs and pricing of different instance sizes in different regions.