RC: Self-managed encryption private preview - Google Cloud and Subscription creation

content/operate/rc/databases/create-database/create-pro-database-new.md

@@ -130,6 +130,7 @@ The following settings are defined in the **Advanced options** of the **Setup**
 | **Multi-AZ** | Determines if replication spans multiple Availability Zones, which provides automatic failover when problems occur. See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). |
 | **Allowed Availability Zones** | The availability zones for your selected region.<br/><br/>If you choose **Manual selection**, you must select at least one zone ID from the **Zone IDs** list.  For more information, see [Availability zones]({{< relref "/operate/rc/databases/configuration/high-availability#availability-zones" >}}). |
 | **Cloud account** | To deploy these databases to an existing cloud account, select it here.  Use the **Add** button to add a new cloud account.<br/><br/>(Available only if [self-managed cloud vendor accounts]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts" >}}) are enabled) |
+| **Persistent storage encryption** | Select whether to encrypt persistent storage with a Cloud-provider managed key or a [self-managed encryption key]({{< relref "/operate/rc/security/manage-encryption-keys" >}}). If you select **Customer managed key**, you'll get clear instructions to provide access to your self-managed key after you set up your database(s). See [Grant key permissions]({{< relref "/operate/rc/security/manage-encryption-keys#grant-key-permissions" >}}) for more information. |
 | **VPC configuration** | Select **In a new VPC** to deploy to a new [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC).<br/><br/>To deploy these databases to an existing virtual private cloud, select **In existing VPC** and then set VPC ID to the appropriate ID value.<br/><br/>(Available only if [self-managed cloud vendor accounts]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts" >}}) are enabled) |
 | **Deployment CIDR** | The [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) range of IP addresses for your deployment. Redis creates a new [subnet](https://en.wikipedia.org/wiki/Subnetwork) for the **Deployment CIDR** in your [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud) (VPC). It cannot overlap with the CIDR ranges of other subnets used by your account.<br/><br/>For deployments in an existing VPC, the **Deployment CIDR** must be within your VPC's **primary** CIDR range (secondary CIDRs are not supported). |
 | **Auto Tiering**| Determines if your databases are stored only in memory (RAM) or are split between memory and Flash storage (RAM+Flash).  See [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}})|

content/operate/rc/security/manage-encryption-keys.md

@@ -0,0 +1,118 @@
+---
+Title: Self-managed persistent storage encryption
+LinkTitle: Self-managed encryption keys
+alwaysopen: false
+categories:
+- docs
+- operate
+- rc
+description: Learn how to use your own keys for persistent storage encryption on Redis Cloud.
+weight: $weight
+---
+
+Redis Cloud databases write their data to disk whenever [persistence]({{< relref "/operate/rc/databases/configuration/data-persistence.md" >}}) is enabled. 
+
+All data on Redis Cloud is [encrypted at rest]({{< relref "/operate/rc/security/encryption-at-rest" >}}). By default, disk storage is encrypted by keys managed by the cloud provider.
+
+Redis Cloud Pro users can choose to use self-managed encryption keys for persistent storage for all databases in a subscription. 
+
+## Self-managed encryption use cases and benefits
+
+Self-managed persistent storage encryption allows you to:
+- **Shield sensitive data**: With Self-managed persistent storage encryption, you can stop sensitive data exposure by revoking key access at any time.
+- **Meet security and compliance requirements**: With self-managed persistent storage encryption, you may be able to easier meet compliance standards for data security and privacy protection.
+
+Consider using self-managed persistent storage encryption if you have specific organizational needs or requirements for data security.
+
+## Prerequisites
+
+Before you set up self-managed encryption, you must have a self-managed encryption key. 
+
+The encryption key must be hosted by the same cloud provider as your database and must be available in your database's cloud provider region.
+
+Refer to the provider's documentation to create a key:
+<!-- - [Amazon Web Services - Create a KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html) -->
+- [Google Cloud - Create a key](https://cloud.google.com/kms/docs/create-key)
+
+## Set up self-managed encryption
+
+To set up self-managed encryption:
+
+1. [Activate self-managed encryption](#activate-self-managed-encryption) for a new or existing subscription.
+2. [Grant Redis permission to access your encryption key](#grant-key-permissions).
+
+### Activate self-managed encryption
+
+<!-- You can activate self-managed encryption on a [new](#new-subscription) or [existing](#existing-subscription) Redis Cloud Pro subscription.
+
+#### New subscription-->
+
+To activate self-managed encryption when you [create a new Pro subscription]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}):
+
+1. Follow the instructions to [create a Pro database with custom settings]({{< relref "/operate/rc/databases/create-database/create-pro-database-new#custom-settings" >}}). 
+1. On the **Setup** tab, go to **Advanced options > Security** to select persistent storage encryption options. 
+1. Select **Customer managed key** to activate self-managed encryption. 
+1. Select **Continue** to go to the [Sizing tab]({{< relref "/operate/rc/databases/create-database/create-pro-database-new#sizing-tab" >}}). Follow the instructions to provision your database(s).
+
+After you set up your subscription and database(s), your subscription will be **Pending** until you [grant Redis access to your encryption key](#grant-key-permissions). You won't be charged for your subscription while it's pending. 
+
+If you don't grant key permissions after 7 days, we'll remove your initial setup.
+
+<!-- #### Existing subscription
+
+To activate self-managed encryption on an existing Redis Cloud Pro subscription:
+
+1. From the [Redis Cloud console](https://cloud.redis.io/), select the **Subscriptions** menu and then select your subscription from the list. 
+
+1. Open the **Security** tab to view security settings.
+
+1. In the **Persistent storage encryption** section, select **Edit**.
+
+1. Select **Customer managed key**.
+
+1. Select **Save changes** to save your changes. -->
+
+### Grant key permissions
+
+After you activate self-managed encryption, you must grant Redis access to your encryption key so we can use it for storage encryption. 
+
+<!-- #### Amazon Web Services 
+
+#### Google Cloud -->
+
+To grant Redis access to a key on Google Cloud:
+
+1. From your subscription page on the Redis Cloud console, copy the provided Redis service account name.
+
+    {{<image filename="images/rc/cmek-access-roles-google.png" alt="The Grant Redis your customer-managed key section shows the service account needed to add as a principal." width=80% >}}
+
+1. Go to [Key management](https://console.cloud.google.com/security/kms) on the Google Cloud console and locate your key.
+
+1. Add the provided service account as a principal for your key, with one of the following Role options:
+
+    - Add the pre-defined IAM roles [Cloud KMS CryptoKey Encrypter/Decrypter](https://cloud.google.com/kms/docs/reference/permissions-and-roles#cloudkms.cryptoKeyEncrypterDecrypter) and [Cloud KMS Viewer](https://cloud.google.com/kms/docs/reference/permissions-and-roles#cloudkms.viewer), OR
+    - [Create a custom IAM role](https://cloud.google.com/iam/docs/creating-custom-roles#creating) with the following minimal permissions needed to use the key, and then assign that custom role to the principal:
+        - cloudkms.cryptoKeyVersions.useToDecrypt
+        - cloudkms.cryptoKeyVersions.useToEncrypt
+        - cloudkms.cryptoKeys.get
+
+1. Return to the Redis Cloud console. In your subscription page, enter your key's resource name in the **Key resource name** field.
+
+    {{<image filename="images/rc/cmek-provide-resource-name-google.png" alt="The Provide the name of your customer-managed key section lets you provide your key to Redis." width=80% >}}
+
+    At this point, Redis Cloud will check to see if it can access your key. If it can't access your key, make sure that you've added the correct permissions to your key, that the key is available in the database's cloud provider region, and that you have correctly entered your key's resource name.
+
+<!-- 1. Choose a **Deletion grace period** from the list. If Redis Cloud loses access to your key, Redis will notify you and delete your key after the selected grace period. During the grace period, you must provide a new key to prevent data loss. -->
+
+1. After you finish granting access to your key, you can save your changes. For a new subscription, select **Activate** to activate your subscription and start billing.
+
+    {{<image filename="images/rc/cmek-new-subscription-activate.png" alt="The Activate button." width=500px >}}
+
+## Revoke key access
+
+When you have set up self-managed encryption, you can revoke Redis's access to your encryption key at any time through your cloud provider. Redis will delete your plan immediately if we can't access your key.
+
+<!-- Redis will delete your plan after the selected grace period if we can't access your key. During the grace period, you must provide a new key to prevent data loss. -->
+
+
+