RC: Seamless endpoint migration - Dynamic endpoints/Endpoint redirection

content/embeds/rc-get-prometheus-endpoint.md

@@ -0,0 +1,5 @@
+In the **Metrics** tab of your database, select **Connect to Prometheus > Copy Prometheus endpoint** to save your Prometheus endpoint to the clipboard.
+
+{{<image filename="images/rc/database-metrics-connect-prometheus.png" width="250px" alt="Use the Connect to Prometheus button to get the Prometheus endpoint.">}}
+
+You can also get the Prometheus endpoint by calling [`GET /subscriptions/{subscriptionId}`]({{< relref "/operate/rc/api/api-reference#tag/Subscriptions-Pro/operation/getSubscriptionById" >}}) and getting the `prometheusEndpoint` from the response.

content/integrate/dynatrace-with-redis-cloud/_index.md

@@ -42,7 +42,9 @@ If you have not already created a VPC between the Redis Cloud cluster and the ne
 Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
+You'll also need the [Prometheus endpoint for your database]({{< relref "/operate/rc/databases/monitor-performance#connect-to-prometheus" >}}) from the [Redis Cloud console](https://cloud.redis.io/).
 
+{{< embed-md "rc-get-prometheus-endpoint.md" >}}
 
 ## View metrics
 

content/integrate/new-relic-with-redis-cloud/_index.md

@@ -62,6 +62,10 @@ Get metrics from Redis Cloud:
       - targets: ["REDIS_CLOUD_HOST:8070"]
 ```
 
+Replace `REDIS_CLOUD_HOST` with the [Prometheus endpoint for your database]({{< relref "/operate/rc/databases/monitor-performance#connect-to-prometheus" >}}), which you can get from the [Redis Cloud console](https://cloud.redis.io/). 
+
+{{< embed-md "rc-get-prometheus-endpoint.md" >}}
+
 Write them to New Relic:
 
 ```yaml

content/integrate/prometheus-with-redis-cloud/_index.md

@@ -43,19 +43,9 @@ You can quickly set up Prometheus and Grafana for testing using the Prometheus a
 
 1. Set up [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}).
 
