If you are using the AWS CLI and experience an Invalid base64 exception, the cause is the same as the Invalid UTF-8 middle byte 0x28 exception mentioned in my other post http://catamountcloud.com/2020/12/27/aws-invalid-utf-8-middle-byte-0x28/
Again, you have two options to address
- revert to using v1 of the CLI
- add ‘–cli-binary-format raw-in-base64-out’ to your command if sticking with v2
v2 is recommended by AWS. Here is a list of the breaking changes when moving from v1 to v2:
https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html
