Possible values for a resource’s Removal Policy.
The removal policy controls what happens to the resource if it stops being managed by CloudFormation. This can happen in one of three situations:
The resource is removed from the template, so CloudFormation stops managing it;
A change to the resource is made that requires it to be replaced, so CloudFormation stops managing it;
The stack is deleted, so CloudFormation stops managing all resources in it.
The Removal Policy applies to all above cases.
Many stateful resources in the AWS Construct Library will accept a
removalPolicyas a property, typically defaulting it to
If the AWS Construct Library resource does not accept a
removalPolicyargument, you can always configure it by using the escape hatch mechanism, as shown in the following example:
# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826 cfn_bucket = bucket.node.find_child("Resource") cfn_bucket.apply_removal_policy(cdk.RemovalPolicy.DESTROY)
This is the default removal policy.
It means that when the resource is removed from the app, it will be physically destroyed.
This uses the ‘Retain’ DeletionPolicy, which will cause the resource to be retained in the account, but orphaned from the stack.
This retention policy deletes the resource, but saves a snapshot of its data before deleting, so that it can be re-created later.
Only available for some stateful resources, like databases, EFS volumes, etc.