-1. Extract the Prometheus endpoint from the private endpoint to your database. The private endpoint is in the [Redis Cloud console](https://cloud.redis.io/) under the [Configuration tab]({{< relref "/operate/rc/databases/view-edit-database#configuration-tab" >}}) of your database. The Prometheus endpoint is on port 8070 of the internal server.
+1. Get the Prometheus endpoint for your database from the [Redis Cloud console]({{< relref "/operate/rc/databases/monitor-performance#connect-to-prometheus" >}}).
 
-    For example, if your private endpoint is:
-
-    ```sh
-    redis-12345.internal.<cluster_address>:12345
-    ```
-
-    The Prometheus endpoint is:
-
-    ```sh
-    internal.<cluster_address>:8070
-    ``` 
+    {{< embed-md "rc-get-prometheus-endpoint.md" >}}
 
 1. Create an instance to run Prometheus and Grafana on the same cloud provider as your Redis Cloud subscription (for example, Amazon Web Services or Google Cloud). This instance must:
     - Exist in the same region as your Redis Cloud subscription.

content/operate/rc/changelog/march-2026.md

@@ -7,7 +7,7 @@ categories:
 - rc
 description: New features, enhancements, and other changes added to Redis Cloud during
   March 2026.
-highlights: Redis 8.4 on Redis Cloud Pro, Automatic database upgrades
+highlights: Dynamic endpoints & endpoint redirection, Redis 8.4 on Redis Cloud Pro
 linktitle: March 2026
 weight: 53
 tags:
@@ -16,6 +16,16 @@ tags:
 
 ## New features
 
+### Dynamic endpoints
+
+As of March 22, 2026, Redis Cloud now generates dynamic endpoints for all databases. Databases created before March 22, 2026 can still view both legacy static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future.
+
+We recommend slowly migrating connections to the dynamic endpoints. Moving connections from the static endpoints to the dynamic endpoints does not cause any downtime. See [Applications that use legacy static endpoints]({{< relref "/operate/rc/databases/redirect-endpoints#applications-that-use-legacy-static-endpoints" >}}) for more information.
+
+### Redirect dynamic endpoints
+
+You can redirect your dynamic endpoints to any Redis Cloud Pro database in the same account. Redirecting your dynamic endpoints lets you switch connections to your new database seamlessly through Redis Cloud without any code changes. See [Redirect database endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information.
+
 ### Redis 8.4 on Redis Cloud Pro
 
 Redis 8.4 is now available for [Redis Cloud Pro databases]({{< relref "/operate/rc/databases/create-database/create-essentials-database" >}}) in select regions.

content/operate/rc/databases/connect/_index.md

@@ -11,15 +11,46 @@ linkTitle: Connect
 weight: 12
 ---
 
-After you [create your database]({{< relref "/operate/rc/databases/create-database" >}}), you can connect to it.
+After you [create your database]({{< relref "/operate/rc/databases/create-database" >}}), you can connect to it using the public or private endpoint.
 
-To connect to the database, you need your username and password. By default, your database is protected by a [**Default user**]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) called `default` and a masked **Default user password**. You can see the default user password in the **Security** section of the **Configuration** details for your database. Select the eye icon to show or hide the password.    
+## Get connection information
+
+To connect to the database, you need the following information:
+- The database endpoint
+- Your database username and password
+
+### Database endpoints
+
+The database endpoints are listed in the **General** section of the **Configuration** tab for your database.
+
+{{<image filename="images/rc/databases-configuration-general-endpoints.png" alt="The General section of the Configuration tab of the database details page." >}}
+
+Redis Cloud Pro and Redis Cloud Essentials databases have a public endpoint, which you can access from the public internet. Redis Cloud Pro databases also have a private endpoint. You can connect to the private endpoint from a private network. Before you can connect to the private endpoint, you must set up a private connectivity method, such as:
+- [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}})
+- [Google Cloud Private Service Connect]({{< relref "/operate/rc/security/private-service-connect" >}}) (Google Cloud only)
+- [AWS Transit Gateway]({{< relref "/operate/rc/security/aws-transit-gateway" >}}) or [AWS PrivateLink]({{< relref "/operate/rc/security/aws-privatelink" >}}) (AWS only)
+
+Redis Cloud Pro users can block the public endpoint for their databases. For more information, see [Block public endpoints]({{< relref "/operate/rc/security/database-security/block-public-endpoints" >}}).
+
+For databases created after March 22, 2026, you can [redirect these endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) to a different database. 
+
+Databases created before March 22, 2026 have both legacy static endpoints and dynamic endpoints. You can see the Dynamic endpoints by expanding the **Dynamic endpoints** section in the **General** section of the **Configuration** tab. 
+
+{{<image filename="images/rc/databases-configuration-general-endpoints-legacy.png" alt="The General section of the Configuration tab of the database details page for a database created before March 22, 2026." >}}
+
+You can redirect the dynamic endpoints to a different database at any time, but you cannot redirect the static endpoints. We recommend using the dynamic endpoints for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information.
+
+### Database username and password
+
+By default, your database is protected by a [**Default user**]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) with the username `default` and a masked **Default user password**. You can see the default user password in the **Security** section of the **Configuration** details for your database. Select the eye icon to show or hide the password.    
 
 {{<image filename="images/rc/database-fixed-configuration-security.png" width="75%" alt="The Security section of the Configuration tab of the database details page." >}}
 
 If you've turned on [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}) for your database and [turned off the default User]({{< relref "/operate/rc/security/access-control/data-access-control/default-user#turn-off-default-user" >}}), use the username and password for your data access role.
 
-Once you have the username and password, select **Connect** to open the connection wizard.
+## Connect to your database with connection wizard
+
+Select **Connect** to open the connection wizard.
 
 {{< image filename="/images/rc/button-connect.png#no-click" alt="Connect button." >}}
 
@@ -37,7 +68,7 @@ The connection wizard provides the following database connection methods:
 
 {{<image filename="images/rc/connection-wizard.png" alt="The connection wizard." width=500px >}}
 
-## Redis Insight {#using-redisinsight}
+### Redis Insight {#using-redisinsight}
 
 [Redis Insight]({{< relref "/develop/tools/insight" >}}) is a free Redis GUI that lets you visualize your Redis data and learn more about Redis.
 
@@ -47,7 +78,7 @@ You can connect to your database with Redis Insight in two ways:
 
 1. [Download and Install Redis Insight](#ri-app) on Windows, macOS, and Linux.
 
-### Open in your browser {#ri-browser}
+#### Open in your browser {#ri-browser}
 
 {{< note >}}
 Opening your database with Redis Insight in your browser is only available for Essentials databases. For all other databases, [Download and install Redis Insight](#ri-app) on your computer.
@@ -65,7 +96,7 @@ Redis Insight will open in a new tab.
 
 This browser-based version of Redis Insight has a subset of the features of Redis Insight. For more information, see [Open with Redis Insight on Redis Cloud]({{< relref "/operate/rc/databases/connect/insight-cloud" >}}).
 
-### Install and open on your computer {#ri-app}
+#### Install and open on your computer {#ri-app}
 
 1. If you haven't downloaded Redis Insight, select **Download** under **Redis Insight** in the Connection wizard to download it. 
 
@@ -79,7 +110,7 @@ If you get an error when connecting with Redis Insight, [manually connect to you
 
 You can use Redis Insight to view your data, run Redis commands, and analyze database performance. See the [Redis Insight docs]({{< relref "/develop/tools/insight" >}}) for more info.
 
-## Redis client {#using-redis-client}
+### Redis client {#using-redis-client}
 
 A Redis client is a software library or tool that enables applications to interact with a Redis server. Each client has its own syntax and installation process. For help with a specific client, see the client's documentation.
 
@@ -98,7 +129,13 @@ If the username and password are not already filled in, replace `<username>` and
 
 See [Clients]({{< relref "/develop/clients" >}}) to learn how to connect with the official Redis clients.
 
-### redis-cli {#using-rediscli}
+{{< note >}}
+Databases created before March 22, 2026 have a set of default static endpoints and dynamic endpoints that can be redirected to a Redis Cloud Pro database. We recommend using the dynamic endpoints for your application so that you can migrate your database endpoints to a different database in the future without any code changes. See [Redirect dynamic endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information.
+
+Databases created after March 22, 2026 only have dynamic endpoints. You can redirect those endpoints at any time.
+{{< /note >}}
+
+#### redis-cli {#using-rediscli}
 
 The [`redis-cli`]({{< relref "/develop/tools/cli" >}}) utility is installed when you install Redis.  It provides a command-line interface that lets you work with your database using core [Redis commands]({{< relref "/commands" >}}).
 

content/operate/rc/databases/migrate-databases.md

@@ -141,11 +141,22 @@ Active-Passive sync lets you migrate data while apps and other connections are u
 Do not write to the target database until turning off Active-Passive. Writing to the target database of an Active-Passive setup can cause data consistency issues and replication failures. See [Active-Passive replication considerations]({{< relref "/operate/rc/databases/configuration/data-eviction-policies.md#active-passive-replication-considerations" >}}) for more information.
 {{< /warning >}}
 
-## Active-Passive memory requirements
+### Active-Passive memory requirements
 
 Active-Passive sync requires more memory than data import.  On average, you need an extra 25% memory on top of other requirements, though specific requirements depend on the data types and other factors.  
 
 To illustrate, suppose you want to migrate a 1&nbsp;GB source database without replication to a target database with replication enabled.  Here, the target database memory limit should be at least 2.5&nbsp;GB to avoid data loss.
 
-Once the databases are synced, you can disable Active-Passive for the target database.  Before doing so, however, verify that apps and other connections have switched to the target database; otherwise, you may lose data.
+## Next steps
 
+If you want to redirect your application's connections to the target database, you can [redirect your database endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) to the target database. 
+
+Before you redirect your endpoints, make sure:
+- 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. Pausing writes during endpoint redirection is a standard best practice to help ensure data consistency. Still, you can choose the timing and behavior that fits your system (for example, whether to allow reads, how long to pause traffic, and what validation to run).
+
+Once the databases are synced and the endpoints are redirected, you can turn off Active-Passive for the target database.  Before doing so, however, verify that apps and other connections have switched to the target database; otherwise, you may lose data.

content/operate/rc/databases/monitor-performance.md

@@ -90,6 +90,14 @@ To update alert settings for one or more team members, select **Access Managemen
 
 If you subscribe to Redis Cloud through a Platform-as-a-Service (PaaS) provider (such as Heroku), you will need to review your provider's documentation for help managing your team.
 
+## Connect to Prometheus
+
+Redis Cloud exposes a Prometheus endpoint for Redis Cloud Pro databases. You can use this endpoint to connect Prometheus to your database.
+
+{{< embed-md "rc-get-prometheus-endpoint.md" >}}
+
+For more information on how to connect Prometheus to Redis Cloud, see [Prometheus and Grafana with Redis Cloud]({{< relref "/integrate/prometheus-with-redis-cloud/" >}}).
+
 ## Continue learning with Redis University
 
 {{< university-links >}}