# S3 compatible storage are not able to mounted for snapshot **URL:** \ **Category:** Elasticsearch\ **Tags:** snapshot-and-restore\ **Created:** [May 21, 2026, 1:02pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444 "2026-05-21T13:02:27Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Rajesh\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajesh_kannan/32/47154_2.png) [@Rajesh\_Kannan](https://discuss.elastic.co/u/Rajesh_Kannan)\ **Post date:** [May 21, 2026, 1:02pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/1 "2026-05-21T13:02:28Z")
We are trying to mount the s3 storage( S3 compatible DataCore (caringo)) bucket on elastic 9.3.0 using the below command and we are getting "s3\_exception: A header you provided implies functionality that is not implemented. (Service: S3, Status Code: 501, Request ID: 286BE1B0D952065D) (SDK Attempt Count: 1)" ```auto PUT \_snapshot/backup-s3-repository?verify=true { "type": "s3", "settings": { "bucket": "-es-backup", "base_path": "elasticsearch-backups", "endpoint": "http://swarm.com", "protocol": "http", "path_style_access": true, "access_key": "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*", "secret_key": "\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*", "max_retries": 15, "disable_chunked_encoding": true, "register_operation_disabled": true } } ``` Also i tried added these parameters in `elasticsearch.yml` ```auto s3.client.default.path_style_access: true s3.client.default.read_timeout: 50s ``` Can someone help whether DataCore (caringo) is supported for S3 backup ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [May 21, 2026, 1:25pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/2 "2026-05-21T13:25:49Z")
Hi @Rajesh_Kannan I suggest you read this in detail > **[S3-compatible services - S3 repository | Elastic Docs](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore/s3-repository#repository-s3-compatible-services)** > > There are a number of storage systems that provide an S3-compatible API, and the s3 repository type allows you to use these systems in place of AWS S3. To do so, you should set the s3.client.CLIENT\_NAME.endpoint setting to the system's endpoint. This... And did you run the following analyzer as suggested? > **[Analyze a snapshot repository | Elasticsearch API documentation](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze)** > > Performs operations on a snapshot repository in order to check for incorrect behaviour. > There are a large number of third-party storage systems available, not all of which are s... ---
**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\ **Post date:** [May 21, 2026, 1:51pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/3 "2026-05-21T13:51:03Z")
I agree that the analyze repository tool that @stephenb linked would be a good thing to try. It might give you a more useful error message. I suspect that DataCore doesn't support if-none-match headers on a put object request, and that you'll need to set [`unsafely_incompatible_with_s3_conditional_writes`](https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/s3-repository-settings#repository-s3-repository-settings) to true for your repository. I've never used DataCore though, so I don't know if that will actually help, or if you'll run into other problems after that. ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [May 21, 2026, 3:19pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/4 "2026-05-21T15:19:02Z")
> [@Keith\_Massey](#): > > you'll need to set [`unsafely_incompatible_with_s3_conditional_writes`](https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/s3-repository-settings#repository-s3-repository-settings) to true Might be worth noting this option is now marked as deprecated, exactly one minor release after it was Generally Available. Personally, I'd take very careful note of the wording in the documentation. > (boolean) Elasticsearch uses AWS S3's [support for conditional writes](https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-writes.html) to protect against repository corruption. If your repository is based on a storage system which claims to be S3-compatible but does not accept conditional writes, set this setting to `true` to make Elasticsearch perform unconditional writes, _bypassing the repository corruption protection, while you work with your storage supplier to address this incompatibility with AWS S3_. Defaults to `false`. Are you really working with DataCore on this specific incompatibility with S3 ? ---
**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\ **Post date:** [May 21, 2026, 3:35pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/5 "2026-05-21T15:35:09Z")
> [@RainTown](#): > > Might be worth noting this option is now marked as deprecated, exactly one minor release after it was Generally Available. I'm thinking this might be a bug in the documentation. The setting is not marked as deprecated [in the code](https://github.com/elastic/elasticsearch/blob/v9.4.1/modules/repository-s3/src/main/java/org/elasticsearch/repositories/s3/S3Repository.java#L240-L243). I'm trying to track where this deprecation came from. The name of the setting though definitely implies that this is not our first choice in how we want to interact with a repository. ---
**Author:** ![Keith\_Massey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/keith_massey/32/83666_2.png) [@Keith\_Massey](https://discuss.elastic.co/u/Keith_Massey)\ **Post date:** [May 21, 2026, 3:41pm UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/6 "2026-05-21T15:41:09Z")
I was wrong. That setting was [intentionally deprecated](https://github.com/elastic/docs-content/pull/4992). So be careful using it -- it is subject to be removed in the next major version. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 22, 2026, 8:00am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/7 "2026-05-22T08:00:16Z")
> [@RainTown](#): > > this option is now marked as deprecated, exactly one minor release after it was Generally Available It should have been marked as deprecated as soon as it was released, but the docs system doesn't allow that yet. In any case yes this is an unsafe option that might enable a temporary workaround but it's only necessary if your storage isn't actually S3-compatible and you need to get your supplier to fix the incompatibility ASAP as it is putting your data at risk. ---
**Author:** ![Mamta\_Bankoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mamta_bankoti/32/140518_2.png) [@Mamta\_Bankoti](https://discuss.elastic.co/u/Mamta_Bankoti)\ **Post date:** [May 22, 2026, 10:26am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/8 "2026-05-22T10:26:13Z")
DataCore (Caringo Swarm) is only partially S3 compatible, so it does not support some features required by Elasticsearch 9.3. That is why the 501 error is coming. The issue is with compatibility, not the command or configuration. ---
**Author:** ![Rajesh\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rajesh_kannan/32/47154_2.png) [@Rajesh\_Kannan](https://discuss.elastic.co/u/Rajesh_Kannan)\ **Post date:** [May 23, 2026, 3:48am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/9 "2026-05-23T03:48:07Z")
Is there any settings or headers need to modify at Datacore? ---
**Author:** ![Mamta\_Bankoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mamta_bankoti/32/140518_2.png) [@Mamta\_Bankoti](https://discuss.elastic.co/u/Mamta_Bankoti)\ **Post date:** [May 26, 2026, 9:52am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/10 "2026-05-26T09:52:41Z")
There are no specific headers or Datacore settings to fix this. The issue is due to S3 compatibility limitations between DataCore (Caringo Swarm) and Elasticsearch 9.3. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [May 26, 2026, 10:32am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/11 "2026-05-26T10:32:56Z")
> [@Mamta\_Bankoti](#): > > The issue is due to S3 compatibility limitations between DataCore (Caringo Swarm) and Elasticsearch 9.3. No, the issue is due to S3 compatibility limitations between DataCore and AWS S3 itself, i.e. the storage in question is not S3-compatible. Elasticsearch is not involved in that problem. ---
**Author:** ![Mamta\_Bankoti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mamta_bankoti/32/140518_2.png) [@Mamta\_Bankoti](https://discuss.elastic.co/u/Mamta_Bankoti)\ **Post date:** [May 27, 2026, 11:05am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444/12 "2026-05-27T11:05:50Z")
> [@DavidTurner](#): > > No, the issue is due to S3 compatibility limitations between DataCore and AWS S3 itself, i.e. the storage in question is not S3-compatible. Elasticsearch is not involved in that problem. Thanks for the clarification. Understood that the issue is related to S3 compatibility limitations between DataCore and AWS S3, and that the storage is not fully S3-compatible. Also noted that Elasticsearch is not involved in this case.... 😀