Alex Woods

We're looking into how we can more gracefully handle or expose this information. However, in the meantime the correct bucket region is exposed through the response headers which are available...

Hey - yeah this is unfortunately a known limitation (see #2397). I wasn't aware of the `usedforsecurity` option - if we can find support (or if its eventually added) to...

There are upcoming changes that will add support for using user defined/flexible checksums, see: #2667. This is just the start, as operations/services need to add support for this trait, but...

An now, with version 1.113.0 of `aws-sdk-s3`, S3 now supports setting flexible checksums - allowing you to avoid using md5 and use instead another, user selected checksum. See: * [AWS...

Thanks for submitting this - I think its a valuable feature request and something the SDK should likely support natively.

We could implement it by using a block for defaults on Aws.config eg, when defining it: ```ruby # lib/aws-sdk-core.rb @config = Hash.new { |hash, key| hash[key] = Aws.shared_config.send(key) if Aws.shared_config.respond_to?(key)...

Whats the actual bucket name you're using? The issue here I believe is that in the FIPS regions, the bucket needs to be the endpoint host prefix, but the uri...

Just a thought on this - rather than trying to fix this through adding additional configuration, could you instead fix this by creating a new instance of `InstanceProfileCredentials` or explicitly...

Unfortunately we don't support multipart upload with client side encryption. There are additional complexities to ensure that client side encryption applied to multipart upload is both secure and correct. I'd...

If you're getting the same error on all operations you attempt on the bucket, make sure you have constructed the resource with a client with the correct region. eg: ```ruby...