Move content and fix relrefs

Author: cmilesb

content/operate/rc/accounts/account-settings.md

@@ -20,7 +20,7 @@ The available tabs depend on your subscription type and may include:
 
 - The **Account** tab displays basic information associated with your account, including general info, address details, time zone setting, security settings, and provider integration details.
 
-- The **Cloud Account** tab is displayed for Redis Cloud Pro subscriptions hosted on Amazon Web Services (AWS).  To learn more, see [Manage AWS cloud accounts]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/" >}}).
+- The **Cloud Account** tab is displayed for Redis Cloud Pro subscriptions hosted on Amazon Web Services (AWS).  To learn more, see [Manage AWS cloud accounts]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/" >}}).
 
 - The **Integrations** tab lets you manage certain integrations. For more information on the Confluent Cloud integration, see [Use the Redis Sink Confluent Connector]({{< relref "/integrate/confluent-with-redis-cloud/" >}}).
 

content/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources/aws-console.md

@@ -62,7 +62,7 @@ You can reduce network transfer costs and network latency by ensuring your Redis
 
 To specify the availability zone for your cluster, select *Manual Selection* under **Allowed Availability Zones**. 
 
-For Google Cloud clusters and [self-managed AWS cloud accounts]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/" >}}), select an availability zone from the **Zone name** list.
+For Google Cloud clusters and [self-managed AWS cloud accounts]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/" >}}), select an availability zone from the **Zone name** list.
 
 {{<image filename="images/rc/availability-zones-no-multi-az.png" width="95%" alt="Select one availability zone when Multi-AZ is turned off." >}}
 

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

@@ -131,8 +131,8 @@ 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) |
-| **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) |
+| **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/subscriptions/aws-cloud-accounts" >}}) are enabled) |
+| **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/subscriptions/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/" >}})|
 | **Maintenance windows** | Determines when Redis can perform [maintenance]({{< relref "/operate/rc/subscriptions/maintenance" >}}) on your databases. Select **Manual** if you want to set [manual maintenance windows]({{< relref "/operate/rc/subscriptions/maintenance/set-maintenance-windows" >}}). |

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

