Was wondering if there are any technical limitations for supporting the BucketKeyEnabled argument on upload_file? It is already supported by put_object and the multi-part upload APIs, which I would assume upload_file calls under the hood.
It is mentioned in this blog: https://aws.amazon.com/blogs/storage/reduce-encryption-costs-by-using-amazon-s3-bucket-keys-on-existing-objects/ that BucketKeyEnabled is not supported. Based on the patch in the repository mentioned in that blog, it looks like a one liner change: simon-data/s3transfer@02eb942
So wanted to know if there was any reason why this never got pulled into the official release?
Was wondering if there are any technical limitations for supporting the
BucketKeyEnabledargument onupload_file? It is already supported byput_objectand the multi-part upload APIs, which I would assumeupload_filecalls under the hood.It is mentioned in this blog: https://aws.amazon.com/blogs/storage/reduce-encryption-costs-by-using-amazon-s3-bucket-keys-on-existing-objects/ that
BucketKeyEnabledis not supported. Based on the patch in the repository mentioned in that blog, it looks like a one liner change: simon-data/s3transfer@02eb942So wanted to know if there was any reason why this never got pulled into the official release?