For customers hosting it on your own cloud account, Couchbase Capella connects to your existing cloud provider to deploy and run Couchbase clusters.
This information is for anyone still using Couchbase Server 6.6, hosted in their own cloud provider’s VPC. It does not apply to Couchbase 7.0, hosted in Couchbase’s VPC and fully managed for you.
For further information contact Couchbase.
The easiest way to get started with Capella, our fully managed DBaaS, is hosting in Couchbase’s Cloud.
New Couchbase Capella instances are hosted in Couchbase’s own cloud account. Customers already running Capella hosted in a virtual private cloud (VPC) in their existing public cloud provider account can extend their Capella installation with more clusters hosted this way, and most of the information in this section is for this type of Capella instance.
Couchbase Capella is a fully managed service, but it can leverage your existing public cloud provider in order to deploy and run your clusters if you prefer. It does this by creating a persistent and secure connection between the Capella control plane (hosted by Couchbase) and your cloud provider. As part of this connection, the control plane deploys a virtual private cloud (VPC) within your cloud provider account, which establishes a data plane in your cloud provider account within which your clusters will be deployed.
In order to deploy clusters, Capella first needs to establish a connection to your existing cloud provider. Connecting a cloud is a one-time procedure — so once you’ve connected a cloud to your organization, you can use it to deploy multiple clusters across multiple projects.
A connected cloud is provider and region-specific. When you connect a cloud, you’ll select a supported cloud provider and a supported region within that cloud provider. You’ll then authenticate your cloud provider account and deploy a pre-configured resource template that Capella uses to automatically establish the cloud connection.
A connected cloud represents a single region in a single cloud provider.
Multiple connected clouds can be created in the same region.
Multiple connected clouds can be created in multiple regions, even across multiple supported cloud providers. For example:
Connect one cloud in AWS
eu-central-1for development clusters, and another cloud in AWS
us-west-1for production clusters.
Connect a cloud in AWS
ap-southeast-1using one AWS cloud account, and connect another cloud in AWS
us-east-1using a different AWS account.
Multiple clusters can be deployed on a single connected cloud.
A cluster can only be deployed on a single connected cloud, and cannot be deployed across multiple connected clouds.
Capella automatically deploys clusters across availability zones, providing fault tolerance against zonal outages that occur within the region of the connected cloud. For protection against whole-region or even whole-provider outages, you can connect clouds in different regions and different providers, and then replicate data between clusters in those connected clouds in order to achieve your availability strategy.
For information on how to create, manage, and delete cloud connections, refer to Manage Clouds.