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 call fileb:// yourself.
Very small doc change, which should hopefully reduce confusion - let me know if I've missed something.
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.