# Problem with S3 Plugin

**URL:** <https://discuss.elastic.co/t/problem-with-s3-plugin/288714>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [November 9, 2021, 6:33am UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714 "2021-11-09T06:33:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajsuper2021](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajsuper2021/32/81472_2.png) [@rajsuper2021](https://discuss.elastic.co/u/rajsuper2021)\
**Post date:** [November 9, 2021, 6:33am UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714/1 "2021-11-09T06:33:50Z")

</div>

My current EFK logging configuration looks like this:

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
  name: efk
  namespace: logging
spec:
  version: 7.14.0
  secureSettings:
  - secretName: es-s3-backup-aws-creds
  nodeSets:
  - name: logging-cluster
    count: 3
    podTemplate:
      spec:
        initContainers:
        - name: install-plugins
          command:
          - sh
          - -c
          - |
            bin/elasticsearch-plugin install --batch repository-s3
    config:
      node.master: true
      node.data: true
      node.ingest: true
      node.store.allow_mmap: false
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 300Gi
        storageClassName: gp2

```

"es-s3-backup-aws-creds" is stored in logging namespace as a secret with my aws access + secrets keys

but I am getting this error when deploying this configuration using the ECK operator

```auto
java.lang.IllegalArgumentException: unknown secure setting [s3.client.secondary.secret_key] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:533)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:478)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:449)
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:420)
	at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:138)
	at org.elasticsearch.node.Node.<init>(Node.java:445)
	at org.elasticsearch.node.Node.<init>(Node.java:281)

```

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [November 9, 2021, 1:34pm UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714/2 "2021-11-09T13:34:05Z")

</div>

I am thinking the issue might be that you have not yet created a repository configuration in Elasticsearch that references your `secondary` client. So when the node boots up it sees these additional settings under the `secondary` key in the keystore and cannot place them and that's why it bails out. Try creating a snapshot repository via the API that references the `secondary` client.

> **[Client Settings | Elasticsearch Plugins and Integrations \[7.15\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/plugins/7.15/repository-s3-client.html)**

---

<div class="post-metadata">

**Author:** ![rajsuper2021](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajsuper2021/32/81472_2.png) [@rajsuper2021](https://discuss.elastic.co/u/rajsuper2021)\
**Post date:** [November 11, 2021, 1:41pm UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714/3 "2021-11-11T13:41:24Z")

</div>

Thank you @pebrc - i will try that out.

---

<div class="post-metadata">

**Author:** ![rajsuper2021](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajsuper2021/32/81472_2.png) [@rajsuper2021](https://discuss.elastic.co/u/rajsuper2021)\
**Post date:** [November 11, 2021, 9:00pm UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714/4 "2021-11-11T21:00:24Z")

</div>

@pebrc -

I am seeing this

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "repository_exception",
        "reason" : "[my_s3_repository] repository type [s3] does not exist"
      }
    ],
    "type" : "repository_exception",
    "reason" : "[my_s3_repository] repository type [s3] does not exist"
  },
  "status" : 500
}

```

here is my CRD yaml to deploy the ECK pods

```auto
apiVersion: elasticsearch.k8s.elastic.co/v1beta1
kind: Elasticsearch
metadata:
  name: efk
  namespace: logging
spec:
  version: 7.14.0
  nodeSets:
  - name: logging-cluster
    count: 1
    podTemplate:
      spec:
        initContainers:
        - name: install-plugins
          command:
          - sh
          - -c
          - |
            bin/elasticsearch-plugin install --batch repository-s3
    config:
      node.master: true
      node.data: true
      node.ingest: true
      node.store.allow_mmap: false
    volumeClaimTemplates:
    - metadata:
        name: elasticsearch-data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 300Gi
        storageClassName: gp2

```

for some reason its still not installing the s3 plugin on the ECK pods

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 9, 2021, 9:01pm UTC](https://discuss.elastic.co/t/problem-with-s3-plugin/288714/5 "2021-12-09T21:01:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.