It’s a good question. That said unless there are compliance or fallback concerns i would prefer a service that burns my data on departure.
It’s a good question. That said unless there are compliance or fallback concerns i would prefer a service that burns my data on departure.
No, that's the naive view
Because in case of a compromise/unauthorized access that's exactly what you don't want to happen
> No, that's the naive view
No, not really. That's pretty basic stuff. You would do well in reading up on the shared responsibility model. Customers are responsible for setting up their own infrastructure, and platform/service providers are only responsible for the services they manage. Even then, stuff like persisted data is still recoverable by design.
But you are absolutely responsible for the service you put together. This is a basic principle for around two decades. Infrastructure as code tools are pervasive and ubiquitous for over a decade.
Oh "reading about it"?
Try experiencing it in person
Again this is the naive view
Again if someone compromises your accounts and everything is deleted instantly you'll be the one looking like a fool