An error occurred (ValidationError) when calling the CreateChangeSet operation: Template error: the attribute in Fn::ImportValue should not depend upon any assets, imported values, or Fn::GetAZs | by Teri Radichel | Bugs That Chew | Sep, 2022

September 20, 2022

1

One other deceptive error from CloudFormation

This error is form 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 fancy approach, to not point out I in all probability want glasses.

I used to be my template again 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 title. That labored.

I believe I in all probability 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 will be extra acceptable to say:

The worth referenced in your Sub doesn't exist on this template. Verify to see that the title you might be passing in precisely matches what you might be are attempting to reference.

Additionally I want AWS would repair the inconsistent syntax. It’s onerous to recollect how you can create all these one-off circumstances.

Another: I noticed another person bought the identical error I am going the place the FN::Import can’t be on the identical line because the property — a mapping error. The individual responding to them stated “effectively it’s invalid yaml.” However that is CloudFormation, not simply Yaml. Overwrite that underlying YAML error message with one thing extra significant within the context of CloudFormation.

Teri Radichel

In the event you favored this story please clap and comply with:

Medium: Teri Radichel or E-mail Record: Teri Radichel
Twitter: @teriradichel or @2ndSightLab
Requests companies through LinkedIn: Teri Radichel or IANS Analysis