New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS CLI v2 - Cannot import certificate, certificate chain base64 not accepted, but valid #4978
Comments
Ditto it looks like a python base64.py issue File "awscli/customizations/binaryformat.py", line 59, in _visit_scalar
File "base64.py", line 87, in b64decode
binascii.Error: Incorrect padding |
Created a pull request #4981 - seems to work based on this gist |
This is due to how cli v2 changed processing binary inputs to support round tripping values by default. You can read about the change here: https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam and either update to using fileb:// instead, or revert to the previous behavior with the configuration option. |
To address issue mentioned here: aws/aws-cli#4978
Following this guide failed due to this https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-binaryparam and this aws/aws-cli#4978
Fix for AWS CLI v2 to handle bug aws/aws-cli#4978
is this fixed, coz i'm still getting this error! |
Upload the certificate to AWS ACMaws acm import-certificate --certificate fileb://certificate.pem --private-key fileb://privatekey.pem --certificate-chain fileb://chain.pem --profile default --region us-west-2 |
While trying to import a certificate to ACM using CLI v2, I get an error that my certificate chain contains invalid base64:
However, importing the same ca.crt works fine with CLI v1:
ca.crt has been created using the latest easy-rsa from Github, on AL2.
The text was updated successfully, but these errors were encountered: