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
Just using sigv4 shouldn't require changes, but the backend made a
couple of extra requirements alongside changing to sigv4 - requiring
headers for tagging and encryption.
Signed-off-by: Ashley Davis <ashley.davis@cyberark.com>
// Read [Checking object integrity for data uploads in Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity-upload.html),
104
112
// to learn more.
105
-
//
106
-
// TODO(wallrj): There is a bug in the AWS backend:
107
-
// [S3 Presigned PutObjectCommand URLs ignore Sha256 Hash when uploading](https://github.com/aws/aws-sdk/issues/480)
108
-
// ...which means that the `x-amz-checksum-sha256` request header is optional.
109
-
// If you omit that header, it is possible to PUT any data.
110
-
// There is a work around listed in that issue which we have shared with the
0 commit comments