Skip to content

Fix handling of empty SSEKMSKeyId parameter#33

Open
asafonov303 wants to merge 1 commit intoawslabs:mainfrom
asafonov303:set_sse_kms_key_better
Open

Fix handling of empty SSEKMSKeyId parameter#33
asafonov303 wants to merge 1 commit intoawslabs:mainfrom
asafonov303:set_sse_kms_key_better

Conversation

@asafonov303
Copy link

Ensure uploads of files smaller than 5MB succeed when no KMS key is specified.

In github.com/aws/aws-sdk-go-v2/service/s3 (c *Client) PutObject handles SSEKMSKeyId differently across versions:

  • v1.52.0 accepts a pointer to an empty string without issue
  • v1.91.1 requires nil; otherwise S3 responds with HTTP 400: "InvalidArgument: Server Side Encryption with AWS KMS managed key requires HTTP header x-amz-server-side-encryption : aws:kms"

Update code to pass nil when SSEKMSKeyId is not specified.

Apply the same change to (c *Client) CreateMultipartUpload, even though it does not currently cause errors.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ensure uploads of files smaller than 5MB succeed when no KMS key is
specified.

In github.com/aws/aws-sdk-go-v2/service/s3 (c *Client) PutObject handles
SSEKMSKeyId differently across versions:
- v1.52.0 accepts a pointer to an empty string without issue
- v1.91.1 requires nil; otherwise S3 responds with HTTP 400:
  "InvalidArgument: Server Side Encryption with AWS KMS managed key
  requires HTTP header x-amz-server-side-encryption : aws:kms"

Update code to pass nil when SSEKMSKeyId is not specified.

Apply the same change to (c *Client) CreateMultipartUpload, even though
it does not currently cause errors.
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 this pull request may close these issues.

1 participant