S3 ServerSideEncryption with KMS key ID

Summary I would like to build on top of At my work we're forced to use customer provided KMS keys to encrypt our data at rest in S3. So in order to CRUD the S3 bucket we need to provide the KMS key ID. Basically we'd have to add SSEKMSKeyId to the AWS SDK Commands in the S3 storage driver. For e.g. here: Basic Example _No response_ Motivation We would be able to handle more S3 KMS edge cases which are often the norm in bigger companies. Detailed Design Add SSEKMSKeyId | SSECustomerKey to the DriverS3Config and use that when communicating with S3, if defined and ServerSideEncryption == 'aws:kms' Requirements List Must Have: • Support for the SSEKMSKeyId and SSECustomerKey attribute in the aws sdk CommandInputs when ServerSideEncryption is 'aws:kms' Could have: • Additional configuration in the ENV vars that are mapped and append to the CommandInputs as additional parameters Drawbacks There are no drawbacks. We, and probably o…