diff --git a/content/embeds/rc-get-prometheus-endpoint.md b/content/embeds/rc-get-prometheus-endpoint.md new file mode 100644 index 0000000000..22b3b5c406 --- /dev/null +++ b/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. + +{{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. diff --git a/content/integrate/dynatrace-with-redis-cloud/_index.md b/content/integrate/dynatrace-with-redis-cloud/_index.md index 97234f2ad3..743584811d 100644 --- a/content/integrate/dynatrace-with-redis-cloud/_index.md +++ b/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 diff --git a/content/integrate/new-relic-with-redis-cloud/_index.md b/content/integrate/new-relic-with-redis-cloud/_index.md index a37cea5371..5519998816 100644 --- a/content/integrate/new-relic-with-redis-cloud/_index.md +++ b/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 diff --git a/content/integrate/prometheus-with-redis-cloud/_index.md b/content/integrate/prometheus-with-redis-cloud/_index.md index b7cfd52ef0..2894d69a75 100644 --- a/content/integrate/prometheus-with-redis-cloud/_index.md +++ b/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.:12345 - ``` - - The Prometheus endpoint is: - - ```sh - internal.: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. diff --git a/content/operate/rc/changelog/march-2026.md b/content/operate/rc/changelog/march-2026.md index ae96eb089e..5dc33dcd1a 100644 --- a/content/operate/rc/changelog/march-2026.md +++ b/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. diff --git a/content/operate/rc/databases/connect/_index.md b/content/operate/rc/databases/connect/_index.md index d5e9ca7edf..9d53d4cedb 100644 --- a/content/operate/rc/databases/connect/_index.md +++ b/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. + +{{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. + +{{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. {{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: {{The connection wizard.}} -## 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 `` 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" >}}). diff --git a/content/operate/rc/databases/migrate-databases.md b/content/operate/rc/databases/migrate-databases.md index 12cfdabebd..f9077c1e8a 100644 --- a/content/operate/rc/databases/migrate-databases.md +++ b/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 GB source database without replication to a target database with replication enabled. Here, the target database memory limit should be at least 2.5 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. \ No newline at end of file diff --git a/content/operate/rc/databases/monitor-performance.md b/content/operate/rc/databases/monitor-performance.md index 6936dc4bb0..e5c01dbdcb 100644 --- a/content/operate/rc/databases/monitor-performance.md +++ b/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 >}} diff --git a/content/operate/rc/databases/redirect-endpoints.md b/content/operate/rc/databases/redirect-endpoints.md new file mode 100644 index 0000000000..a8143a7887 --- /dev/null +++ b/content/operate/rc/databases/redirect-endpoints.md @@ -0,0 +1,137 @@ +--- +Title: Redirect dynamic endpoints +alwaysopen: false +categories: +- docs +- operate +- rc +description: Shows how to redirect dynamic endpoints to a different database. +linkTitle: Redirect endpoints +weight: 31 +--- + +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. For a smooth transition with your existing data, you should [migrate your data]({{< relref "/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]({{< relref "/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 + +Databases created before March 22, 2026 have both legacy static endpoints and dynamic endpoints. You can only migrate the dynamic endpoints to point to a new database. If your application uses the static endpoints, it will connect to the source database instead of the target database after redirection. You can find both the static and dynamic endpoints for these databases on the database's **Configuration** page. + +{{The General section of the Configuration tab of the database details page for a database created before March 22, 2026. The dynamic endpoints are listed under the **Dynamic endpoints** section.}} + +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]({{< relref "/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 stop all traffic to the source database for 5 minutes after the redirection. During this time: +- All existing connections to the source database will be terminated and new connections will be refused. +- Clients will automatically reconnect with refreshed DNS. +- New connections are established to the target database. + +If you choose to revert the redirection, traffic to the source will resume, even if the 5-minute window has not passed. + +Plan for the following impacts when redirecting your endpoints: +- Short-lived connection disruptions may occur as clients reconnect to the database, depending on client reconnection behavior. +- Application behavior may change if the target differs in configuration from the source database. See [Redirection compatibility](#redirection-compatibility) for a list of differences that can change application behavior. + +We recommend redirecting during a low-traffic window. + +#### Redirecting endpoints after data migration + +If you [migrated your data]({{< relref "/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. 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). + +### 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]({{< relref "/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]({{< relref "operate/rc/databases/monitor-performance#connect-to-prometheus" >}}) 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]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}) + - [VPC Peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or other connectivity method settings + - [Default User settings]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}) + - [CIDR allow list]({{< relref "/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]({{< relref "/develop/reference/protocol-spec" >}}#resp-versions) +- [OSS Cluster API]({{< relref "/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**. + + {{Use the **Redirect endpoints** button to change the target database for the source database endpoints.}} + +1. Select the target Redis Cloud Pro database from the **Target database** list. You can type in the database's name to find it. + + {{Select the target database from the database list.}} + +1. If you want to assign the same [Role-based Access Control (RBAC) roles]({{< relref "/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**. + + {{Select **Assign the same ACLs to the target database** to assign the same roles to the target database.}} + +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**. + + {{The **Redirect endpoints** button redirects the source database endpoints to the target database.}} + +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 stop all traffic to the source database for 5 minutes after the redirection. + +## 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. + +{{The **Revert** button reverts endpoint migration.}} + +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. + + + + + diff --git a/content/operate/rc/subscriptions/upgrade-essentials-pro.md b/content/operate/rc/subscriptions/upgrade-essentials-pro.md index 10bfcb563f..7650813dc5 100644 --- a/content/operate/rc/subscriptions/upgrade-essentials-pro.md +++ b/content/operate/rc/subscriptions/upgrade-essentials-pro.md @@ -15,7 +15,7 @@ Redis Cloud Essentials supports low throughput workflows. It supports a range of For more information about the different subscription plans, see [Subscription plans]({{< relref "/operate/rc/subscriptions#subscription-plans" >}}). -To upgrade your Essentials plan, see [Upgrade subscription plan]({{< relref "/operate/rc/subscriptions/view-essentials-subscription#upgrade-plan" >}}). +To upgrade your Essentials plan to another essential plan, see [Upgrade subscription plan]({{< relref "/operate/rc/subscriptions/view-essentials-subscription#upgrade-plan" >}}). ## Upgrade Essentials subscription to Pro @@ -25,19 +25,20 @@ To upgrade your Essentials database to Redis Cloud Pro: 1. [Create a new database in Redis Cloud Pro](#create-rcp) with the right specifications to be able to migrate your database. -1. [Migrate your Essentials database](#migrate-database) to your new Redis Cloud Pro database. +1. [Migrate the data in your Essentials database](#migrate-database) to your new Redis Cloud Pro database. + +1. [Migrate your endpoints](#migrate-endpoints) to your new Redis Cloud Pro database. ### Create Redis Cloud Pro database {#create-rcp} [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}) with the following specifications: - Select **Redis Cloud Pro** for your subscription type. -- Select the **Version** that matches the Redis version your Essentials subscriptions use. - In the [**Sizing tab**]({{< relref "/operate/rc/databases/create-database/create-pro-database-new#sizing-tab" >}}), create your databases with the following specifications: - Set the memory limit to comply with [Active-Passive memory requirements]({{< relref "/operate/rc/databases/migrate-databases#active-passive-memory-requirements" >}}) if you want to migrate your database using [Active-Passive]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}). - - Select any advanced capabilities that your Essentials database offers. You can find a list of enabled advanced capabilities in the [Configuration tab]({{< relref "/operate/rc/databases/view-edit-database#configuration-details-tab" >}}) of your database. + - In **More options**, set the **Port** to **Manually assign**, and enter the port of your Essentials database. You must set the port number to match the port of your Essentials database if you want to migrate your database endpoints. You can find the port in the endpoint of your database on the **Configuration** tab of your database. -### Migrate database +### Migrate data You can migrate your Redis Cloud Essentials database to your new Redis Cloud Pro subscription using any method in the [Migrate databases]({{< relref "/operate/rc/databases/migrate-databases" >}}) guide. This guide uses [Active-Passive]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}) to migrate databases between subscriptions in the same account. @@ -85,11 +86,46 @@ Before you follow this guide, be aware of the following limitations: {{When the data is migrated, the target database status displays `Synced`.}} - Active-Passive sync lets you migrate data while apps and other connections are using the source database. Once the data is migrated, you should migrate active connections to the target database before you move on. + Active-Passive sync lets you migrate data while apps and other connections are using the source database. Once the data is migrated, you should migrate active connections to the target database before you move on if you choose not to redirect your endpoints. + +### Redirect database endpoints + +Redirecting your database endpoints after migrating your data lets you direct connections to your new database without any code changes. + +{{< note >}} +See [Redirect dynamic endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) for more information on the limitations and requirements for endpoint redirection. +{{< /note >}} + +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**. + + {{Use the **Redirect endpoints** button to change the target database for the source database endpoints.}} + +1. Select the target Redis Cloud Pro database from the **Target database** list. You can type in the database's name to find it. + + You can choose whether to map the original endpoint to the **Public** or the **Private** endpoint. + + {{Choose whether to map the original endpoint to the Public or Private endpoint.}} + +1. If you want to assign the same [Role-based Access Control (RBAC) roles]({{< relref "/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**. + + {{Select **Assign the same ACLs to the target database** to assign the same roles to the target database.}} + +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**. + + {{The **Redirect endpoints** button redirects the source database endpoints to the target database.}} + +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. -1. After your data and connections are migrated, turn off **Active-Passive Redis** from the target database. +You can revert endpoint migration within 24 hours to restore the original endpoints. Select **Revert** to revert endpoint migration. -1. [Delete the source database]({{< relref "/operate/rc/databases/delete-database" >}}). +{{The **Revert** button reverts endpoint migration.}} +After the 24-hour window, you can no longer revert to the endpoint to the original database. +### Delete Essentials database +After you migrate your data and redirect your endpoints, turn off **Active-Passive Redis** from the target database, and then [delete the source database]({{< relref "/operate/rc/databases/delete-database" >}}). diff --git a/static/images/rc/database-details-configuration-tab-general-flexible.png b/static/images/rc/database-details-configuration-tab-general-flexible.png index 7c11cd9198..675ca4f958 100644 Binary files a/static/images/rc/database-details-configuration-tab-general-flexible.png and b/static/images/rc/database-details-configuration-tab-general-flexible.png differ diff --git a/static/images/rc/database-metrics-connect-prometheus.png b/static/images/rc/database-metrics-connect-prometheus.png new file mode 100644 index 0000000000..064cf04db8 Binary files /dev/null and b/static/images/rc/database-metrics-connect-prometheus.png differ diff --git a/static/images/rc/databases-configuration-general-endpoints-legacy.png b/static/images/rc/databases-configuration-general-endpoints-legacy.png new file mode 100644 index 0000000000..e56c39ac30 Binary files /dev/null and b/static/images/rc/databases-configuration-general-endpoints-legacy.png differ diff --git a/static/images/rc/databases-configuration-general-endpoints.png b/static/images/rc/databases-configuration-general-endpoints.png new file mode 100644 index 0000000000..c8ec62ee60 Binary files /dev/null and b/static/images/rc/databases-configuration-general-endpoints.png differ diff --git a/static/images/rc/databases-configuration-redirect-endpoints.png b/static/images/rc/databases-configuration-redirect-endpoints.png new file mode 100644 index 0000000000..e029cd1fe1 Binary files /dev/null and b/static/images/rc/databases-configuration-redirect-endpoints.png differ diff --git a/static/images/rc/migrate-data-redirect-acknowledge.png b/static/images/rc/migrate-data-redirect-acknowledge.png new file mode 100644 index 0000000000..6cf2ba5468 Binary files /dev/null and b/static/images/rc/migrate-data-redirect-acknowledge.png differ diff --git a/static/images/rc/migrate-data-redirect-assign-acls.png b/static/images/rc/migrate-data-redirect-assign-acls.png new file mode 100644 index 0000000000..39e350f867 Binary files /dev/null and b/static/images/rc/migrate-data-redirect-assign-acls.png differ diff --git a/static/images/rc/migrate-data-redirect-essentials-endpoints.png b/static/images/rc/migrate-data-redirect-essentials-endpoints.png new file mode 100644 index 0000000000..9aa7ca3a1c Binary files /dev/null and b/static/images/rc/migrate-data-redirect-essentials-endpoints.png differ diff --git a/static/images/rc/migrate-data-redirect-pro-endpoints.png b/static/images/rc/migrate-data-redirect-pro-endpoints.png new file mode 100644 index 0000000000..4c524e74da Binary files /dev/null and b/static/images/rc/migrate-data-redirect-pro-endpoints.png differ diff --git a/static/images/rc/migrate-data-redirect-revert.png b/static/images/rc/migrate-data-redirect-revert.png new file mode 100644 index 0000000000..28fdcb9505 Binary files /dev/null and b/static/images/rc/migrate-data-redirect-revert.png differ