2 ms·
I would say that's not being able to rollback to a last-known-good snapshot-of-the-world a feature, not a bug. A major premise of cloud computing is that every
by nunez 3y ago
I would say that's not being able to rollback to a last-known-good snapshot-of-the-world a feature, not a bug.
A major premise of cloud computing is that everything is disposable.
Consequently, this is meant to encourage consumers to express as much of their system's configuration with code and automation as possible.
For example: the change to the S3 bucket policy that you mentioned would, theoretically, be done by changing the policy doc in Terraform and reapplying the Terraform configuration.
Modification to those policies would, theoretically, only be allowed by anyone with the "AdministratorAccess" role, which would only be provided to the IAM user running Terraform (via temporary STS tokens) or admins through some sort of a "oh-shit" process.
- pxc 3y ago> A major premise of cloud computing is that everything is disposable. That norm is itself a way of coping with the hopeless state of state management, a lesson learned from running imperative/convergent configuration management systems on VMs running mutable operating systems a generation before 'cloud native' was a thing. That whole 'best practice' is a workaround for shaky foundations.