Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.13] Recommend NFS over S3-like repositories (#107297) #107300

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 11 additions & 7 deletions docs/reference/snapshot-restore/repository-s3.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -541,13 +541,17 @@ MinIO-backed repositories as well as repositories stored on AWS S3. Other
S3-compatible storage systems may also work with {es}, but these are not
covered by the {es} test suite.

Note that some storage systems claim to be S3-compatible but do not faithfully
emulate S3's behaviour in full. The `repository-s3` type requires full
compatibility with S3. In particular it must support the same set of API
endpoints, return the same errors in case of failures, and offer consistency and
performance at least as good as S3 even when accessed concurrently by multiple
nodes. You will need to work with the supplier of your storage system to address
any incompatibilities you encounter. Please do not report {es} issues involving
There are many systems, including some from very well-known storage vendors,
which claim to offer an S3-compatible API despite failing to emulate S3's
behaviour in full. If you are using such a system for your snapshots, consider
using a <<snapshots-filesystem-repository,shared filesystem repository>> based
on a standardized protocol such as NFS to access your storage system instead.
The `repository-s3` type requires full compatibility with S3. In particular it
must support the same set of API endpoints, with the same parameters, return
the same errors in case of failures, and offer consistency and performance at
least as good as S3 even when accessed concurrently by multiple nodes. You will
need to work with the supplier of your storage system to address any
incompatibilities you encounter. Please do not report {es} issues involving
storage systems which claim to be S3-compatible unless you can demonstrate that
the same issue exists when using a genuine AWS S3 repository.

Expand Down
Loading