-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 kms has 'utf8' codec can't decode byte error #1001
Comments
Also, in case the awscli module version isn't sufficient. $> aws --version
aws-cli/1.6.1 Python/2.7.6 Darwin/13.4.0 |
Pretty sure this is due to it decoding the Base64-encoded keys and random data and trying to re-format the result as JSON or text. |
Working on a fix now. Just to give a little more background on what's going on, this appears to be a regression from earlier versions from of the AWS CLI. Typically, an AWS service response will return binary data base64 encoded. What the various AWS SDKs then do is decode the base64 data to then get the actual binary contents. What the AWS CLI has historically done is take the base64 encoded response from the server and not decoded it. Instead we print the base64 contents directly to stdout, and the user can then base64 decode the contents when they need the actual binary contents. However, in recent versions of the AWS CLI we are actually decoding the base64 contents which will then either
What I'd propose, and plan on implementing, is putting back the old behavior (and fixing the regression) such that binary content is always printed as base64 encoded. |
This fixes aws#1001. This also fixes a regression we had when displaying binary content. As mentioned on the github issue, we were previously always showing binary content as base64 encoded. This PR adds back this behavior. In addition, this also gives us a hook into changing the timestamp parsing so we can later add a config option to unify the way timestamps are displayed. Also fixes aws#970, and closes aws#1005. I've also added an integration test for aws#1001 to ensure we are in fact displaying a response that can be printed to stdout.
Looks like this one might be back?
|
I upgraded the awscli this afternoon to try and take advantage of the new kms system. I'm getting the following error when I try to use the cli.
pip modules installed:
I'm on OS X 10.9.5
The text was updated successfully, but these errors were encountered: