# Storing, processing, and replicating notifications using notification hubs in AWS User Notifications
Notification hubs

Notification hubs are an account-level setting that identify the AWS Regions where you store, process, and replicate notifications. You must select at least one notification hub before you create any notification configurations. If you have no notification hubs, the console prompts you to choose at least one before you create a notification configuration. You can also edit notification hubs from **Notification hubs** in the navigation pane. Currently, you can select up to three Regions. 

**Note**  
 If you want to manage notification hubs, ensure you have the appropriate permissions. For more information, see [Resource-level permissions in AWS User Notifications](resource-level-permissions.md). 

**Important**  
Notification hubs only set the Regional boundaries of notifications. User Notifications stores the notification configuration's data in the default Region, US East (N. Virginia). This data is also stored in individual Regions that you have configured rules for. For example, say that you create a configuration that receives Amazon CloudWatch Alarm notifications about events in Europe (Milan) and Europe (Frankfurt). User Notifications creates the notification configuration in US East (N. Virginia). It then replicates the configuration to Europe (Milan) and Europe (Frankfurt). 

**Important**  
User Notifications uses Amazon Simple Email Service (Amazon SES) API endpoints to deliver email notifications. Amazon SES API endpoints aren't available in all Regions. For a list of Regions that support Amazon SES API endpoints, see [Amazon Simple Email Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/ses.html#ses_region) in the *Amazon Web Services General Reference*. User Notifications routes emails about events originating from Regions that aren't supported as Amazon SES API endpoints through US East (N. Virginia). If wanted, you can turn off the receipt of notification for events that originate in Regions that Amazon SES API endpoints don't support. To do so, don't configure emails for notification configurations that contain events in these Regions.

**Topics**
+ [

# Adding or removing a notification hub in AWS User Notifications
](nhr-add-remove.md)
+ [

# Enabling or disabling opt-in Regions in AWS User Notifications
](nhr-optin-out.md)

# Adding or removing a notification hub in AWS User Notifications
Adding or removing a notification hub

You can add or remove a notification hub using the AWS Management Console. When you add a new notification hub, User Notifications replicates new notifications into that Region. User Notifications doesn’t backfill earlier notifications. When you remove a notification hub, User Notifications stops replicating new notifications into that Region. User Notifications doesn’t remove previous notifications from that Region. However, notifications expire 90 days after they are generated.

**To add or remove notification hubs**

1. Open User Notifications in the [AWS Management Console](https://console.aws.amazon.com/).

   1. In the navigation pane, choose **Notification hubs**.

1. Choose **Edit**.

1. Either add Regions by selecting them or remove Regions by choosing the **×** next to a Region.

1. Choose **Update**.

# Enabling or disabling opt-in Regions in AWS User Notifications
Enabling or disabling opt-in Regions

Although most AWS Regions are active by default for your AWS account, certain Regions are activated only when you manually select them. This document refers to those Regions as *opt-in Regions*. In contrast, Regions that are active by default, as soon as your AWS account is created, are referred to as *commercial Regions*, or simply, *Regions*.

If you choose to select an opt-in Region as your notification hub, enable it first by following the steps in [Enabling a Region](https://docs.aws.amazon.com//general/latest/gr/rande-manage.html#rande-manage-enable). Enabling or disabling an opt-in Region may impact your notifications experience. For a list of supported opt-in Regions, see [Opt-in Regions](supported-regions.md#opt-in-Regions).

## Disabling a notification hub Region


You must have a notification hub configured to create notification configurations. If you disable an opt-in Region that contains your only notification hub, you can't create new notification configurations. You also can't access previous notifications until you enable the opt-in Region or create a new notification hub.

### Choosing a notification hub Region that isn't enabled


You must enable an opt-in Region to use a notification hub you create in that opt-in Region. If you don't enable the opt-in Region, your notification hub remains inactive. You can't create notification configurations or view notifications until you enable that opt-in Region on your account or select a new notification hub.