Decode Account IDs from access keys. #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
875cf6d to
fe74eed
Compare
fe74eed to
a9dd1d7
Compare
3039598 to
01f722e
Compare
01f722e to
8e4e4f9
Compare
8e4e4f9 to
9266f62
Compare
AzySir
approved these changes
Oct 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
New Feature! adds the ability to decode the account number from access keys and will add a new env var AWS_ACCOUNT_ID to
execandenvcommands, also adds adecodecommand that I may remove later depending on how I feel. Caveat AWS may change how the account number is encoded in the future so its more of a guess.To test run
awskeyring decode AKIA.....(what ever your access key is) and see if you get the correct account number matchingaws sts get-caller-identity.Did you run the Tests?