@@ -53,7 +53,7 @@ Before you can set up Transit Gateway:
 1. [Share the transit gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-transit-gateways.html#tgw-sharing) from the [AWS resource access manager](https://console.aws.amazon.com/ram/).
 
 {{< note >}}
-If you have a self-managed AWS account, you will need to set its IAM Instance Policy to include Transit Gateway. See [Create IAM resources using the AWS console]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources/aws-console.md" >}}) (deprecated) for more information.
+If you use Redis Cloud Bring your own Cloud, you will need to set its IAM Instance Policy to include Transit Gateway. See [Create IAM resources using the AWS console]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/aws-console.md" >}}) for more information.
 {{< /note >}}
 
 ## AWS Transit Gateway

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

@@ -0,0 +1,30 @@
+---
+LinkTitle: Bring your own Cloud
+Title: Redis Cloud Bring your own Cloud
+alwaysopen: false
+categories:
+- docs
+- operate
+- rc
+description: Describes how to provision your Redis Cloud subscription to use an existing
+  cloud provider account.
+bannerText: This article is for Redis Cloud Bring your Own Cloud (BYOC). If you're interested in Redis Cloud BYOC, [contact sales](https://redis.io/meeting/).
+bannerChildren: true
+hidden: true
+hideListLinks: true
+weight: 80
+aliases:
+  - /operate/rc/how-to/view-edit-cloud-account
+  - /operate/rc/cloud-accounts
+  - /operate/rc/cloud-integrations/aws-cloud-accounts
+---
+
+Redis Cloud Bring your own Cloud (BYOC) lets organizations deploy Redis Cloud directly within their own AWS environments. 
+
+## Benefits
+
+## Use Cases
+
+## Set up Redis Cloud BYOC
+
+

content/operate/rc/subscriptions/aws-cloud-accounts/_index.md

@@ -1,35 +1,23 @@
 ---
-LinkTitle: AWS cloud accounts
-Title: Manage AWS cloud accounts
-alwaysopen: false
-bannerChildren: true
-bannerText: Self-managed AWS accounts are deprecated, so this article has been archived.
+Title: Create and edit Cloud accounts
+LinkTitle: Create and edit Cloud accounts
 categories:
 - docs
 - operate
 - rc
-description: Describes how to provision your Redis Cloud subscription to use existing
-  cloud provider accounts.
-hidden: true
+description: null
 hideListLinks: true
-weight: 40
-aliases:
-  - /operate/rc/how-to/view-edit-cloud-account
-  - /operate/rc/cloud-accounts
+weight: 2
 ---
 
-Many customers use cloud provider accounts provisioned and maintained by Redis.  
-
-Customers with existing Amazon Web Services (AWS) accounts can provision their Redis Cloud Pro subscriptions to use their existing AWS accounts.  
-
 To do so, you associate your existing AWS account as a _cloud account_ for your subscription.  This requires setting up and entering credentials that enable monitoring, maintenance, and technical support of your subscription.
 
 To do this, you need:
 
 1. A programmatic user with an access key and a secret access key for that user.
 1. A console role that allows administrative access to the cloud account.
 
-These resources need to exist before adding the cloud account to your subscription.  To learn more, see [Create IAM resources]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources" >}}).
+These resources need to exist before adding the cloud account to your subscription.  To learn more, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources" >}}).
 
 {{<note>}}
 Once an AWS account has been configured as a cloud account, you must _not_:
@@ -88,7 +76,7 @@ If the **Add account** button is inactive, verify that:
 - The resources exist in your AWS account
 - Each resource provides the required level of access
 
-For help, see [Create IAM resources]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources" >}}).
+For help, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources" >}}).
 
 ## Edit cloud account details
 
@@ -122,4 +110,4 @@ To remove a cloud account from your Redis cloud subscription, select the cloud a
 
 We strongly recommend using dedicated identity and access management (IAM) resources to manage your AWS cloud accounts.  These resources should not be shared with any other task, account, or process.
 
-To learn more, see [Create IAM resources for AWS cloud accounts]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources" >}}).
+To learn more, see [Create IAM resources for AWS cloud accounts]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources" >}}).

content/operate/rc/cloud-integrations/aws-cloud-accounts/_index.md renamed to content/operate/rc/subscriptions/aws-cloud-accounts/cloud-account-settings.md

@@ -7,7 +7,7 @@ categories:
 description: null
 hideListLinks: true
 linkTitle: Create IAM resources
-weight: $weight
+weight: 1
 ---
 For most Redis Cloud Pro databases deployed to Amazon Web Services (AWS), we manage the supporting infrastructure for you in dedicated AWS accounts.
 
@@ -22,7 +22,7 @@ In the new AWS account, you need to create:
 - A user with an **access key**
 - A role that grants **AWS console access**
 
-Save the access key in a secure location so that you can enter it when you [register the cloud account]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/" >}}) with your the Redis Cloud subscription.
+Save the access key in a secure location so that you can enter it when you [register the cloud account]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/" >}}) with your the Redis Cloud subscription.
 
 {{< warning >}}
 We use the provided credentials to configure your AWS environment and provision required resources.
@@ -37,6 +37,6 @@ For help creating an AWS user, see the [AWS IAM documentation](https://docs.aws.
 
 You can use one of the following tools to create IAM resources:
 
-- [CloudFormation]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources/cloudformation.md" >}}) - The AWS automation tool
-- [Terraform]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources/terraform.md" >}}) - Widely supported in the Redis community for additional automation
-- The [AWS Console]({{< relref "/operate/rc/cloud-integrations/aws-cloud-accounts/iam-resources/aws-console.md" >}})
+- [CloudFormation]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/cloudformation" >}})
+- [Terraform]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/terraform" >}})
+- The [AWS Console]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/aws-console" >}})