Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS::SecretsManager::Secret-DeletionPolicy #405

Closed
AknEp opened this issue Mar 2, 2020 · 2 comments
Closed

AWS::SecretsManager::Secret-DeletionPolicy #405

AknEp opened this issue Mar 2, 2020 · 2 comments

Comments

@AknEp
Copy link

AknEp commented Mar 2, 2020

I want to keep secret value after stack deletion, similar to other almost all resources can.

2. Scope of request

AWS::SecretsManager::Secret-DeletionPolicy DOES NOT supports DeletionPolicy.

It would be a new option for an existing attribute is desired type of request.

3. Expected behavior

I expect AWS::SecretsManager::Secret to be exists after stack deletion, s3::Bucket or other many resources as is.

6. Category (required) - Will help with tagging and be easier to find by other users to +1

Use the categories as displayed in the AWS Management Console (simplified):

  1. Security (IAM, KMS...)
@PatMyron
Copy link
Contributor

PatMyron commented Mar 2, 2020

Creating and deleting a stack with this template works as desired in us-east-1:

Resources:
  Resource:
    DeletionPolicy: Retain
    Type: AWS::SecretsManager::Secret

Could you share that part of your template or more details on where you're experiencing this?

@AknEp
Copy link
Author

AknEp commented Mar 2, 2020

@PatMyron Thanks a lot.
Actually, I'm using AWS-CDK.

As cdk doesn't provide this option, and cloudformation's document does not mention to DeletionPolicy, I thought it's because of cloudformation.

But, it may CDK's issue. I'll make other issue on cdk repository.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants