Shared responsibility model for BYOC
In any CockroachDB CockroachDB Cloud deployment, responsibility for a successful and healthy deployment is . In a BYOC deployment, all of the except the control plane lives in an account under your control, which means that you incur additional responsibilities under the shared model. The following table describes the split of responsibilities between you and Cockroach Labs in the shared responsibility model for BYOC:| Area | Cockroach Labs responsibility | Customer responsibility |
|---|---|---|
| Uptime | Ensure 99.999% cluster uptime | Ensure that clusters remain accessible to CRL via cross-account IAM as documented in the corresponding deployment guide |
| Deployments | Automate cluster provisioning and scaling, provide hardware best practices | Provision new cloud service accounts and grant IAM permissions for Cockroach Labs to create and manage clusters |
| Upgrades | Provide automatic minor/patch upgrades and major upgrade automation via Terraform, APIs, or the CockroachDB Cloud Console | Initiate , if applicable |
| Workload | Troubleshoot problems as they pertain to cluster availability | to manage workload requirements, tune performance, and adjust schema designs with support from Cockroach Labs |
| Backups | Initialize a default backup schedule and write to customer-owned Cloud storage, ensure backup jobs run successfully | Configure a backup schedule as needed to meet RPO/RTO requirements |
| Support | Reactively and proactively identify and resolve availability-impacting incidents | Ensure sufficient hardware is made available to prevent scaling issues, including negotiating cloud resource quotas and availability with your cloud service provider. Maintain appropriate IAM permissions at all times |
| Billing | Meter vCPUs consumed, at the per-minute level | Negotiate with cloud service provider, manage infrastructure spend and discounts |