11–20 of 173 posts
That person wasn’t around to respond.
It's also why nothing in my AWS account is "canonical storage". If I need, say, a database in AWS, it is live-mirrored to somewhere within my control, on hardware I own, even if that thing never sees any production traffic beyond the mirror itself. Plus backups.
That way, if this ever happens, I can recover fairly easily. The backups protect me from my own mistakes, and the local canonical copies and backups protect me from theirs.
Granted, it gets harder and more expensive with increasing scale, but it's a necessary expense if you care at all about business continuity issues. On a personal level, it's much cheaper though, especially these days.
If you are given only 5 days to comply with some request, that's how complicated your infra at AWS should be - so you can migrate to another provider in that time. Just use EC2 and basic primitives which are easy to migrate (ie S3, SES)
Lesson to learn: Never use Amazon or anyone else.
They’ve really buried the lede here: this reads like the person paying for the account was not the post author, and AWS asked the payer (who from their perspective is the owner of the account) for information. That person wasn’t around to respond.
They should have to hold it for at least 90 days. In my opinion, it should be more like six months to a year.
In my mind, it's exactly equivalent to a storage space destroying your car five days after you miss a payment. They effectively stole and destroyed the data when they should have been required to return it to the actual owner.
Of course, that's my opinion of how it should be. AFAIK, there is no real legal framework, and how it actually is is entirely up to your provider, which is one reason I never trust them.
My fear of this sort of thing happening is why I don't use github or gitlab.com for primary hosting of my source code; only mirrors. I do primary source control in house, and keep backups on top of that. It's also why nothing in my AWS account is "canonical storage". If I need, say, a database in AWS, it is live-mirrored to somewhere within my control, on hardware I own, even if that thing never sees any production t…
He said, "no, it's on github".
I said no more.
They’ve really buried the lede here: this reads like the person paying for the account was not the post author, and AWS asked the payer (who from their perspective is the owner of the account) for information. That person wasn’t around to respond.
Earlier quoted context omitted.
Wild that people don't realize that these "separate" systems in AWS all share things like the same control plane.
That is wrong in every way possible. Each service is isolated, has its own control plane, and often even split into multiple cells. Source: I worked there. https://docs.aws.amazon.com/wellarchitected/latest/reducing-...
They’ve really buried the lede here: this reads like the person paying for the account was not the post author, and AWS asked the payer (who from their perspective is the owner of the account) for information. That person wasn’t around to respond.
While that is certainly true, the idea that they can so rapidly decimate your data without the possibility to restore is still terrifying if that's your only copy of that data. They should have to hold it for at least 90 days. In my opinion, it should be more like six months to a year. In my mind, it's exactly equivalent to a storage space destroying your car five days after you miss a payment. They effectively stole…