Skip to content

fix(aws_s3 source): keep EventBridge S3 object keys as sent - #52

Merged
sundaresanr merged 1 commit into
v0.54.0-exaforcefrom
sundar/aws-s3-eventbridge-notifications
Nov 5, 2026
Merged

sundaresanr merged 1 commit into
v0.54.0-exaforcefrom
sundar/aws-s3-eventbridge-notifications

Conversation

@sundaresanr

Copy link
Copy Markdown

EventBridge does not URL-encode the object key, unlike native S3 notifications. Decoding it changed keys that contain "+" or "%", so GetObject requested an object that does not exist.

Give the EventBridge detail its own object type with a plain key, and copy the key unchanged into the S3 event record. Native notifications still decode their keys.

EventBridge does not URL-encode the object key, unlike native S3
notifications. Decoding it changed keys that contain "+" or "%", so
GetObject requested an object that does not exist.

Give the EventBridge detail its own object type with a plain key, and
copy the key unchanged into the S3 event record. Native notifications
still decode their keys.
@sundaresanr
sundaresanr merged commit 6c10979 into v0.54.0-exaforce Nov 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants