# Repository verification exception while using S3 repo

**URL:** <https://discuss.elastic.co/t/repository-verification-exception-while-using-s3-repo/306649>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [June 8, 2022, 7:51am UTC](https://discuss.elastic.co/t/repository-verification-exception-while-using-s3-repo/306649 "2022-06-08T07:51:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pallavi\_Chaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pallavi_chaudhari/32/97757_2.png) [@Pallavi\_Chaudhari](https://discuss.elastic.co/u/Pallavi_Chaudhari)\
**Post date:** [June 8, 2022, 7:51am UTC](https://discuss.elastic.co/t/repository-verification-exception-while-using-s3-repo/306649/1 "2022-06-08T07:51:23Z")

</div>

Hi All,

I am trying to use s3 plugin for backup and restore, please find the details below

1. I have create IBM COS bucket which is s3 compatible and created access and secret key
2. I have added s3.client.default.endpoint to IBM S3 bucket endpoint in Elasticsearch.yaml
3. i have added  
s3.client.default.access\_key  
s3.client.default.secret\_key

but while verifying the bucket, i am getting following issue

`The AWS Access Key ID you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; S3 Extended Request ID: null)"`

Can someone please suggest, what might be going wrong here?  
Am i missing on something or IBM COS is not supported with S3 plugin?

JFYI - the ES is 3 node cluster hosted on k8s

Thanks  
Pallavi C

---

<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:** [July 6, 2022, 7:51am UTC](https://discuss.elastic.co/t/repository-verification-exception-while-using-s3-repo/306649/2 "2022-07-06T07:51:39Z")

</div>

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