Skip to content

Commit 9bcbf10

Browse files
authored
[DOC-953][2025.2][yba] AWS S3 signing region (#29524)
* AWS S3 signing region
1 parent 3c3598b commit 9bcbf10

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/content/stable/yugabyte-platform/back-up-restore-universes/configure-backup-storage.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,19 @@ The following S3 IAM permissions are required:
7777
"s3:GetBucketLocation"
7878
```
7979

80+
### Specify signing region
81+
82+
In some circumstances, you may need to additionally specify the signing region for the AWS backup configuration. For example:
83+
84+
- The S3 bucket uses a non-standard S3 endpoint, such as a private VPC endpoint, or S3-compatible storage; and
85+
- YugabyteDB Anywhere is running in a region that is different than the region where the S3 bucket is located.
86+
87+
In these cases you can encounter errors such as 'Cannot list objects in backup location'.
88+
89+
Typically, the signing region is the AWS region where the S3 bucket is located (for example, `us-east-1`). Enter the AWS region in the **Signing region** field.
90+
91+
By default, the **Signing region** field is not available in the UI. To make it available, set the **Enable Signing Region** Global Runtime Configuration option (config key `yb.ui.feature_flags.enable_signing_region`) to true. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/). You must be a Super Admin to set global runtime configuration flags.
92+
8093
## Google Cloud Storage
8194

8295
You can configure Google Cloud Storage (GCS) as your backup target.

0 commit comments

Comments
 (0)