1 Answer
- Newest
- Most votes
- Most comments
0
I worked it out.
The template had a reference to a parameter being of type AWS::SSM::Parameter::Name but that was unresolvable because the account launching the CloudFormation didn't have ssm:GetParameter action permissions.
A better error message and fast-failure would have been helpful in debugging this.
answered 5 years ago
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated a year ago