# Snapshot to IBM S3 compatible object storage

**URL:** <https://discuss.elastic.co/t/snapshot-to-ibm-s3-compatible-object-storage/157603>\
**Category:** Elasticsearch\
**Created:** [November 20, 2018, 6:57pm UTC](https://discuss.elastic.co/t/snapshot-to-ibm-s3-compatible-object-storage/157603 "2018-11-20T18:57:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sszabo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sszabo/32/36570_2.png) [@sszabo](https://discuss.elastic.co/u/sszabo)\
**Post date:** [November 20, 2018, 6:57pm UTC](https://discuss.elastic.co/t/snapshot-to-ibm-s3-compatible-object-storage/157603/1 "2018-11-20T18:57:51Z")

</div>

Is it possible to snapshot to IBM object store which is S3 compatible?

```
curl -s -XPUT http://hostname:9200/_snapshot/filebeat20180110 -H 'Content-Type: application/json' -d'
{
  "type": "s3",
  "settings": {
    "endpoint": "http://s3.tor01.objectstorage.service.networklayer.com/",
    "region": "tor01-standard",
    "bucket": "my-bucket",
    "compress": "true"
  },
  "indices": "filebeat-2018.01.10"
}'

```

This error seems to come from amazon not IBM:

amazon\_s3\_exception:  
The AWS Access Key Id you provided does not exist in our records.  
Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId

When I use an invalid endpoint it fails for the above reason, I would expect it to fail with bad hostname or something similar.

---

<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 18, 2018, 6:58pm UTC](https://discuss.elastic.co/t/snapshot-to-ibm-s3-compatible-object-storage/157603/2 "2018-12-18T18:58:07Z")

</div>

Closed on December 18, 2018, 6:58pm UTC

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