I am using SSM Secure Parameter store to store a password for an RDS DB.
ssm-secure:
like this "MasterUserPassword": {
"Fn::Sub": "{{resolve:ssm-secure:${WorkshopName}:1}}"
},
Note the "1". The SSM Secure String Parameters docs are very clear: An integer that specifies the version of the parameter to use. You must specify the exact version. You cannot currently specify that AWS CloudFormation use the latest version of a parameter
That's the bummer
The ciphertext refers to a customer master key that does not exist, does not exist in this region, or you are not allowed to access.
)Any programmatic suggestion on how I might implement more resilient logic to either
Looks here like the behavior has changed:
version
An integer that specifies the version of the parameter to use. If you don't specify the exact version, CloudFormation uses the latest version of the parameter whenever you create or update the stack. For more information, see Working with parameter versions in the AWS Systems Manager User Guide
Optional.
So now it can access the latest version