Route desk not related to VPC
I had what I believed was a typo in my CloudFormation template as follows:
It might appear to me that CloudFormation ought to throw an error on this case as a result of so far as I can inform from the documentation “Ref:” will not be a legitimate ingredient in a yaml CloudFormation template. Or is it. I at all times use !Ref.
Nonetheless, upon additional evaluate, I see that the Ref syntax is supplied within the instance within the route desk documentation:
I modified the syntax to what ought to be right: !Ref
Nonetheless, plainly a second route desk is added as an alternative of overriding the first route desk. I suppose that’s the way it at all times labored nevertheless it looks as if the route desk ought to have been changed.
This roadmap merchandise means that you need to create a customized useful resource and factors to somebody not everybody can learn (I discovered it elsewhere) however that looks as if lots of work for one thing that ought to be potential with out that choice.
I can carry out a piece round nevertheless it’s sort of annoying.
Teri Radichel
In case you preferred this story please clap and comply with:
Medium: Teri Radichel or Electronic mail Listing: Teri Radichel
Twitter: @teriradichel or @2ndSightLab
Requests companies 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
