Clarify JSON array ingestion behavior for S3 log files#1086
Merged
estherk15 merged 2 commits intoMar 26, 2026
Conversation
Adds a troubleshooting section explaining that JSON arrays in S3 log files are ingested as a single event and that NDJSON format is required for separate log entries. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
maycmlee
approved these changes
Mar 26, 2026
Contributor
maycmlee
left a comment
maycmlee
left a comment
There was a problem hiding this comment.
Just a tiny suggestion, but approving!
Co-authored-by: May Lee <mayl@alumni.cmu.edu>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a troubleshooting subsection to the Forwarder README clarifying that S3 log files containing JSON arrays are ingested as a single log event, and that newline-delimited JSON (NDJSON) is required to ingest each entry as a separate event.
Motivation
Customers sending logs from S3 via the Lambda Log Forwarder have encountered unexpected behavior when their log files contain JSON arrays. The current documentation states that logs must be in JSON format but does not specify that JSON arrays are treated as a single event. This change surfaces that requirement upfront to help users avoid ingestion issues.
Testing Guidelines
No functional changes — documentation update only.
Additional Notes
This change was requested in DOCS-13685 based on customer feedback.
Types of changes