How to prevent CloudFormation stack exception (accidentally)?

CloudFormation clouds are great for automation, but the problem I see with them is how easy it is to delete them and, in turn, cascade the deletion of other resources.

I already found a solution to the last problem, you can protect each of the resources by changing the delete policy. But what about the stack as a whole? Is it possible to protect him?

+4
source share
3 answers

I think the only way is to restrict access to the IAM users that you use. You can remove the “Delete Stacks” permission from all relevant users.

+3
source

AFAIK , . , , "DeletionPolicy" : "" .

+1

- -, , CloudFormation. , - stack :

String: name -- name of the stack
String: template -- JSON template for the stack
String: createdby -- name of the user that created the stack
Boolean: protected -- true if protected.

, / , , AWS IAM, .

, .

0

Source: https://habr.com/ru/post/1532161/


All Articles