You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
We use server side encryption with customer keys and therefore set the
SSECustomerAlgorithm
andSSECustomerKey
in thecommandInput
argument. This works great with everything except multipart uploads.This is caused by the
CompleteMultipartLocalObjectCommand
not using thecommandInput
inCompleteMultipartLocalObjectCommand
. TheCreateMultipartLocalObjectUploadCommand
that calls the complete command upon completion uses the additional headers properly, but does not pass them on to theComplete
command.The text was updated successfully, but these errors were encountered: