Skip to content

Commit 659b15d

Browse files
committed
RC: Bring your own Cloud Phase 1
1 parent 2b36ed6 commit 659b15d

File tree

12 files changed

+71
-46
lines changed

12 files changed

+71
-46
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The available tabs depend on your subscription type and may include:
2020

2121
- The **Account** tab displays basic information associated with your account, including general info, address details, time zone setting, security settings, and provider integration details.
2222

23-
- 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/" >}}).
23+
- The **Cloud Account** tab is displayed for Redis Cloud Pro subscriptions hosted on Amazon Web Services (AWS). To learn more, see [Bring your own Cloud]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/" >}}).
2424

2525
- 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/" >}}).
2626

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ You can reduce network transfer costs and network latency by ensuring your Redis
6262

6363
To specify the availability zone for your cluster, select *Manual Selection* under **Allowed Availability Zones**.
6464

65-
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.
65+
For Google Cloud clusters and [self-managed AWS cloud accounts]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/" >}}), select an availability zone from the **Zone name** list.
6666

6767
{{<image filename="images/rc/availability-zones-no-multi-az.png" width="95%" alt="Select one availability zone when Multi-AZ is turned off." >}}
6868

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,8 +131,8 @@ The following settings are defined in the **Advanced options** of the **Setup**
131131
|---|---|
132132
| **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" >}}). |
133133
| **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" >}}). |
134-
| **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) |
135-
| **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) |
134+
| **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/bring-your-own-cloud" >}}) are enabled) |
135+
| **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/bring-your-own-cloud" >}}) are enabled) |
136136
| **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). |
137137
| **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/" >}})|
138138
| **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/security/aws-transit-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Before you can set up Transit Gateway:
5353
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/).
5454

5555
{{< note >}}
56-
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.
56+
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/bring-your-own-cloud/iam-resources/aws-console.md" >}}) for more information.
5757
{{< /note >}}
5858

5959
## AWS Transit Gateway

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

Lines changed: 0 additions & 30 deletions
This file was deleted.
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
LinkTitle: Bring your own Cloud
3+
Title: Redis Cloud Bring your own Cloud
4+
alwaysopen: false
5+
categories:
6+
- docs
7+
- operate
8+
- rc
9+
description: Describes how to provision your Redis Cloud subscription to use an existing
10+
cloud provider account.
11+
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/).
12+
bannerChildren: true
13+
hideListLinks: true
14+
weight: 80
15+
aliases:
16+
- /operate/rc/how-to/view-edit-cloud-account
17+
- /operate/rc/cloud-accounts
18+
- /operate/rc/cloud-integrations/aws-cloud-accounts
19+
---
20+
21+
Redis Cloud Bring your own Cloud (BYOC) allows organizations to use their own cloud infrastructure to deploy Redis Cloud.
22+
23+
By default, Redis is responsible for the infrastructure that runs Redis Cloud. However, if your organization has specific requirements, you may want to have more control over your data residency or security options. Redis Cloud BYOC lets you fulfill these requirements while keeping the managed service experience of Redis Cloud. Like standard Redis Cloud, Redis handles deployment, scaling, monitoring, and support, so you can focus on building applications while Redis manages the backend.
24+
25+
If you're interested in Redis Cloud BYOC, [contact sales](https://redis.io/meeting/).
26+
27+
## Benefits of Redis Cloud BYOC
28+
29+
Redis Cloud BYOC has some benefits over standard Redis Cloud:
30+
31+
- **Full Data Control**: All data stays within your environment, giving you complete control over data security and reducing risks associated with data sovereignty.
32+
- **Simplified Compliance**: BYOC simplifies adherence to regulatory standards like GDPR, HIPAA, and compliance frameworks like SOC 2 and PCI DSS since data remains within the your own cloud account.
33+
- **Maximize Cloud Commitments**: Infrastructure costs are billed directly through your cloud provider account, enabling you to fully utilize existing commitments.
34+
- **Separation of Costs**: Customers pay Redis only for licensing and management, while infrastructure costs go directly to the cloud provider, offering clear visibility into each cost stream.
35+
- **Instant Access Control**: You can revoke Redis’ access to your environment at any time, offering complete control over data and infrastructure.
36+
37+
## Redis Cloud BYOC Use cases
38+
39+
Consider using Redis Cloud BYOC if you have specific organizational needs or requirements, such as:
40+
41+
- **Data Residency and Compliance**: Organizations operating in heavily regulated industries (such as finance, healthcare, and government) can use Redis Cloud BYOC to meet strict data residency and sovereignty requirements, ensuring sensitive data remains within their controlled environments.
42+
- **Cloud spend optimization**: Companies with significant cloud provider commitments can use Redis Cloud BYOC to optimize their cloud spend. Since infrastructure costs are billed directly through the cloud provider, customers can fully utilize existing cloud provider discounts, improving cost efficiency.
43+
- **Enhanced Security and Control**: Redis Cloud BYOC is ideal for organizations that require a higher degree of security and control over their data. By keeping data within your own cloud account and leveraging existing security policies, tools, and procedures on your cloud’s security infrastructure, you are able to minimize external access to your data, and adhere to more strict organizational security guidelines.
44+
45+
## Set up Redis Cloud BYOC
46+
47+
To set up Redis Cloud BYOC on Amazon Web Services (AWS):
48+
49+
1. [Create the Identity and Access Management (IAM) resources]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources" >}}) needed to let Redis create, monitor, and maintain deployment infrastructure.
50+
51+
1. [Set your AWS Account as a BYOC Cloud account]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings" >}}) on Redis Cloud.
52+
53+

