Merge branch 'master' into release-rs-fuji-mar

content/embeds/rc-vpc-peering-cidr-list.md

@@ -0,0 +1 @@
+If you've enabled the database's [CIDR allow list]({{< relref "/rc/security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/rc/security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.

content/kubernetes/release-notes/7-2-4-releases/7-2-4-12-03-24.md

@@ -83,7 +83,7 @@ Any distribution not listed below is not supported for production workloads.
 #### OpenShift images
 
 - **Redis Enterprise**: `registry.connect.redhat.com/redislabs/redis-enterprise:7.2.4-105.rhel8-openshift`
-    (or `redislabs/redis-enterprise:7.2.4-92.rhel7-openshift` if upgrading from RHEL 7)
+    (or `redislabs/redis-enterprise:7.2.4-105.rhel7-openshift` if upgrading from RHEL 7)
 - **Operator**: `registry.connect.redhat.com/redislabs/redis-enterprise-operator:7.2.4-12`
 - **Services Rigger**: `registry.connect.redhat.com/redislabs/services-manager:7.2.4-12`
 
@@ -142,4 +142,4 @@ The limitations below are specific to the Redis Enterprise for Kubernetes produc
 
 - **Long cluster names cause routes to be rejected  (RED-25871)** A cluster name longer than 20 characters will result in a rejected route configuration because the host part of the domain name exceeds 63 characters. The workaround is to limit the cluster name to 20 characters or fewer.
 
-- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.
+- **Cluster CR (REC) errors are not reported after invalid updates (RED-25542)** A cluster CR specification error is not reported if two or more invalid CR resources are updated in sequence.

content/rc/changelog/march-2024.md

@@ -0,0 +1,16 @@
+---
+Title: Redis Cloud changelog (March 2024)
+linktitle: March 2024
+description: New features, enhancements, and other changes added to Redis Cloud during March 2024.
+highlights: Fixed plans through Google Cloud Marketplace
+weight: 60
+alwaysopen: false
+categories: ["RC"]
+aliases: []
+---
+
+## New Features
+
+### Fixed subscriptions through Google Cloud Marketplace
+
+You can now use your [Google Cloud Marketplace]({{<relref "/rc/cloud-integrations/gcp-marketplace/">}}) account to pay for your Fixed subscriptions as well as your Flexible subscriptions. 

content/rc/changelog/november-2023.md

@@ -15,7 +15,7 @@ aliases: []
 
 Redis is updating our [Fixed subscriptions]({{<relref "/rc/subscriptions/create-fixed-subscription">}}) on Redis Cloud. These plans offer increased capacity at lower prices compared to legacy plans.
 
-See [Fixed plan subscription tiers]({{<relref "/rc/subscriptions/create-fixed-subscription#fixed-plan-subscription-tiers">}}) for an updated list of all Fixed plans.
+See [Fixed plan subscription tiers]({{<relref "/rc/subscriptions/create-fixed-subscription#fixed-plans">}}) for an updated list of all Fixed plans.
 
 ### Redis 7.2 Fixed region support
 

content/rc/cloud-integrations/aws-marketplace/_index.md

@@ -1,5 +1,5 @@
 ---
-Title: Flexible subscriptions with AWS Marketplace
+Title: Sign up for Redis Cloud with AWS Marketplace
 LinkTitle: AWS Marketplace 
 description: Shows how to subscribe to Redis Cloud using AWS Marketplace
 weight: $weight
@@ -11,7 +11,7 @@ aliases: /rc/cloud-integrations/aws-marketplace/
 
 You can use AWS Marketplace to subscribe to Redis Cloud through AWS Marketplace.  This lets you provision according to your needs and pay using your AWS account.
 
-Here's how to create a new Flexible subscription as part of your AWS Marketplace commitment.
+Here's how to subscribe to Redis Cloud with AWS Marketplace:
 
 1.  Sign in to the [AWS console](https://console.aws.amazon.com/).
 

content/rc/cloud-integrations/gcp-marketplace/_index.md

@@ -1,5 +1,5 @@
 ---
-Title: Flexible subscriptions with Google Cloud Marketplace
+Title: Sign up for Redis Cloud with Google Cloud Marketplace
 LinkTitle: Google Cloud Marketplace
 description: Shows how to subscribe to Redis Cloud using Google Cloud Marketplace
 weight: $weight
@@ -11,7 +11,7 @@ aliases: /rc/cloud-integrations/gcp-marketplace/
 
 You can use Google Cloud Marketplace to subscribe to Redis Cloud. This lets you provision according to your needs and pay using your Google Cloud account.
 
-Here's how to create a new Flexible subscription as part of your Google Cloud Marketplace commitment:
+Here's how to subscribe to Redis Cloud with Google Cloud Marketplace:
 
 1.  Sign in to the [Google Cloud console](https://console.cloud.google.com/).
 
@@ -50,10 +50,10 @@ Here's how to create a new Flexible subscription as part of your Google Cloud Ma
 
     {{<image filename="images/rc/gcp-marketplace-manage-on-provider.png" alt="The Manage on Provider button" >}}{{< /image >}}
 
-At this point, you can create a new Flexible subscription using the [standard workflow]({{<relref "/rc/subscriptions/create-flexible-subscription">}}), with one important change. You don't need to enter a payment method, as it automatically uses your Google Cloud Marketplace account.
+At this point, you can create a new [Fixed]({{<relref "/rc/subscriptions/create-fixed-subscription">}}) or [Flexible]({{<relref "/rc/subscriptions/create-flexible-subscription">}}) subscription using the standard workflow, with one important change. You don't need to enter a payment method, as it automatically uses your Google Cloud Marketplace account.
 
 To confirm this, review the payment method associated with your subscription.
 
 Additional users can be added on the Redis Cloud console using the [Access Management]({{<relref "/rc/security/access-control/access-management">}}) page.
 
-If your Google Cloud Marketplace account is deactivated or otherwise unavailable, you can't use your Flexible subscription until you update the billing method.  For help, [contact support](https://redis.com/company/support/).
+If your Google Cloud Marketplace account is deactivated or otherwise unavailable, you can't use your subscription until you update the billing method.  For help, [contact support](https://redis.com/company/support/).

content/rc/databases/configuration/high-availability.md

@@ -34,15 +34,17 @@ Your replication options depend on your [subscription plan]({{<relref "/rc/subsc
 
 After database creation, you can still enable or turn off replication.  However, [zone settings]({{<relref "/rc/databases/configuration/high-availability#zone-setting-maintenance">}}) are only configurable during database creation.  
 
-## Performance and cost impact 
+## Performance impact 
 
 Replication can affect performance as traffic increases to synchronize all copies. 
 
-Database storage costs also increase:
+## Memory limit
 
-- For Fixed plans, single-zone and multi-zone replication effectively doubles storage costs
+For both Fixed and Flexible plans, replication doubles the memory limit you need for your database. 
 
-- For Flexible and Annual plans, replication requires additional shards and can affect subscription costs
+For Fixed plans, The size of the plan you choose includes replication. Therefore, if you choose replication, the dataset size you can use is half of the stated plan size. For example, if you choose a 1GB plan, Redis allocates 512 GB for the memory limit, and the other 512 MB for Replication.
+
+For Flexible and Annual plans, you also need to double the amount of memory needed if you choose replication.
 
 ## Zone setting maintenance
 

content/rc/databases/create-database.md

@@ -129,7 +129,7 @@ Here are some general guidelines:
 
 - Memory limit represents an upper limit.  You cannot store more data than the memory limit.  Depending on your other selections, available memory for data may be much less than expected.
 
-- Replication doubles memory consumption; that is, 512MB of data requires at least 1GB of memory limit when replication is enabled.
+- Replication doubles memory consumption; that is, 512MB of data requires at least 1GB of memory limit when replication is enabled. This also affects Fixed plans. For example, if you subscribe to a 1 GB Fixed plan, Redis will allocate 512 MB for your dataset and the other 512 MB for replication.
 
 - Active-Active also doubles memory consumption and the effect is cumulative with replication's impact. Since Active-Active requires replication to be turned on, the memory limit impact can be as large as four times (4x) the original data size.
 
@@ -141,12 +141,14 @@ Memory limits in Redis Cloud are subject to the same considerations as Redis Ent
 
 Throughput is the amount of operations a database can handle over a certain period of time. For most Redis Cloud databases, throughput is defined in operations per second (ops/sec).
 
-Databases with search and query enabled use the number of shards to determine throughput. To determine how many shards you need for your database, use the [sizing calculator](https://redis.com/modules/redis-search/redisearch-sizing-calculator/).
-
-Your actual throughput may not match the throughput you set when you create your database. The following things can affect your database's throughput:
+We assume a typical workload that includes a different mix of commands and an average key and value size of 1KB. Therefore, your actual throughput may be higher or lower than the throughput you set when you create your database. The following properties can affect your database's throughput:
 - **Command complexity**: O(N) and O(log(N)) commands will take more time than O(1) commands, and will affect throughput accordingly.
-- **Key and value sizing**: If your database's keys and values are very large, setting and reading those keys may take more time and affect throughput.
+- **Key and value sizing**: If your database's keys and values are very large, your actual throughput may be lower than expected. If the keys and values are smaller than the typical workload, the actual throughput might be higher than expected.
 - **Replication**: Using [multi-zone replication]({{<relref "rc/databases/configuration/high-availability">}}) affects throughput as each write operation is executed asynchronously in each zone.
+- **Security**: Some security options, such as [transport layer security]({{< relref "/rc/security/database-security/tls-ssl" >}}), may affect throughput.
+- **Number of client connections**: The number of client connections affects throughput. Increasing or decreasing the number of client connections can result in higher or lower throughput.
+
+Databases with search and query enabled use the number of shards to determine throughput. To determine how many shards you need for your database, use the [sizing calculator](https://redis.com/modules/redis-search/redisearch-sizing-calculator/).
 
 ### OSS Cluster API
 

content/rc/rc-quickstart.md

@@ -18,7 +18,7 @@ You'll learn how to:
 
 1.  Connect to your database
 
-If you already have an account, see [Create a Fixed subscription]({{< relref "/rc/subscriptions/create-fixed-subscription" >}}) to create a Free 30MB subscription. Free plans are a tier of fixed plans; this provides an easy upgrade path when you need it.
+If you already have an account, see [Create a Fixed subscription]({{< relref "/rc/subscriptions/create-fixed-subscription" >}}) to create a Free 30MB subscription. Free plans are a type of fixed plans; this provides an easy upgrade path when you need it.
 
 If you already have a subscription, see [Manage subscriptions]({{< relref "/rc/subscriptions/" >}}) and [Manage databases]({{< relref "/rc/databases/" >}}).
 

content/rc/security/aws-transit-gateway.md

@@ -156,4 +156,8 @@ To finish Transit gateway setup, [update your route tables for the peering conne
 
 After Transit gateway is established, we recommend switching your application connection string to the private endpoint.
 
+{{< note >}}
+If you've enabled the database's [CIDR allow list]({{< relref "/rc/security/cidr-whitelist" >}}), you must also [add the Transit Gateway's IP address to the CIDR allow list]({{< relref "/rc/security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.
+{{< /note >}}
+
 

content/rc/security/cidr-whitelist.md

@@ -14,21 +14,19 @@ The [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) [allow
 
 You can configure your database's CIDR allow list to restrict client connections to a specific range of IP addresses.
 
-
 {{< note >}}
 To use the CDIR allow list, you must be on either Redis Cloud Fixed, Flexible, or Annual plans.  This feature is not supported on Redis Cloud Free.
 {{< /note >}}
 
-
 ### Define CIDR allow list
 
 To define the CIDR allow list for a database:
 
 1. Select **Databases** from the [Redis Cloud console](https://app.redislabs.com/) menu and then select your database from the list.
 
-1. From the database's **Configuration** screen, select the **Edit database** button:
+1. From the database's **Configuration** screen, select the **Edit database** button.
 
-1. In the **Security** section, turn on the **CIDR allow list** toggle:
+1. In the **Security** section, turn on the **CIDR allow list** toggle.
 
 1. Enter the first IP address (in CIDR format) you want to allow in the text box and then select the check mark to add it to the allow list:
 
@@ -44,6 +42,10 @@ To define the CIDR allow list for a database:
 
 1. Select **Save database** to apply your changes.
 
+{{< note >}}
+The database CIDR allow list applies to both the public endpoint and the private endpoint. If you use connectivity options such as [VPC Peering]({{< relref "/rc/security/vpc-peering" >}}) and [Transit Gateway]({{<relref "/rc/security/aws-transit-gateway">}}) to connect to your database via the private endpoint, you must also add those IPs to your database's CIDR allow list.
+{{< /note >}}
+
 ## Subscription allow list
 
 If you use a [self-managed, external cloud account]({{<relref "/rc/cloud-integrations">}}) to host your Redis Cloud deployment, you can configure a subscription-wide allow list

content/rc/security/private-service-connect.md

@@ -132,6 +132,10 @@ Once your Private Service Connect endpoint is active, you can connect your appli
 
 1. Copy the endpoint and use it in your application to connect to your database.
 
+{{< note >}}
+Once your Private Service Connect endpoint is active, you must connect to the database from the Private Service Connect endpoint if you want to connect with Private Service connect. If you previously used the public or private endpoint to connect to your database, you must migrate any connections to the Private Service Connect endpoint.
+{{< /note >}}
+
 
 ## Deactivate Private Service Connect {#deactivate-psc}
 
@@ -159,6 +163,8 @@ To deactivate Private Service Connect for your subscription:
 
     {{<image filename="images/rc/button-subscription-connectivity-psc-remove-service-confirm.png" width="100px" alt="Use the Confirm button to deactivate Private Service Connect." >}}{{< /image >}}
 
+Once you remove all of your Private Service Connect endpoints and deactivate it, you must migrate any connections from a Private Service Connect endpoint to the public or private endpoint of your database.
+
 ## Limitations
 
 Private Service Connect has the following limitations in Redis Cloud:

content/rc/security/vpc-peering.md

@@ -87,6 +87,10 @@ To finish VPC peering setup, [update your route tables for the peering connectio
 
 Once VPC peering is established, we recommend switching your application connection string to the private endpoint.
 
+{{< note >}}
+{{< embed-md "rc-vpc-peering-cidr-list.md"  >}}
+{{< /note >}}
+
 ## Google Cloud VPC peering {#gcp-vpc-peering}
 
 If you want to peer a Redis Cloud VPC with a Google Cloud VPC, you need to:
@@ -126,3 +130,7 @@ To set up VPC peering:
 To approve the VPC peering request between Redis Cloud and Google Cloud, use the [`gcloud` CLI](https://cloud.google.com/sdk/gcloud) to run the **Google cloud command** that you copied before you initiated VPC peering.
 
 Once VPC peering is established, we recommend switching your application connection string to the private endpoint.
+
+{{< note >}}
+{{< embed-md "rc-vpc-peering-cidr-list.md"  >}}
+{{< /note >}}

content/rc/subscriptions/_index.md

@@ -43,7 +43,7 @@ To learn more, see [Redis Cloud Pricing](https://redislabs.com/redis-enterprise-
 
 ### Free plans
 
-Free plans are a tier of Fixed plans designed for training purposes and prototyping. They can be seamlessly upgraded to Fixed plans with no data loss.
+Free plans are a type of Fixed plans designed for training purposes and prototyping. They can be seamlessly upgraded to Fixed plans with no data loss.
 
 ### Fixed plans
 Fixed plans are cost-efficient and designed for low-throughput scenarios. They support a range of availability, persistence, and backup options.  Pricing supports low throughput workloads.