21–30 of 173 posts
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)
>Just use EC2 and basic primitives which are easy to migrate (ie S3, SES) If that's your whole infra you really shouldn't be on AWS in the first place.
So you restored from your off cloud backup, right? Tell me you have off cloud backups? If not, then I know its brutal, but AWS is responsible for their part in the disaster, and you are responsible for yours - which is not being able to recover at all.
Store your data on your own disks, then at least you will blame yourself, not .. Java command line parsers?
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-...
Some accident occurs. You don't pay your bill, address changes, etc. You have at least two entire years to contact the holder and claim your property. After that point, it is passed to the state as unclaimed property. You still have an opportunity to claim it.
Digital data? Screw that! One mistake, everything deleted.
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)
The amount of people shilling for a multi billion dollar corporation is baffling.
A lot of people in this industry have near-zero operations knowledge that doesn't involve AWS, and it's frightening.
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-...
I mean, sure every Ford Pinto is strictly it's own vehicle, but each will predictably burst into flames when you impinge its fuel tank and I don't wanna travel on a company operating an all Pinto fleet.
https://aws.amazon.com/compliance/shared-responsibility-mode...
You, the customer, are responsible for your data. AWS is only responsible for the infrastructure that it resides on.