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

commandInput options not passed to CompleteMultipartLocalObjectCommand #59

Open
jstastny opened this issue Oct 6, 2023 · 1 comment

Comments

@jstastny
Copy link

jstastny commented Oct 6, 2023

We use server side encryption with customer keys and therefore set the SSECustomerAlgorithm and SSECustomerKey in the commandInput argument. This works great with everything except multipart uploads.

This is caused by the CompleteMultipartLocalObjectCommand not using the commandInput in CompleteMultipartLocalObjectCommand. The CreateMultipartLocalObjectUploadCommand that calls the complete command upon completion uses the additional headers properly, but does not pass them on to the Complete command.

@jstastny
Copy link
Author

jstastny commented Oct 6, 2023

I was probably wrong about the root cause. The error message I am getting is: InvalidRequest: The multipart upload initiate requested encryption. Subsequent part requests must include the appropriate encryption parameters. and the stack trace mentions /src/commands/UploadLocalObjectPartCommand.ts:76:24 as the last location in the s3-sync-client library.

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

No branches or pull requests

1 participant