Conversation
RC: Seamless endpoint migration phase A
andy-stark-redis
left a comment
There was a problem hiding this comment.
Embed paths need to be fixed but otherwise LGTM.
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
Just checking that the {{ RELEASE DATE}} still isn't known yet?
There was a problem hiding this comment.
current eta is March 22
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
kaitlynmichael
left a comment
There was a problem hiding this comment.
Didn't get through it all yet, but here's a few small things.
andy-stark-redis
left a comment
There was a problem hiding this comment.
A few minor style suggestions, otherwise LGTM.
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
current eta is March 22
|
|
||
| ### Dynamic endpoints | ||
|
|
||
| As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
I think we need a section in the docs on "Dynamic endpoints" (maybe in the configuration page, or connectivity?). That would explain a few sentences what Dynamic endpoints are and that you can redirect endpoints, alias of the dB endpoint, bla bla bla.
And link it from here and from other places in the docs
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
| 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. | ||
|
|
There was a problem hiding this comment.
Here I want to add a note regarding the API. I'll describe the process and you will do your magic to make it clear and put here where you think:)
- In the UI, the process is as you described. You just search for your DB in the search
- Using the API is different. Because the Dynamic endpoint can move, the user needs to give us the cluster endpoint and not dynamic one. In the UI we don't need to do adjustments because we just choose the actual DB.. not the endpoint
- What we did:
- We exposed a new attribute in the API on the GET DB call: replicaAsSourceEndpoints
- So the customer will need to use those endpoints if they want to set the replica of the program programmatically.
There was a problem hiding this comment.
We should definitely put this in the API docs. I'll work on adding this to the user docs later.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 3 total unresolved issues (including 2 from previous reviews).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a408c18. Configure here.
andy-stark-redis
left a comment
There was a problem hiding this comment.
There's still a TODO, of course, but LGTM this far.
Co-authored-by: Cameron Bates <102550101+cmilesb@users.noreply.github.com>
|
|
||
| 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. |
There was a problem hiding this comment.
Essentials: you don't have private connectivity (PC), that true. This is an exception. If you choose a private endpoint in Pro, we verify you have a PC configured. if so, we allow. If you don't have PC and you try to redirect from essentials to private endpoint in Pro, we don't allow it.
Pro: You're right - we block you if you don't have the same connectivity method. You might have, for example, 3 VPC peerings in the source and only 1 of them in the target - that's what we allow. You have to have at least one overlapping PC method in Pro->Pro redirections
|
|
||
| For databases created after April 21, 2026, you can [redirect these endpoints]({{< relref "/operate/rc/databases/redirect-endpoints" >}}) to a different database. | ||
|
|
||
| Databases created before April 21, 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. |
There was a problem hiding this comment.
@cmilesb it's not correct with the new approach of the Public preview. Not sure exactly how to write it.. but maybe something like that:
“Dynamic endpoints are enabled gradually, starting with new accounts and then expanding to existing accounts. For existing databases, the Dynamic endpoints section appears under General in the Configuration tab when the feature is available for your account.”
| 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-data) to your new Redis Cloud Pro database. |
There was a problem hiding this comment.
data migration is still optional.. even in Essentials to Pro migration
|
|
||
| 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. |
There was a problem hiding this comment.
@cmilesb I don't see that we edited this section as well
| ### Dynamic endpoints | ||
|
|
||
| As of April 21, 2026, Redis Cloud now generates dynamic endpoints for all databases. Databases created before April 21, 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. | ||
| Redis Cloud now generates dynamic endpoints for all databases. For accounts created before April 20, 2026, dynamic endpoints will be rolled out over the next few weeks. You will be able to view both legacy static endpoints and dynamic endpoints when the feature is available for your account. Static endpoints will still work at this time, but they may be deprecated in the future. |
There was a problem hiding this comment.
I prefer not putting any date here.
My recommendation:
Redis Cloud is gradually rolling out dynamic endpoints across accounts. Static endpoints continue to work at this time, but may be deprecated in the future. Dynamic endpoint redirection is currently available in Public Preview.
| {{<image filename="images/rc/migrate-data-status-synced.png" alt="When the data is migrated, the target database status displays `Synced`." width=100px >}} | ||
|
|
||
| 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. | ||
| 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. You can turn off Active-Passive after you migrate active connections to the target database. |
There was a problem hiding this comment.
let's just remove "You can turn off Active-Passive after you migrate active connections to the target database."

Note
Low Risk
Documentation-only changes plus deletion of a lockfile; no production code paths or runtime behavior are affected.
Overview
Documents Redis Cloud dynamic endpoints and the new endpoint redirection workflow, including a new
redirect-endpoints.mdguide (compatibility checks, limitations, traffic blocking/unblocking, and revert window) and an April 2026 changelog entry announcing the features.Updates connection and migration/upgrade docs to steer users toward dynamic endpoints and describe redirecting endpoints as the preferred cutover step (including Essentials→Pro upgrade flow), and refreshes Prometheus setup instructions across integration pages via a reusable embed for obtaining the Prometheus endpoint from the console/API.
Separately removes the Rust
Cargo.lockfrom the rate-limiter demo content.Reviewed by Cursor Bugbot for commit a1a7b56. Bugbot is set up for automated code reviews on this repo. Configure here.