Skip to content
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

S3Proxy is not compatible with official AWS' extended library #300

Closed
bwiercinski opened this issue May 8, 2023 · 0 comments · Fixed by #301
Closed

S3Proxy is not compatible with official AWS' extended library #300

bwiercinski opened this issue May 8, 2023 · 0 comments · Fixed by #301
Assignees

Comments

@bwiercinski
Copy link
Collaborator

pass4s is sending following payload on the SQS if the message is considered large:

{"s3BucketName": "bucket", "s3Key": "key"}

This format is not compatible with the official AWS' extended client which is putting a message with the following format:

["software.amazon.payloadoffloading.PayloadS3Pointer", {"s3BucketName": "bucket", "s3Key": "key"}]

S3Proxy Addon was designed from the beginning to be compatible, so I would consider it as a bug.

Another difference is with message attributes, but this is less important as the attribute is optional I think:

pass4s:
-{"ExtendedPayloadSize":{"StringValue":"22","DataType":"String"}}
aws extended client:
+{"ExtendedPayloadSize":{"StringValue":"22","DataType":"Number"}}
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 a pull request may close this issue.

1 participant