Skip to content

docs add AWS_DEFAULT_REGION to S3-compatible storage workaround #1108

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

Open
theluckystrike wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs add AWS_DEFAULT_REGION to S3-compatible storage workaround #1108

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
10 changes: 10 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 @@ -171,13 +171,23 @@ spec:
value: when_required
- name: AWS_RESPONSE_CHECKSUM_VALIDATION
value: when_required
- name: AWS_DEFAULT_REGION
value: eu-central-1
[...]
```

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
Expand Down