skip to Main Content

Would like to understand does anyone commits the AWS Secret Manager CloudFormation file to private repository ?

If not how should the team manage the changes and version control the configuration ?

2

Answers


  1. It’s not a good practice to store secrets in a CloudFormation template. You should always keep your configuration separated from your code.

    You can use:

    Best approach would be to put most of your configuration in Parameter store, and use Parameter store with Secure String type or Secrets manager only for sensible information.

    For versioning, you can use Secrets manager versioning and save up to 100 versions per secret.

    Login or Signup to reply.
  2. I think it’s security risk to store secrets in CloudFormation templates, even in private repositories. You may store all secrets directly in AWS Secrets Manager and use secret references in your CloudFormation when needed. As for version control, there is AWS Secrets Manager’s built-in configuration.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search