One other non-sensical Coverage Doc error message in CloudFormation
I could have written about this earlier than however this one of many worst error messages for Coverage Paperwork in existence. How is an finish consumer studying this error message alleged to know what to do with this?
The coverage failed legacy parsing (Service: AmazonIdentityManagement; Standing Code: 400; Error Code: MalformedPolicyDocument; Request ID: xxx; Proxy: null)
This error message occurred as a result of I failed to make use of a sub in my coverage when utilizing an AWS pseudo parameter. That’s it. Right here’s the coverage:
As an alternative of this:
Useful resource:
- !Sub 'arn:aws:iam::${AWS::AccountId}:function/Lambda*'
- !Sub 'arn:aws:iam::${AWS::AccountI}:function/Batch*'
I had this:
Useful resource:
- 'arn:aws:iam::${AWS::AccountId}:function/Lambda*'
- 'arn:aws:iam::${AWS::AccountId}:function/Batch*'
One factor I’m wondering is, why do we’d like the sub in any respect? Can’t AWS inform that it must substitute one thing when it runs throughout ${ ??
Anyway, that’s at the very least one repair should you see: “The coverage failed legacy parsing” whereas deploying a CloudFormation template.
Teri Radichel
When you preferred this story please clap and observe:
Medium: Teri Radichel or E-mail Record: Teri Radichel
Twitter: @teriradichel or @2ndSightLab
Requests providers through LinkedIn: Teri Radichel or IANS Analysis
© 2nd Sight Lab 2022
____________________________________________
Creator:
Cybersecurity for Executives within the Age of Cloud on Amazon
Want Cloud Safety Coaching? 2nd Sight Lab Cloud Safety Coaching
Is your cloud safe? Rent 2nd Sight Lab for a penetration take a look at or safety evaluation.
Have a Cybersecurity or Cloud Safety Query? Ask Teri Radichel by scheduling a name with IANS Analysis.
Cybersecurity & Cloud Safety Sources by Teri Radichel: Cybersecurity and Cloud safety courses, articles, white papers, displays, and podcasts
