|
| 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 covers Redis Cloud Bring your Own Cloud (BYOC) deployments. To learn more or get started with 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 hosts the infrastructure that runs Redis Cloud. However, if your organization has specific requirements, you may need to have more control over your data residency or security options. Redis Cloud BYOC lets you fulfill these requirements while still having a fully managed service experience of Redis Cloud. Like standard Redis Cloud, Redis manages deployment, scaling, monitoring, and support, so you can focus on building applications while Redis manages the backend. |
| 24 | + |
| 25 | +Redis Cloud BYOC availability requires approval from Redis. If you're interested, [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 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, you can use existing security policies, tools, and procedures in your cloud’s security infrastructure. In this way, you can 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 | +## Avoid Redis Cloud BYOC service disruption {#avoid-service-disruption} |
| 54 | + |
| 55 | +{{< warning >}} |
| 56 | +Failing to follow the instructions in this section will cause your databases to become inaccessible, and Redis will not be able to ensure cluster and database stability. Please read them carefully. |
| 57 | +{{< /warning >}} |
| 58 | + |
| 59 | +To keep your Redis Cloud BYOC service and all databases running without issues: |
| 60 | +- Do not stop, delete, or modify Redis-managed resources through the cloud provider - including VPCs, subnets, virtual machines, and other infrastructure. |
| 61 | +- Do not change roles or access policies. |
| 62 | + |
| 63 | +If you make any infrastructure changes, whether or not they are listed above, it may violate our SLA commitments. See [Appendix 1 in our Terms of Service](https://redis.io/legal/cloud-tos/#Appendix-1) for more details. |
| 64 | + |
0 commit comments