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?
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.
AFAIK , . , , "DeletionPolicy" : "" .
- -, , CloudFormation. , - stack :
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, .
, .
Source: https://habr.com/ru/post/1532161/More articles:Current best practice for a "retirement" project on github and npmjs.org? - githubLibrary call in Lua - luaPhp calendar event with attachment - phphttps://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1532159/disabling-desktop-composition-using-lua-scripting&usg=ALkJrhgYzVRRnu2MTV2FXMEOE6dawcu4iAHow to track user session in Unity3d? - sessionNormalize / translate ndarray - Numpy / Python - pythonМожно ли программно изменить тип сети? - android.NET Domain Model when you need to load a load - c #https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1532165/what-to-do-when-function-has-too-many-arguments&usg=ALkJrhjRjNNwKvL4LdPNKeVvTns2F0AqDwUnsupported media type - HTTP status 415 - javaAll Articles