Mapping Values are Not Allowed Here

Summary

Teri Radichel encountered a "Mapping Values are Not Allowed Here" error while updating a CloudFormation resource, which was resolved by correcting a missing property and addressing a separate issue with a !Ref directive in front of AWS::NoValue.

Abstract

While attempting to deploy a CloudFormation template, Teri Radichel faced an error message stating "Mapping Values are Not Allowed Here." This error was due to an accidentally deleted property name in the code. After identifying and correcting the missing property, Teri also discovered a related issue where a !Ref directive was required before AWS::NoValue for the policy to deploy successfully. The article includes screenshots for reference and invites readers to follow for updates, sign up for an email list, and explore additional content on cybersecurity careers, jobs, and troubleshooting CloudFormation error messages. Teri Radichel's expertise is highlighted through her authorship of cybersecurity books, presentations, awards, and certifications, as well as her company's services in penetration testing, security assessments, and consulting.

Opinions

Teri Radichel values the importance of proper code syntax and error message interpretation in CloudFormation deployments.
The author emphasizes continuous learning and sharing of knowledge by providing links to her series on Automating Cybersecurity Metrics and related stories on bugs, AWS security, secure code, and CloudFormation.
Teri encourages reader engagement and professional development through her email list, social media presence, and the offer of cybersecurity services.
The inclusion of personal achievements and company offerings suggests a belief in the significance of credibility and expertise in the field of cybersecurity.

Error trying to deploy a CloudFormation template

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I was trying to update a CloudFormation resource when I got the error message “Mapping Values are Not Allowed Here.”

I had copied and pasted some code and inadvertently deleted the name of the value I was trying to set — Conditions:

Now, although that solved my mapping problem, the policy wouldn’t deploy because I need a !Ref in front of AWS::NoValue also. But that’s a separate issue.

Follow for updates.

About Teri Radichel:
~~~~~~~~~~~~~~~~~~~~
⭐️ Author: Cybersecurity Books
⭐️ Presentations: Presentations by Teri Radichel
⭐️ Recognition: SANS Award, AWS Security Hero, IANS Faculty
⭐️ Certifications: SANS ~ GSE 240
⭐️ Education: BA Business, Master of Software Engineering, Master of Infosec
⭐️ Company: Penetration Tests, Assessments, Phone Consulting ~ 2nd Sight Lab

Need Help With Cybersecurity, Cloud, or Application Security?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
🔒 Request a penetration test or security assessment
🔒 Schedule a consulting call
🔒 Cybersecurity Speaker for Presentation

Follow for more stories like this:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
❤️ Sign Up my Medium Email List
❤️ Twitter: @teriradichel
❤️ LinkedIn: https://www.linkedin.com/in/teriradichel
❤️ Mastodon: @teriradichel@infosec.exchange
❤️ Facebook: 2nd Sight Lab
❤️ YouTube: @2ndsightlab

Mapping Values are Not Allowed Here — Missing Property

Error trying to deploy a CloudFormation template