avatarTeri Radichel

Summary

The web content discusses troubleshooting an AWS CLI error message related to missing credentials and suggests using role_arn instead of role in the configuration.

Abstract

The article addresses a common issue encountered when using the AWS CLI, where users receive an error message indicating that credentials cannot be located. The author, Teri Radichel, explains that this error can occur when configuring a role profile that assumes an AWS role but references an incorrect configuration option. Instead of using role, the correct configuration should be role_arn. Radichel emphasizes the importance of clear error messages and points out that a more precise message would help users correct such configuration mistakes more efficiently. The post also provides resources for further reading on AWS IAM, cybersecurity careers, and other related topics, and invites readers to follow the author for updates and to access more content on cybersecurity.

Opinions

  • The author finds the AWS CLI error message confusing when the actual issue is the use of role instead of role_arn in the configuration.
  • Radichel suggests that a better error message would improve the user experience by directly indicating the incorrect configuration option and providing the correct one.
  • The author promotes their series on automating cybersecurity metrics, emphasizing the value of their content with references to their expertise, certifications, and recognition in the field.
  • Radichel encourages engagement by inviting readers to sign up for an email list, follow on social media, and explore additional cybersecurity resources provided in the article.

Unable to locate credentials. You can configure credentials by running “aws configure”.

Error message is confusing under these circumstances

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

⚙️ Check out my series on Automating Cybersecurity Metrics | Code.

🔒 Related Stories: Bugs | AWS Security | Secure Code | CloudFormation

💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List

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

I’ve written numerous blog posts on different methods of creating AWS CLI Profiles and assuming roles here:

The thing that is confusing is that I’m creating a role profile configuration that assumes a role and references a source profile for the credentials.

Now if I had a typo in the name of the source profile or forgot to configure the credentials this might make sense.

However, the problem was in this case that I used the configuration:

role = 

instead of

role_arn = 

Perhaps a better error message would be:

Invalid configuration option: role. Did you mean role_arn?

Follow for updates.

Teri Radichel | © 2nd Sight Lab 2023

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
Role
Aws Configure
Unable To Locate
Credentials
Aws Cli
Recommended from ReadMedium