One other deceptive error from CloudFormation
This error is sort of proper however largely unhelpful within the specific case I used to be having. I had named some parameters I handed into my template in a posh method, to not point out I most likely want glasses.
I used to be taking a look at my template time and again and thought I had copied the documentation precisely for FN::Import — even the bizarre caveats.
Lastly I copied and pasted the code from the documentation after which copied and pasted my parameter names into the sub identify. That labored.
I believe I most likely had a typo within the Sub that was referencing a parameter. So the error message is telling me one thing that on this case doesn’t make sense.
It could be extra acceptable to say:
The worth referenced in your Sub doesn't exist on this template. Verify to see that the identify you might be passing in precisely matches what you might be are attempting to reference.
Can also you please repair the bizarre, inconsistent syntax? It’s laborious to recollect how you can create all these one-off instances.
Another: I noticed another person received the identical error I’m going the place the FN::Import can’t be on the identical line because the property — a mapping error. The particular person responding to them stated “properly it’s invalid yaml.” So? That is CloudFormation. Overwrite that underlying YAML error message with one thing extra significant within the context of CloudFormation.
In the event you favored this story please clap and observe:
Medium: Teri Radichel or E mail Record: Teri Radichel
Twitter: @teriradichel or @2ndSightLab
Requests companies by way of LinkedIn: Teri Radichel or IANS Analysis
© 2nd Sight Lab 2022
Want Cloud Safety Coaching? 2nd Sight Lab Cloud Safety Coaching
Cybersecurity & Cloud Safety Assets by Teri Radichel: Cybersecurity and Cloud safety courses, articles, white papers, shows, and podcasts