diff --git a/website/versioned_docs/version-1.28/appendixes/object_stores.md b/website/versioned_docs/version-1.28/appendixes/object_stores.md index 91d1dcb..81a4662 100644 --- a/website/versioned_docs/version-1.28/appendixes/object_stores.md +++ b/website/versioned_docs/version-1.28/appendixes/object_stores.md @@ -39,6 +39,16 @@ store backups in S3 buckets in two ways: [IRSA authentication method](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) - Alternatively, you can use the `ACCESS_KEY_ID` and `ACCESS_SECRET_KEY` credentials +:::info S3 provider compatibility + +Per the [Barman Cloud documentation](https://docs.pgbarman.org/release/3.17.0/user_guide/barman_cloud.html), + +> Barman Cloud utilizes the Boto3 SDK to integrate with S3-compatible object stores. While this ensures Barman Cloud functions correctly with the AWS S3 reference implementation and supports Barman Cloud integration with S3-compatible object stores, Barman Cloud does not directly support the underlying storage infrastructure of third-party vendors. Support is limited to the Barman Cloud software; issues that are reproducible on AWS S3 are treated as Barman Cloud defects and will be addressed by support channels. However, operational inconsistencies that occur exclusively on third-party object stores, and which cannot be reproduced on AWS S3, are considered API incompatibilities. Such issues must be resolved by the user in conjunction with their specific storage vendor. + +There have been compatibility issues with various S3-compatible storage providers. If you rely on such a provider, refer to the [Barman Cloud documentation](https://docs.pgbarman.org/release/3.17.0/user_guide/barman_cloud.html) for potential workarounds, and check for updates from your provider. + +::: + ### AWS Access key You will need the following information about your environment: @@ -357,4 +367,4 @@ Now the operator will use the credentials to authenticate against Google Cloud S This way of authentication will create a JSON file inside the container with all the needed information to access your Google Cloud Storage bucket, meaning that if someone gets access to the pod will also have write permissions to the bucket. -::: \ No newline at end of file +:::