The Outputs section contains duplicate Export names

Summary

The web content discusses the necessity of having unique export names in CloudFormation outputs to avoid duplication errors.

Abstract

The article emphasizes the importance of unique names for CloudFormation outputs, which are values returned by a CloudFormation template after execution. The author, Teri Radichel, shares a personal experience of encountering an error due to duplicate names in the outputs section and provides a corrected example. The piece also includes a screenshot illustrating the error and the resolution. Additionally, Radichel offers resources for further learning in cybersecurity, including her own books, presentations, and services provided by her company, 2nd Sight Lab. She also invites readers to follow her on various platforms and to try out an AI service called ZAI.chat, which she recommends for its cost-effective alternative to ChatGPT Plus (GPT-4).

Opinions

The author believes that the error message regarding duplicate output names in CloudFormation is clear and should be easily understood.
Teri Radichel values the sharing of knowledge and experience, as evidenced by her series on automating cybersecurity metrics and her invitation to sign up for her email list.
She suggests that her readers can benefit from the AI service ZAI.chat, implying it is a valuable tool for those interested in AI capabilities similar to ChatGPT Plus but at a lower cost.
The author's credentials, including her awards, certifications, and role as a cybersecurity speaker, indicate a strong endorsement of her expertise in the field.

CloudFormation outputs need to have unique names

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

Each CloudFormation template can have outputs — values that the function returns after it runs. You can see the outputs for a CloudFormation stack in the console or query them with the CLI, for example.

Hopefully this error message is pretty obvious but each output needs a unique name. Here’s my outputs section in my template:

The error that I had is that the value for the last two Name: properties was the same:

!Sub 'CloneUrlHttp-${NameParam}

As you can see I’ve corrected that in the above block of code. Every value after Name: is different (unique).

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