From d546dc67ffd7582071cbfaa9aa6f1f42566faef3 Mon Sep 17 00:00:00 2001
From: Michael Lip <51033404+theluckystrike@users.noreply.github.com>
Date: Sun, 20 Sep 2026 17:36:43 +0700
Subject: [PATCH] docs document AWS_DEFAULT_REGION workaround for S3-compatible
 storage

Assisted-by: Hermes Agent (theluckystrike)
---
 web/docs/object_stores.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/web/docs/object_stores.md b/web/docs/object_stores.md
index 11b1ff8c..cd9c8eed 100644
--- a/web/docs/object_stores.md
+++ b/web/docs/object_stores.md
@@ -171,6 +171,8 @@ spec:
         value: when_required
       - name: AWS_RESPONSE_CHECKSUM_VALIDATION
         value: when_required
+      - name: AWS_DEFAULT_REGION
+        value: eu-central-1
   [...]
 ```
 
@@ -178,6 +180,14 @@ These settings ensure that checksum calculations and validations are only
 applied when explicitly required, avoiding compatibility issues with certain
 S3-compatible storage providers.
 
+Newer AWS SDK libraries can also fail to resolve the target region
+automatically, particularly on recent releases of S3-compatible storage
+providers. If the sidecar logs show region-related errors, set
+`AWS_DEFAULT_REGION` in the same `env` block. This was reported in
+[GitHub issue #800](https://github.com/cloudnative-pg/plugin-barman-cloud/issues/800),
+where the operator also required the checksum variables on a cloud with
+strict defaults.
+
 Example with DigitalOcean Spaces (SFO3, path-style):
 
 ```yaml