AWS::SecretsManager::RotationSchedule doesn't check for existing schedule


I was able to add a SecretsManager rotation schedule resource to two different stacks for the same secret. When I removed the duplicate resource from one one of the stacks it deleted the schedule from the secret.

  1. This seems like a bug in Cloudformation/Secrets Manager. I'd expect them to prevent creating the same resource in two different stacks.
  2. Any advice on getting the schedule back in sync with the remaining stack resource?
1 Answer

Hi, AWS-User-1437729

You're right, I'm not seeing a do not duplicate check in the API doc for AWS::SecretsManager::RotationSchedule properties.

What do your CFN templates look like, are you doing nested stack or export-import with your resource creations?

profile pictureAWS
answered 21 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions