# Redirect dynamic endpoints

```json metadata
{
  "title": "Redirect dynamic endpoints",
  "description": "Shows how to redirect dynamic endpoints to a different database.",
  "categories": ["docs","operate","rc"],
  "tableOfContents": {"sections":[{"id":"when-to-redirect-dynamic-endpoints","title":"When to redirect dynamic endpoints"},{"id":"applications-that-use-legacy-static-endpoints","title":"Applications that use legacy static endpoints"},{"children":[{"id":"scope-and-impact","title":"Scope and impact"},{"id":"prerequisites","title":"Prerequisites"},{"id":"limitations","title":"Limitations"}],"id":"before-you-start","title":"Before you start"},{"id":"redirect-database-endpoints","title":"Redirect database endpoints"},{"id":"revert-endpoint-redirection","title":"Revert endpoint redirection"},{"id":"unblock-database-traffic","title":"Unblock database traffic"}]}

,
  "codeExamples": []
}
```
Dynamic endpoints allow you to redirect application traffic from one database to another in the same Redis Cloud account without updating the endpoints in your application. Redis manages endpoint redirection for you.

You can redirect any database's dynamic endpoints to any Redis Cloud Pro database in the same account. If you need to replicate the data from the source database, you should [migrate your data](https://redis.io/docs/latest/operate/rc/databases/migrate-databases) to the target database before you redirect your endpoints.

## When to redirect dynamic endpoints

Use endpoint redirection to seamlessly migrate your application traffic to a different database within the same Redis Cloud account. There is no need to update the endpoints in your application, since they'll remain the same. For example, you might want to:

- Upgrade your database's subscription from an [Essentials Plan to a Pro Plan](https://redis.io/docs/latest/operate/rc/subscriptions/upgrade-essentials-pro)
- Move between Redis Cloud offerings, such as Redis on RAM to Redis Flex
- Split a subscription or combine databases from multiple subscriptions into one
- Migrate your database to a different cloud provider, region, or availability zone
- Redirect the endpoint to another database to restore service during Disaster Recovery

## Applications that use legacy static endpoints

Existing databases have both legacy static endpoints and dynamic endpoints. 

Static endpoints on Redis Cloud start with `redis-<port>.c<number>` (or `redis-<port>.internal.c<number>` for the private endpoint). For example, a static endpoint might look like this:

```text
redis-12345.c12345.us-east-1-mz.ec2.cloud.rlrcp.com
```

Dynamic endpoints on Redis Cloud always contain three words and a random number, and end in `db.redis.io`. For example, a dynamic endpoint might look like this:

```text
horse-battery-staple-12345.db.redis.io
```

You can see the Dynamic endpoints for databases with both static and dynamic endpoints by expanding the **Dynamic endpoints** section in the **General** section of the **Configuration** tab. 

![images/rc/databases-configuration-general-endpoints-legacy.png](https://redis.io/docs/latest/images/rc/databases-configuration-general-endpoints-legacy.png)

You can only migrate the dynamic endpoints to point to a new database. Transitioning from the static to the dynamic endpoint does not cause downtime and allows you to gradually manage client disconnections. To migrate to the dynamic endpoint safely:
- Move clients one-by-one (or service-by-service) from legacy static endpoints to dynamic endpoints. Note that during the transition period, both static and Dynamic endpoints can be used concurrently.
- After all clients use the dynamic endpoint, you can then redirect the dynamic endpoints to the target database.

This phased approach minimizes risk and allows controlled client reconnections throughout the migration process.

## Before you start

Read the following sections to prepare for endpoint redirection.

### Scope and impact

This process redirects a source database's dynamic endpoints to a selected target database, including both public and private (if available) endpoints. **Redirecting endpoints does not migrate the data in your database.** You can choose to redirect the endpoints without migrating your data. If you need your data to be available in the target database, you must [migrate your data](https://redis.io/docs/latest/operate/rc/databases/migrate-databases) to the target database **before** you redirect your endpoints.

To ensure all connections are redirected to the target database, Redis Cloud will block all traffic to the source database for at least 5 minutes. This block period gives DNS caches time to expire and allow clients to reconnect and re-resolve the endpoint. All existing connections to the source database will be terminated and new connections will be refused. To reduce the risk of traffic being split between the source and target database, traffic will remain blocked until you [unblock it](#unblock-database-traffic).   

Short-lived connection disruptions may occur as clients reconnect to the database, depending on client reconnection behavior.

We recommend redirecting during a low-traffic window.

#### Redirecting endpoints after data migration

If you [migrated your data](https://redis.io/docs/latest/operate/rc/databases/migrate-databases) to the target database before redirecting your endpoints, make sure that:
- The import or replication is finished.
- Basic metrics for both the source and target databases are reporting normally.
- The application authentication and authorization are set up correctly for the target database.
- You have tested connection to the target database to confirm connectivity and credentials.

Different applications have different availability and consistency requirements. Redis Cloud blocks traffic to the source database for at least 5 minutes to ensure all clients have reconnected to the target database, but you can choose the timing and behavior that fits your system (for example, how long to block traffic and what validation to run).

### Prerequisites

Make sure you have met the following prerequisites:

- Your application is using the dynamic endpoint. Endpoint redirection does not redirect [static endpoints](#applications-that-use-legacy-static-endpoints).
- You have [created a target Redis Cloud Pro database](https://redis.io/docs/latest/operate/rc/databases/create-database/create-pro-database-new) in the same account that [is compatible with the source database](#redirection-compatibility).
- If you monitor the source database with Prometheus, add the target database to Prometheus before your redirect the endpoint so that you can monitor the target database after the redirection. See [Connect to Prometheus](https://redis.io/docs/latest/operate/rc/databases/monitor-performance#connect-to-prometheus) for more information.
- Make sure that your client connections are configured with socket/connection timeouts. If you do not configure them, your client may hang indefinitely and the connection will not refresh until the application is restarted. Refer to the [Client documentation](https://redis.io/docs/latest/develop/clients) for your client for more information.

#### Redirection compatibility

Endpoint redirection is only allowed when the source and target databases are compatible. Redis Cloud will validate compatibility and may prevent redirection if the source and target databases are not compatible.

If any of the following properties differ, the databases are not compatible and you cannot redirect the endpoints:
- Port number
- Connectivity settings, such as:
    - [TLS settings](https://redis.io/docs/latest/operate/rc/security/database-security/tls-ssl)
    - [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering) or other connectivity method settings
    - [Default User settings](https://redis.io/docs/latest/operate/rc/security/access-control/data-access-control/default-user)
    - [CIDR allow list](https://redis.io/docs/latest/operate/rc/security/cidr-whitelist) settings

Some differences may be intentional but can affect application behavior. In those cases, the console will warn you about the difference but allow you to proceed with redirection. The following differences will cause a warning:
- Redis version
- [RESP Database protocol version](https://redis.io/docs/latest/develop/reference/protocol-spec#resp-versions)
- [OSS Cluster API](https://redis.io/docs/latest/operate/rc/databases/configuration/clustering#oss-cluster-api) configuration

### Limitations

Be aware of the following limitations when redirecting dynamic endpoints:
- The target database must be a Redis Cloud Pro database on the same account as the source database.
- Active-Active databases are currently not supported as either a source or target database (coming soon).
- Databases using GCP Private Service Connect or AWS PrivateLink are currently not supported for endpoint redirection (coming soon).

## Redirect database endpoints

To redirect your database endpoints:

1. From the Redis Cloud console, select **Databases** from the menu and select the source database in the list.

1. In the **General** section of the **Configuration** tab, select **Redirect endpoints**.

    ![images/rc/databases-configuration-redirect-endpoints.png](https://redis.io/docs/latest/images/rc/databases-configuration-redirect-endpoints.png)

1. Select the target Redis Cloud Pro database from the **Target database** list. You can type in the database's name to find it.

    ![images/rc/migrate-data-redirect-pro-endpoints.png](https://redis.io/docs/latest/images/rc/migrate-data-redirect-pro-endpoints.png)

1. If you want to assign the same [Role-based Access Control (RBAC) roles](https://redis.io/docs/latest/operate/rc/security/access-control/data-access-control/role-based-access-control) to the target database that are assigned to the source database, select **Assign the same ACLs to the target database**.

    ![images/rc/migrate-data-redirect-assign-acls.png](https://redis.io/docs/latest/images/rc/migrate-data-redirect-assign-acls.png)

1. Select **I acknowledge this action will redirect my database endpoints** to confirm that you understand that this action will redirect your database endpoints. Then select **Redirect endpoints**.

    ![images/rc/migrate-data-redirect-acknowledge.png](https://redis.io/docs/latest/images/rc/migrate-data-redirect-acknowledge.png)

After you redirect your database endpoints, you can go to the **Configuration** tab of the target database to verify that the endpoints now point to the target database. To ensure all connections are redirected to the target database, Redis Cloud will block all traffic to the source database for at least 5 minutes to ensure all clients have reconnected to the target database. After 5 minutes, you can  [unblock traffic to the source database](#unblock-database-traffic). You can also [revert the redirection](#revert-endpoint-redirection) within 24 hours to restore the original endpoints.

## Revert endpoint redirection

You can revert endpoint redirection within 24 hours to restore the original endpoints. From either database's **Configuration** tab, select **Revert** to revert endpoint migration.

![images/rc/migrate-data-redirect-revert.png](https://redis.io/docs/latest/images/rc/migrate-data-redirect-revert.png)

After the 24-hour window, you can no longer revert to the original endpoints. You can redirect them back to the source database if the source database is a Redis Cloud Pro database. However, doing this will create new endpoints for the target database.

After you revert endpoint redirection, Redis Cloud will unblock traffic to the source database and block traffic to the target database for 5 minutes to ensure all clients have reconnected to the source database. After 5 minutes, you can [unblock traffic to the target database](#unblock-database-traffic).

## Unblock database traffic

After you redirect your database endpoints, Redis Cloud will block all traffic to the source database for at least 5 minutes to ensure all clients have reconnected to the target database. If you revert endpoint redirection, Redis Cloud will unblock traffic to the source database and block traffic to the target database for at least 5 minutes to ensure all clients have reconnected to the source database. If Redis Cloud has blocked traffic to a database, the database will display a **Traffic blocked** badge in the Redis Cloud console.

![images/rc/migrate-data-traffic-blocked.png](https://redis.io/docs/latest/images/rc/migrate-data-traffic-blocked.png)

You will not be able to unblock traffic to a database until 5 minutes after you redirect your database endpoints or revert endpoint redirection. Before you unblock traffic to a database, make sure that all clients have reconnected to the correct database.

To unblock traffic to a database, from the database's **Configuration** tab, select **Unblock traffic**.

![images/rc/migrate-data-redirect-unblock.png](https://redis.io/docs/latest/images/rc/migrate-data-redirect-unblock.png)