Skip to content

docs: warn about third-party S3 provider compatibility #1173

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.

Sign up for GitHub

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

Merged
leonardoce merged 1 commit into from
Oct 20, 2026
Merged

docs: warn about third-party S3 provider compatibility #1173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions web/docs/object_stores.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,15 @@ overhead.
You can use S3-compatible services like **RustFS**, **Linode (Akamai) Object Storage**,
or **DigitalOcean Spaces** by specifying a custom `endpointURL`.

:::warning
Barman Cloud uses the Boto3 SDK and takes AWS S3 as its reference
implementation. Issues you can reproduce on AWS S3 are treated as Barman Cloud
defects. Issues that happen only on a third-party object store are API
incompatibilities, and you must resolve them with your storage vendor. See the
[Barman Cloud documentation](https://docs.pgbarman.org/release/latest/) for
known workarounds.
:::

Example with Linode (Akamai) Object Storage (`us-east1`):

```yaml
Expand Down
Loading