Ways to Use CockroachDB
CockroachDB Cloud
CockroachDB Cloud provides fast and easy access (including a free tier) to CockroachDB as a web service, hosted by Cockroach Labs. Clusters run in multi-tenant Google Cloud Platform (GCP) or Amazon Web Services (AWS) environments with shared compute and networking resources. CockroachDB Advanced offers a single-tenant cluster running in its own Virtual Private Cloud (VPC). Compute and networking resources are isolated. CockroachDB Advanced provides additional security-enhancing features such as single sign-on (SSO) and SQL audit logging. Sign up for a CockroachDB Cloud account!CockroachDB Dedicated clusters comply with the Payment Card Industry Data Security Standard (PCI DSS). Compliance is certified by a PCI Qualified Security Assessor (QSA).To achieve compliance with PCI DSS on a CockroachDB Dedicated cluster, you must enable all required features in your CockroachDB Cloud organization and your cluster, and you must take additional steps to ensure that your organization’s applications and procedures comply with PCI DSS. For details, refer to PCI DSS Compliance in CockroachDB Dedicated advanced.To learn more about achieving PCI DSS compliance with CockroachDB Dedicated, contact your Cockroach Labs account team.
Learn more:
Self-Hosted
CockroachDB self-hosted here refers to the situation of a user deploying and operating their own cluster. Enterprise refers to an ongoing license relationship with Cockroach Labs. In this situation the customer maintains full control over their data, compute, and network resources while benefiting from the expertise of Cockroach Labs’ Enterprise Support staff. For more information, see theComparison of security features
| Security Domain | Basic | Standard | Advanced | self-hosted Enterprise | Feature |
|---|---|---|---|---|---|
| ✓ | ✓ | ✓ | ✓ | Inter-node and node identity authentication using TLS 1.3 | |
| ✓ | ✓ | ✓ | ✓ | Client identity authentication using username/password | |
| ✓ | ✓ | ✓ | ✓ | ||
| ✓ | SQL client identity authentication using TLS 1.2/1.3 | ||||
| ✓ | ✓ | ✓ | ✓ | Web console authentication with third-party using OpenID Connect OIDC | |
| ✓ | Client identity authentication with | ||||
| ✓ | HTTP API access using login tokens | ||||
| ✓ | OCSP certificate revocation protocol | ||||
| ✓ | ✓ | ✓ | ✓ | Encryption in transit using TLS 1.3 | |
| ✓ | ✓ | ✓ | ✓ | Backups for AWS clusters are encrypted at rest using AWS S3’s server-side encryption | |
| ✓ | ✓ | ✓ | ✓ | Backups for GCP clusters are encrypted at rest using Google-managed server-side encryption keys | |
| ✓ | ✓ | ✓ | ✓ | Industry-standard encryption at rest is provided at the infrastructure level by your chosen deployment environment, such as Google Cloud Platform (GCP), Amazon Web Services (AWS), or Microsoft Azure. You can learn more about GCP persistent disk encryption, AWS Elastic Block Storage, or Azure managed disk encryption. | |
| ✓ | Cockroach Labs’s proprietary storage-level implementing the Advanced Encryption Standard (AES) | ||||
| ✓ | ✓ | ✓ | ✓ | Users and privileges | |
| ✓ | ✓ | ✓ | ✓ | Role-based access control (RBAC) | |
| Network Security | ✓ | ✓ | ✓ | ✓ | SQL-level configuration allowed authentication attempts by IP address |
| ✓ | ✓ | ✓ | ✓ | Network-level Configuration of allowed IP addresses | |
| ✓ | ✓ | ✓ | or for GCP clusters and for AWS clusters | ||
| Non-Repudiation | ✓ | ✓ | ✓ | ✓ | |
| ✓ | ✓ | ✓ | ✓ | CockroachDB, as a distributed SQL database, is uniquely resilient by nature. A cluster can tolerate node failures as long as the majority of nodes remain functional. See |