You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Getting the instance serial console log produces encoding error #5558
Hi @rabits, thanks for opening. I think I've encountered this before (#4778). The current solution is to enable UTF-8 as in the Windows system locale, as described here:
Hi @kdaily , yeah I think it's related - but in my case I have no way to rule the host locale. My application just uses the current aws installation. I think the AWS tool should work properly in all the locales available on the host platform, but that's great to know there is a workaround. Thank you
...if you use Windows with default encoding CP1252, setting AWS_CLI_FILE_ENCODING=UTF-8 would make CLI ignore locale encoding and open text files using UTF-8.
Based on that I believe this issue can be closed. If the above solution does not work please let us know here or create a new issue and we can revisit this. Thanks!
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
kdaily commentedon Sep 28, 2020
Hi @rabits, thanks for opening. I think I've encountered this before (#4778). The current solution is to enable UTF-8 as in the Windows system locale, as described here:
https://stackoverflow.com/questions/57131654/using-utf-8-encoding-chcp-65001-in-command-prompt-windows-powershell-window/57134096#57134096
rabits commentedon Sep 28, 2020
Hi @kdaily , yeah I think it's related - but in my case I have no way to rule the host locale. My application just uses the current aws installation. I think the AWS tool should work properly in all the locales available on the host platform, but that's great to know there is a workaround. Thank you
kdaily commentedon Sep 28, 2020
Agree! As noted in the other post is that
set PYTHONIOENCODING=UTF-8works for the V1 client, but not V2. This needs to be investigated.tim-finnigan commentedon Nov 2, 2022
This error has been previously reported a few times. For the AWS CLI v2 I think #5086 addresses the issue, specifically in this comment.
You can find a section on Locale here in the AWS CLI documentation. For Windows it notes:
Based on that I believe this issue can be closed. If the above solution does not work please let us know here or create a new issue and we can revisit this. Thanks!
github-actions commentedon Nov 2, 2022
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.