<p dir="auto"><strong>Describe the feature</strong>:</p>
<p dir="auto">Currently, by setting server_side_encryption to true, the only method that is allowed is aes256. It would be great if we could specify other s3 encryption methods, e.g. aws:kms.</p>
<p dir="auto">For aws:kms, if the bucket has a default key, it's just a matter of including the correct header, so one possibility may be an additional parameter to specify the value of the <code class="notranslate">x-amz-server-side-encryption</code> header to get sent with requests. But the ability to specify an ams key to use would also be great.</p>
<p dir="auto"><strong>Describe the feature</strong>: We'd like to store the snapshots of our elastic database in the aws bucket secured with the KMS server-side encryption. There already is a stale merge request (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="241472324" data-permission-text="Title is private" data-url="https://github.com/elastic/elasticsearch/issues/25620" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/25620/hovercard" href="https://github.com/elastic/elasticsearch/pull/25620">#25620</a>) and we are considering working on this feature, but only if you guys are keen in merging the change upstream.<br>
Can you guys give us any clues with regards to your release schedules and when we could expect the changes end up in the mainline if we provide the patch in the following days?</p>