Closed albertjannap closed 3 months ago
The error message indicates that this is a client side bug.
The client sdk must provide sse-c headers in all the requests that it wants to send for the object it wants to encrypt via client provided keys.
You should open a bug report on the relevant client implementation not the server.
Description
I am trying to stream a 111MB xlsx file, using putObject, to MinIO and I am using SSE-C encryption
Expected Behavior
I expect that the file will upload without any memory issues or in this case errors about wrong configuration about encryption.
Current Behavior
I receive an error:
S3Error: The multipart upload initiate requested encryption. Subsequent part requests must include the appropriate encryption parameters.
. For not multipart requests the upload is successfulPossible Solution
In
uploadStream
a request is made to upload a part, I think the configuration for this request is wrong, the headers you configure when you callputObject
are not being passed for this request. Maybe it could be a possible solution.Steps to Reproduce (for bugs)
putObject
to upload a file(buffer) larger then 100 MBContext
I am trying to upload this file to temporary store it in a bucket, in a later moment in time I want to process the xlsx file to import the data to Salesforce. This has impact on my work because I need to store the file with the encryption headers.
Regression
Is this issue a regression? No
Your Environment