Generally you’ll get an encoded error message within the AWS console. That’s as a result of there are methods for attackers to insert code in these messages doubtlessly that might execute in your browser.
Nice however how do you view the message? You must decode it. However you don’t decode it with base64 or another command line device, you employ the AWS CLI and the sts decode-authorization-message command.
Initially save your message to a variable like this:
msg="copy and paste the encoded message right here"
Then run the sts command to decode the worth like this:
aws sts decode-authorization-message --encoded-message "$msg" --output textual content
I nonetheless discover {that a} bit laborious to learn so I truly add some further sed instructions on the finish to weed out among the JSON formatting.
aws sts decode-authorization-message --encoded-message "$msg" --output textual content | sed 's/,/nr/g' | sed 's/ sed 's///g' | sed 's/"//g'
Then a minimum of it’s a bit extra readable:
Whether or not it’s useful or not — you may determine for your self 🙂 I’m writing about this specific output in my different weblog collection:
Teri Radichel
When you favored this story please clap and comply with:
Medium: Teri Radichel or E-mail Record: Teri Radichel
Twitter: @teriradichel or @2ndSightLab
Requests providers through LinkedIn: Teri Radichel or IANS Analysis
© 2nd Sight Lab 2022
____________________________________________
Writer:
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