31–40 of 173 posts
This is why I use a local NAS for offline backups.
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.
The lede buried under that lede is that (according to an insider?) some AWS employee accidentally wiped everything immediately (contrary to typical practice in such situations of retaining data while things get sorted out), leading to a chain of brushing-off / covering-up percolating through whatever support chain the OP was talking to.
But the overall post and the double buried ledes make me question the degree to which we’re getting the whole story.
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…
I once said to the CTO of the company I worked for "do we back up our source code"? He said, "no, it's on github". I said no more.
Earlier quoted context omitted.
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…
It sounds like it wasn’t OP’s data though, which is an important distinction.
Earlier quoted context omitted.
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-...
Not sure why you’re being downvoted, this is 100% correct from someone else who worked there.
If you're not sure why someone is being downvoted, there's a good chance there is a misunderstanding somewhere, and a good way for you to understand is to wait for people to comment, and then read those comments.
Alternatively (and in a more general sense), if you want to take a more active role in your learning, a good way to learn is to ask questions, and then read the answers.
They're going to dazzle you with all of their hardened bunker this, and multiple escape route that, not realizing all of their complex machinery is metaphorically running off of a machine with no battery backup. One power outage and POOF!
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…
I once said to the CTO of the company I worked for "do we back up our source code"? He said, "no, it's on github". I said no more.
Additionally to that, if any of those developers have a backup strategy for their local computer, those also count as a backup of that source code.
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…
Similarly, a physical storage company can totally make a mistake and accidentally destroy your stuff if they mix up their bookkeeping, and your remedy is generally either to reach an amicable settlement with them or sue them for your damages.
Earlier quoted context omitted.
I once said to the CTO of the company I worked for "do we back up our source code"? He said, "no, it's on github". I said no more.
If nobody has the repo checked out, what are the odds it's important?
Oh boy.
Tons of apps in maintenance mode run critical infrastructure and see few commits in a year.