Fix documentation for ec2 import-key-pair for how to properly base64-encode keyfiles #3129
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
…with CLI V2, and how it processes binary input types.
This was referenced Feb 29, 2024
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.
Fixes the long-running confusion around base64-encoding and CLI V2:
AWS CLI V2 changed how it processes binary input types.
This means the CLI documentation was now incorrect - the CLI won't automatically do the base64 encoding for you when calling
aws ec2 import-key-pair- you need to explicitly callfileb://yourself.Very small doc change, which should hopefully reduce confusion - let me know if I've missed something.