CockroachDB Cloud FAQs

This page answers the frequently asked questions about CockroachDB Serverless (beta) and CockroachDB Dedicated.

Cluster basics

Why are certain regions in AWS and GCP not available?

We run CockroachDB Cloud in EKS and GKE - the managed Kubernetes offerings for AWS and GCP respectively - and support all regions that the offerings are available in. If a particular region is not available on the CockroachDB Cloud Console, that is due to the cloud provider not supporting the managed Kubernetes offering in that region. See list of EKS regions and list of GKE regions for details.

Known issue: In addition to the non-GKE regions, we had to temporarily disable the following GCP regions due to GCP's quota restrictions:

  • Mumbai (asia-south1)
  • Osaka (asia-northeast2)
  • Hamina (europe-north1)
  • Frankfurt (europe-west3)
  • Zurich (europe-west6)

If you want to create a cluster in a disabled region, please contact Support.

How do CockroachDB Dedicated free trials work?

CockroachDB Dedicated offers a 30-day free trial. Free trials require a credit card so we can validate that you are not a bot and provide a seamless transition into production. Free trials apply when you:

  • Create the first cluster in your organization
  • Select 4 or fewer nodes (we recommend starting with 3 so you can try scaling)
  • Don't remove the pre-applied trial code at check out

Once the 30-day period is over, your trial cluster can be scaled beyond 4 nodes. You can create other paid clusters at any time. If Cockroach Labs has provided you with additional codes, you can use those on applicable clusters. For extended trial options, contact us.

How do I connect to my cluster?

To connect to a cluster, you need to authorize your network, create a SQL user, download the CA certificate, and then generate a connection string or parameters. You can use this information to connect to your cluster through the CockroachDB SQL client or a Postgres-compatible driver or ORM. For more details, see Connect to Your CockroachDB Dedicated Cluster.


Is my cluster secure?

Yes. We create individual sub-accounts and VPCs for each cluster within the cloud provider. These VPCs are firewalled from each other and any other outside connection, unless allowlisted for SQL and Web UI ports.

The allowlist is comprised of IP addresses that you provide to us, and is an additional layer of protection for your cluster. Connections will only be accepted if they come from an allowlisted IP address, which protects against both compromised passwords and any potential bugs in the server.

We use separate certificate authorities for each cluster, and all connections to the cluster over the internet use TLS 1.2.

Is encryption-at-rest enabled on CockroachDB Dedicated?

Yes. All data on CockroachDB Dedicated is encrypted-at-rest using the tools provided by the cloud provider that your cluster is running in.

Because we are relying on the cloud provider's encryption implementation, we do not enable CockroachDB's internal implementation of encryption-at-rest. This means that encryption will appear to be disabled in the DB Console, since it is unaware of cloud provider encryption. For more information, see the Security Overview.

Is my cluster isolated? Does it share resources with any other clusters?

CockroachDB Dedicated is a single-tenant offering and resources are not shared between clusters.

Who has access to my cluster data?

The Cockroach Labs SRE team has direct access to CockroachDB Cloud cluster data. They adhere to the confidentiality agreement described in our Terms and Conditions.

Cluster maintenance

How do I change the configurations on my cluster?

Contact Support to change your cluster configuration.

How do I add nodes?

You can add nodes by accessing the Clusters page on the CockroachDB Cloud Console and clicking the ... button for the cluster you want to add or delete nodes for. See Cluster Mangement for more details.


At this time, you cannot add nodes to a single-node cluster once it is created.

Do you auto-scale?

Today, we do not automatically scale nodes based on your capacity usage. To add or remove nodes, see Cluster Mangement. There are plans to allow auto-scaling in the future.

Who is responsible for backup?

Cockroach Labs runs full backups daily and incremental backups hourly for every CockroachDB Cloud cluster. The full backups are retained for 30 days and incremental backups for 7 days. Only CockroachDB Dedicated cluster backups are available to users at this time.

The backups for AWS clusters are encrypted using AWS S3’s server-side encryption and the backups for GCP clusters are encrypted using Google-managed server-side encryption keys.


All databases are not backed up at the same time. Each database is backed up every hour based on the time of creation. For larger databases, you might see an hourly CPU spike while the database is being backed up.

You can also backup and restore data on your own. If you need additional help, contact us.

Can I download the backups that CockroachDB Cloud takes for me?

CockroachDB Cloud automated backups cannot be downloaded, but you can manually run a backup to your own storage location at any time. To do this, you will need either admin or SELECT privileges on the data you are backing up.

Can I restore my self-hosted CockroachDB cluster to CockroachDB Dedicated?

Yes. You can backup your self-hosted CockroachDB databases to an external location and then restore to your CockroachDB Cloud cluster.


If you are backing up the data to AWS or GCP, use the specified option for the AUTH parameter.

AWS clusters can set up a PrivateLink connection at any time after the cluster is created.

GCP clusters can also set up VPC peering after the cluster is created, but you will be locked into our default IP range ( unless you configure a different IP range during cluster creation. You can use the default IP range for VPC peering as long as it doesn't overlap with the IP ranges in your network. For more information, see VPC peering.

Product features

Are enterprise features available to me?

Yes, CockroachDB Dedicated clusters run the enterprise version of CockroachDB and all enterprise features are available to you.

Is there a public API for CockroachDB Cloud?

Our team is currently working on creating a public API for CockroachDB Cloud. The initial work is focused on core automation requirements, such as creation, modification, and deletion of clusters. We’re always looking for design partners and customer input for our features, so please contact us if you have specific API requirements.

Do you have a UI? How can I see details?

All customers of our CockroachDB Dedicated service can view and manage their clusters in the Console.

What latency should I expect when making a call to CockroachDB Dedicated?

Response times are under 10ms for public access but typically much lower. Additionally, using VPC peering or AWS PrivateLink will reduce latency.


Where can I find the Support Policy and Service Level Agreement (SLA) for CockroachDB Dedicated?

The following pages can be found in our Terms & Conditions:

Am I in control of upgrades for my CockroachDB Dedicated clusters?

Yes, you can apply major release upgrades directly through the CockroachDB Cloud Console; however, minor release upgrades are automatically applied to all clusters. CockroachDB Dedicated clusters are restarted for minor version updates, so previously established connections will need to be reestablished after the restart. For more information, see the Upgrade Policy.

What is the support policy for older versions of the software?

CockroachDB Dedicated supports the latest major version of CockroachDB and the version immediately preceding it. We highly recommend running one of the two latest versions of CockroachDB, but we will never force a major upgrade to a cluster without your knowledge. You can contact Support if you require an exception.

How do I check to see if CockroachDB Cloud is down?

The CockroachDB Cloud Status page is a publicly available page that displays the current uptime status of the following services:

  • CockroachDB Cloud Console: The UI used for signing up for CockroachDB Cloud, cluster creation and management, and user management.
  • AWS: The status reported here reflects the health of existing AWS CockroachDB Cloud clusters and the ability to provision new clusters in AWS.
  • GCP: The status reported here reflects the health of existing GCP CockroachDB Cloud clusters and the ability to provision new clusters in GCP.

Cluster troubleshooting

What do I do if my queries are too slow?

To optimize schema design to achieve your performance goals, we recommend working with our Sales Engineering team before you set up your cluster. You can also read our SQL Performance Best Practices and Query Performance Optimization docs for more information.

If you need additional help, contact Support.

YesYes NoNo