# Opensearch 2.16 snapshot to s3 repository using repository-s3 plugin

**URL:** <https://forum.opensearch.org/t/opensearch-2-16-snapshot-to-s3-repository-using-repository-s3-plugin/27520>\
**Category:** Index Management\
**Tags:** index-management\
**Created:** [November 21, 2025, 11:33am UTC](https://forum.opensearch.org/t/opensearch-2-16-snapshot-to-s3-repository-using-repository-s3-plugin/27520 "2025-11-21T11:33:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [November 21, 2025, 11:40pm UTC](https://forum.opensearch.org/t/opensearch-2-16-snapshot-to-s3-repository-using-repository-s3-plugin/27520/2 "2025-11-21T23:40:38Z")

</div>

@erdna Did you deploy your OpenSearch cluster with official OpenSearch Helm charts?

Take a look at my previous comments on the same error.

> [@Issue with Configuring repository-s3 Plugin in OpenSearch Helm Deployment](https://forum.opensearch.org/t/issue-with-configuring-repository-s3-plugin-in-opensearch-helm-deployment/23400/2):
>
> @swetha AWS access and secret keys must be placed in opensearch.keystore as per OpenSearch documentation. To achieve that in OpenSearch helm you must create a secret with access and secret keys and pass it as keystore element in values.yml Please bear in mind that both key and secret must be encoded with base64 before adding to Secret manifest. apiVersion: v1 kind: Secret metadata: name: aws-credentials type: Opaque data: s3.client.default.access\_key: \<encoded key with base64\> s3.clie…

---

_[View the full topic](https://forum.opensearch.org/t/opensearch-2-16-snapshot-to-s3-repository-using-repository-s3-plugin/27520)._