content/operate/rc/subscriptions/aws-cloud-accounts/cloud-account-settings.md renamed to content/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,16 @@ hideListLinks: true
1010
weight: 2
1111
---
1212

13-
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.
13+
Redis Cloud Bring your own Cloud (BYOC) allows organizations to use their own cloud infrastructure to deploy Redis Cloud.
14+
15+
You can 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.
1416

1517
To do this, you need:
1618

1719
1. A programmatic user with an access key and a secret access key for that user.
1820
1. A console role that allows administrative access to the cloud account.
1921

20-
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" >}}).
22+
You need to create these resources before adding the cloud account to your subscription. To learn more, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources" >}}).
2123

2224
{{<note>}}
2325
Once an AWS account has been configured as a cloud account, you must _not_:
@@ -76,7 +78,7 @@ If the **Add account** button is inactive, verify that:
7678
- The resources exist in your AWS account
7779
- Each resource provides the required level of access
7880

79-
For help, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources" >}}).
81+
For help, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources" >}}).
8082

8183
## Edit cloud account details
8284

@@ -100,7 +102,7 @@ Use the **Update account** button to save your changes.
100102

101103
{{<image filename="images/rc/button-cloud-account-update.png" alt="Use the Update account button to save the updated cloud account details." width="140px">}}
102104

103-
## Delete cloud account details
105+
## Delete cloud account
104106

105107
To remove a cloud account from your Redis cloud subscription, select the cloud account from the **Cloud account** tab and then select the **Delete** button.
106108

@@ -110,4 +112,4 @@ To remove a cloud account from your Redis cloud subscription, select the cloud a
110112

111113
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.
112114

113-
To learn more, see [Create IAM resources for AWS cloud accounts]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources" >}}).
115+
To learn more, see [Create IAM resources for AWS cloud accounts]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources" >}}).

content/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/_index.md renamed to content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/_index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ hideListLinks: true
99
linkTitle: Create IAM resources
1010
weight: 1
1111
---
12-
For most Redis Cloud Pro databases deployed to Amazon Web Services (AWS), we manage the supporting infrastructure for you in dedicated AWS accounts.
12+
For Redis Cloud Bring your Own Cloud (BYOC) on Amazon Web Services (AWS), we manage the supporting infrastructure for you in dedicated AWS accounts.
1313

1414
You can manage this infrastructure with your own AWS accounts.
1515

@@ -22,7 +22,7 @@ In the new AWS account, you need to create:
2222
- A user with an **access key**
2323
- A role that grants **AWS console access**
2424

25-
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.
25+
Save the access key in a secure location so that you can enter it when you [register the cloud account]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings" >}}) with your Redis Cloud subscription.
2626

2727
{{< warning >}}
2828
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.
3737

3838
You can use one of the following tools to create IAM resources:
3939

40-
- [CloudFormation]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/cloudformation" >}})
41-
- [Terraform]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/terraform" >}})
42-
- The [AWS Console]({{< relref "/operate/rc/subscriptions/aws-cloud-accounts/iam-resources/aws-console" >}})
40+
- [CloudFormation]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/cloudformation" >}})
41+
- [Terraform]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/terraform" >}})
42+
- The [AWS Console]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/aws-console" >}})

0 commit comments

Comments
 (0)