Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Content]: Possible outdated query; ran into error when utilizing without extra flag #3617

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

Closed
jpang007 opened this issue Oct 6, 2022 · 0 comments · Fixed by #3643
Closed
Assignees
Labels
content When the bug is about content that needs to get fixed triaged

Comments

@jpang007
Copy link
Contributor

jpang007 commented Oct 6, 2022

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.
Screen Shot 2022-10-06 at 5 42 56 PM

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

@jpang007 jpang007 added content When the bug is about content that needs to get fixed triage labels Oct 6, 2022
@markzegarelli markzegarelli self-assigned this Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants