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
What part(s) of the article would you like to see updated?
I believe there is an outdated command on this help guide which took me some time to figure out. In step 5, #2 the documentation gives us a long command to test out the lambda function from the Amazon CLI. However, when running the command as is, I got the following error.
An error occurred (InvalidRequestContentException) when calling the Invoke operation: Could not parse request body into json: Could not parse payload into json: Invalid UTF-8 middle byte 0x28.
After some searching I found this medium article that suggests adding the following tag at the end of the CLI command:
--cli-binary-format raw-in-base64-out
After adding this command, I was successfully able to test the command and I saw the appropriate result reflected in my Segment AWS S3 source.
Additional information
No response
The text was updated successfully, but these errors were encountered:
What article on segment.com/docs is affected?
https://segment.com/docs/connections/sources/catalog/cloud-apps/amazon-s3/
What part(s) of the article would you like to see updated?
I believe there is an outdated command on this help guide which took me some time to figure out. In step 5, #2 the documentation gives us a long command to test out the lambda function from the Amazon CLI. However, when running the command as is, I got the following error.

An error occurred (InvalidRequestContentException) when calling the Invoke operation: Could not parse request body into json: Could not parse payload into json: Invalid UTF-8 middle byte 0x28.
After some searching I found this medium article that suggests adding the following tag at the end of the CLI command:
--cli-binary-format raw-in-base64-out
After adding this command, I was successfully able to test the command and I saw the appropriate result reflected in my Segment AWS S3 source.
Additional information
No response
The text was updated successfully, but these errors were encountered: