# Cannot Register Snapshot Repository for S3 compliant (backblaze) service

**URL:** <https://discuss.elastic.co/t/cannot-register-snapshot-repository-for-s3-compliant-backblaze-service/365581>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [August 27, 2024, 12:00am UTC](https://discuss.elastic.co/t/cannot-register-snapshot-repository-for-s3-compliant-backblaze-service/365581 "2024-08-27T00:00:43Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**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:** [August 28, 2024, 8:56pm UTC](https://discuss.elastic.co/t/cannot-register-snapshot-repository-for-s3-compliant-backblaze-service/365581/21 "2024-08-28T20:56:13Z")

</div>

Hmm no I can't see how the node handling the HTTP request would make any difference here, it always gets routed internally to the master in any case.

Anyway glad it's working now!

[Previous page](https://discuss.elastic.co/t/cannot-register-snapshot-repository-for-s3-compliant-backblaze-service/365581.md?page=1)