OneUptime has published their update after two years since moving from AWS.

It's an interesting read, and tl;dr is that they do not regret their decision at all. Although, they admit that they still use cloud for dev environments, cold storage, etc.

Here are a few points that I find interesting:

- Our workload is 24/7 steady / We still recommend staying put if your usage pattern is spiky or seasonal - right sizing is one of the major advantages of clouds that is often overlooked.
- We still recommend staying put if you lean heavily on managed services - this is another important point. Managed services add a lot of value to the clouds. It does seem a bit dumb to use AWS just like an expensive datacenter. On another hand, if you want to be able to do multi-cloud, hybrid-cloud, etc.; you have to make a deliberate decision to stay as much decoupled from cloud offerings as possible. It's a deliberate strategy that trades flexibility for immediate value.
- Ceph stack in production - I'm sure, Ceph evolved a lot through the years, but I still remember words of a colleague of mine from a long time ago: "We didn't lose the data, we just cannot retrieve it". Back then, we decided to keep on-premise installations with ephemeral disks and ship all the data that has to be preserved into AWS (it's not like there was a lot of data to preserve there, though).
- so we added Anycast ingress via BGP with our transit provider to cut traffic shifting to sub-minute and We PXE boot with Tinkerbell - ask on an interview about Anycast, and the same day you will get an angry post on Reddit about unreasonable questions and lowballing candidates, lol. Or maybe, it's just my pessimism speaking.

Anyway, use your best judgment before doing any rapid moves. BTW, this advice is generally applicable, and is not limited to the clouds vs dc discussions.

#aws #bare_metal