Clouds Overview

Couchbase Cloud connects to your existing cloud provider to deploy and run Couchbase clusters.

Although Couchbase Cloud is a fully managed service, it leverages your existing public cloud provider for the purposes of deploying and running clusters. It does this by securely connecting the Couchbase Cloud management service (hosted by Couchbase) to your cloud account, and deploys an isolated virtual private cloud (VPC) within your cloud environment.

Connecting Clouds

In order to deploy clusters using Couchbase Cloud, you’ll need to create a connection to your existing cloud provider first. Connecting a cloud is a one-time procedure; so once you’ve connected a cloud, you can use it to deploy multiple clusters across multiple projects.

A cloud connection is provider, region, and even account-specific. When you connect a cloud, you’ll select a supported cloud provider, a supported region within that cloud provider, and then authenticate an existing cloud provider account. This allows a great deal of flexibility when planning your cloud strategy. For example, you can create clouds in:

  • Multiple regions of the same cloud provider

    • Connect one cloud in AWS eu-central-1 for development clusters, and another cloud in AWS us-west-1 for production clusters.

  • Multiple regions of the same cloud provider, using multiple provider accounts

    • Connect a cloud in AWS ap-southeast-1 using one AWS cloud account, and connect another cloud in AWS us-east-1 using a different AWS account.

  • Multiple regions of different cloud providers

    • Connect a cloud in AWS us-west-1 for production clusters, and connect a cloud in Azure East US for failover clusters.

Couchbase Cloud can automatically deploy multi-node clusters across availability zones, providing fault tolerance against outages that occur within a region. But when it comes achieving tolerance against whole-region or even whole-provider outages, planning out your connected clouds can be a key part of your availability strategy.