From 42f57511fca4066a9a3f74e2bb7e9bed8c6ee6ad Mon Sep 17 00:00:00 2001 From: Cameron Bates Date: Fri, 26 Sep 2025 12:41:45 -0400 Subject: [PATCH 1/3] RC RDI: Changelog and clarify security group rules --- .../operate/rc/changelog/september-2025.md | 25 +++++++++++++++++++ content/operate/rc/databases/rdi/setup.md | 17 ++++++++++--- 2 files changed, 38 insertions(+), 4 deletions(-) create mode 100644 content/operate/rc/changelog/september-2025.md diff --git a/content/operate/rc/changelog/september-2025.md b/content/operate/rc/changelog/september-2025.md new file mode 100644 index 0000000000..aead16ddf2 --- /dev/null +++ b/content/operate/rc/changelog/september-2025.md @@ -0,0 +1,25 @@ +--- +Title: Redis Cloud changelog (September 2025) +alwaysopen: false +categories: +- docs +- operate +- rc +description: New features, enhancements, and other changes added to Redis Cloud during + September 2025. +highlights: Data Integration +linktitle: September 2025 +weight: 70 +tags: +- changelog +--- + +## New features + +### Data Integration + +Redis Cloud now supports [Redis Data Integration (RDI)]({{< relref "/operate/rc/databases/rdi" >}}) to create data pipelines that ingest data from a supported primary database to Redis. + +Using a data pipeline lets you have a cache that is always ready for queries. RDI Data pipelines ensure that any changes made to your primary database are captured in your Redis cache within a few seconds, preventing cache misses and stale data within the cache. + +See [Data Integration]({{< relref "/operate/rc/databases/rdi" >}}) to learn how to set up data pipelines with Redis Cloud. \ No newline at end of file diff --git a/content/operate/rc/databases/rdi/setup.md b/content/operate/rc/databases/rdi/setup.md index 0edcd752fa..e05ba183aa 100644 --- a/content/operate/rc/databases/rdi/setup.md +++ b/content/operate/rc/databases/rdi/setup.md @@ -80,7 +80,7 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv - **Scheme**: Select **Internal**. - **Load balancer IP address type**: Select **IPv4**. 1. In **Network mapping**, select the VPC and availability zone associated with your source database. -1. In **Security groups**, select the security group associated with your source database. +1. In **Security groups**, select the security group associated with your source database, or another security group that allows traffic from PrivateLink and allows traffic to the database. 1. In **Listeners and routing**: 1. Select **Create target group** to [create a target group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html) with the following settings: 1. In **Specify group details**: @@ -93,7 +93,11 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv - **Port**: Enter your source database's port. - **Default action**: Select the target group you created in the previous step. 1. Review the network load balancer settings, and then select **Create load balancer** to continue. -1. After the network load balancer is active, select **Security**, and then select the security group ID to open the Security group settings. +1. After the network load balancer is active, select **Security**. + + If you selected the same security group as your source database, you must not enforce security group rules on PrivateLink traffic. Select **Edit** and then deselect **Enforce inbound rules on PrivateLink traffic**, and then select **Save changes**. + +1. Select the security group ID to open the Security group settings. 1. Select **Edit inbound rules**, then **Add rule** to add a rule with the following settings: - **Type**: Select **HTTP**. - **Source**: Select **Anywhere - IPv4**. @@ -146,7 +150,7 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv - **Scheme**: Select **Internal**. - **Load balancer IP address type**: Select **IPv4**. 1. In **Network mapping**, select the VPC and availability zone associated with your source database. -1. In **Security groups**, select the security group associated with your source database. +1. In **Security groups**, select the security group associated with your source database, or another security group that allows traffic from PrivateLink and allows traffic to the database. 1. In **Listeners and routing**: 1. Select **Create target group** to [create a target group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html) with the following settings: 1. In **Specify group details**: @@ -164,7 +168,12 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv - **Port**: Enter your source database's port. - **Default action**: Select the target group you created in the previous step. 1. Review the network load balancer settings, and then select **Create load balancer** to continue. -1. After the network load balancer is active, select **Security**, and then select the security group ID to open the Security group settings. +1. After the network load balancer is active, select **Security**. + + If you selected the same security group as your source database, you must not enforce security group rules on PrivateLink traffic. Select **Edit** and then deselect **Enforce inbound rules on PrivateLink traffic**, and then select **Save changes**. + +1. Select the security group ID to open the Security group settings. + 1. Select **Edit inbound rules**, then **Add rule** to add a rule with the following settings: - **Type**: Select **HTTP**. - **Source**: Select **Anywhere - IPv4**. From c05d2d2a23b564ccadb769cd47b5cee40aa9ede8 Mon Sep 17 00:00:00 2001 From: Cameron Bates Date: Fri, 26 Sep 2025 13:29:41 -0400 Subject: [PATCH 2/3] Clarify username/pass should be for RDI user, not primary/master user --- content/operate/rc/databases/rdi/setup.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/operate/rc/databases/rdi/setup.md b/content/operate/rc/databases/rdi/setup.md index e05ba183aa..ed602f9eae 100644 --- a/content/operate/rc/databases/rdi/setup.md +++ b/content/operate/rc/databases/rdi/setup.md @@ -233,10 +233,10 @@ The required secrets depend on your source database's security configuration. Th | Security configuration | Required secrets | | :-- | :-- | -| Username and password only | | -| TLS connection | | -| mTLS connection | | -| mTLS connection with client key passphrase | | +| Username and password only | | +| TLS connection | | +| mTLS connection | | +| mTLS connection with client key passphrase | | Select a tab to learn how to create the required secret. @@ -251,8 +251,8 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv - **Key/value pairs**: Enter the following key/value pairs. - - `username`: Database username - - `password`: Database password + - `username`: Database username for the RDI pipeline user + - `password`: Database password for the RDI pipeline user {{< embed-md "rc-rdi-secrets-encryption-permissions.md" >}} From 5a543d08611ea20539ac74d7131053b89192a424 Mon Sep 17 00:00:00 2001 From: Cameron Bates Date: Fri, 26 Sep 2025 13:39:27 -0400 Subject: [PATCH 3/3] Add instructions to save secret ARN to each secret --- content/embeds/rc-rdi-secrets-permissions.md | 4 +++- content/operate/rc/databases/rdi/setup.md | 6 +----- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/content/embeds/rc-rdi-secrets-permissions.md b/content/embeds/rc-rdi-secrets-permissions.md index 74867bd35d..6ca05645d3 100644 --- a/content/embeds/rc-rdi-secrets-permissions.md +++ b/content/embeds/rc-rdi-secrets-permissions.md @@ -14,4 +14,6 @@ } } ] } -``` \ No newline at end of file +``` + +After you store this secret, you can view and copy the [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#iam-resources) of your secret on the secret details page. Save the secret ARN to use when you [define your source database]({{}}). \ No newline at end of file diff --git a/content/operate/rc/databases/rdi/setup.md b/content/operate/rc/databases/rdi/setup.md index ed602f9eae..f265313aef 100644 --- a/content/operate/rc/databases/rdi/setup.md +++ b/content/operate/rc/databases/rdi/setup.md @@ -294,12 +294,10 @@ After you create the secret, you need to add permissions to allow the data pipel In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. Select the private key secret you just created and then select **Edit permissions**. -Add the following permissions to your secret: +Add the following permissions to your secret. Replace `` with the AWS account ID for the Redis Cloud cluster that you saved earlier. {{< embed-md "rc-rdi-secrets-permissions.md" >}} -Replace `` with the AWS account ID for the Redis Cloud cluster that you saved earlier. - --tab-sep-- In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) of type **Other type of secret** with the following settings: @@ -310,8 +308,6 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv {{< /multitabs >}} -After you store this secret, you can view and copy the [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#iam-resources) of your secret on the secret details page. - ## Next steps After you have set up your source database and prepared connectivity and credentials, select **Define source database** to [define your source connection and data pipeline]({{}}).