- Newest
- Most votes
- Most comments
Hi.
This error occurs due to a known bug where CloudFormation when dynamically references SSM parameters, it doesn't pick up the latest timestamp from SSM parameter store.
Here is the recommended workaround to resolve this issue:
-
Recreate the SSM parameter.
-
Get the new parameter timestamp using the command $aws ssm get-parameter --name ‘the name of the ssm parameter’. The timestamp is LastModifiedDate. You'll need to convert it to a Unix timestamp with milliseconds. You can do it by pasting the date here and copying the appropriate formatted value.
-
Copy the processed template entirely and save it to a file (you'll have to edit and upload it later).
-
Update the template file with the new SSM Parameter (correct the version and the timestamp for the ssm parameter)
-
In your stack, click Update, choose "Replace current template", and "Upload a template file". Pick the new template file you've just corrected.
-
Finish the wizard by clicking Next until the last step, and finally click Update stack.
Relevant content
- asked a year ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago