---
title: "Configuring Object Event Notification Across Multiple Regions"
slug: "configuring-object-event-notification-across-multiple-regions"
description: "Configure object notifications for buckets located in multiple regions (other than US-EAST-1)."
tags: ["Object Event Notifications", "PostMan", "PUT AWS Credentials"]
updated: 2026-01-09T15:27:04Z
published: 2026-01-09T15:27:04Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Object Event Notification Across Multiple Regions

Follow the instructions below if you want to configure object notifications for buckets located in regions *other than US-EAST-1*.

1. Using [PostMan](https://www.postman.com/) (https://www.postman.com/), create a new API entry for **PUT AWS Credentials**specifying an S3 endpoint that includes the region where the bucket exists. For example:

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1719090686039.png)
2. Select the **Authorization** tab, as shown below, and select the **AWS Signature** as the Type.
3. Enter the Wasabi account **AccessKey** and **SecretKey** for the account that owns the Wasabi S3 bucket for which you want to configure Object Event Notifications.
4. For the **AWS Region**, enter the Wasabi region of the S3 bucket, and be sure the **Service Name** value is set to **s3**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1719090777210.png)
5. Select the **Body** tab and select **Raw**for the body encoding format:

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1719090955754.png)
6. Enter the AWS credentials that you want to add to the selected Wasabi account to the body of the PUT request.

> While configuring AWS keys, the region must match the SNS configuration region set up in AWS.

> When setting credential permissions in AWS (ec2:DescribeRegions and sns:ListTopics), you must give permission to access the AWS resources.

The AWS credentials are specified in XML format and should be similar to the following:

```json
<?xml version="1.0" encoding="UTF-8"?>
                <AWSCredentials>
                <Credentials>
                <Region>us-east-1</Region>
                <AccessKeyID>YOURACCESSKEY</AccessKeyID>
                <SecretAccessKey>YOURSECRETKEY</SecretAccessKey>
                </Credentials>
                </AWSCredentials>
```

For example:

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1692288865090.png)
7. Click the **Send**button and confirm that a 200 OK response is received, indicating the AWS credentials were successfully set for the specified Wasabi account. For example:

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1719091072337.png)
8. To confirm that the AWS credentials were successfully set for the Wasabi account, you can create a new API for **GET AWS Credentials**.

> The **SecretKey** is intentionally omitted from the response body for security purposes.
  - Repeat Step 1 above, but select **GET** as the operation. Specify the same URL.
  - Enter the same Wasabi credentials as in Step 2.
  - Skip Step 3 because Body is not required for this GET operation.
  - Click the **Send** button. Confirm that a 200 OK response is received, indicating the AWS credentials were successfully retrieved for the specified Wasabi account.
  - Confirm that the AWS **AccessKey** returned in the Body of the response matches what was specified in the PUT operation.

You should be able to successfully configure Event Notifications for the bucket in the remote region, and you should be able to select the credentials for the AWS region that you configured with these instructions.

## Related

- [Event Notifications: Configuring, Creating, and Managing](/event-notifications-bucket.md)