Amazon Web Services (AWS)
- reference
Couchbase Capella supports deploying databases onto Amazon Web Services (AWS).
Couchbase Capella provides fully managed Couchbase Server databases that can be deployed onto AWS. This page describes the various regions and configurations that are available to you when using Capella with AWS.
Supported Regions
Couchbase Capella’s fully managed DBaaS supports the following AWS regions.
-
Americas
-
Europe / Middle East
-
Asia Pacific
| AWS Region | Location |
|---|---|
|
US East (N. Virginia) |
|
US East (Ohio) |
|
US West (Oregon) |
|
Canada (Central) |
|
Brazil (São Paulo) |
| AWS Region | Location |
|---|---|
|
EU (Frankfurt) |
|
EU (Ireland) |
|
EU (London) |
|
EU (Paris) |
|
EU (Stockholm) |
| AWS Region | Location |
|---|---|
|
Asia Pacific (Singapore) |
|
Asia Pacific (Sydney) |
|
Asia Pacific (Tokyo) |
|
Asia Pacific (Seoul) |
|
Asia Pacific (Mumbai) |
Availability Zones
Every AWS region includes a number of independent availability zones. These consist of one or more discrete data centers that are isolated from failures in other availability zones. Capella can automatically distribute database nodes across multiple availability zones in a region for the highest availability. Every database in Capella is deployed with a minimum of three nodes.
The Multiple Availability Zones option is the default when creating databases using the Developer Pro or Enterprise Service Plans.
| The option to deploy across multiple AWS availability zones is only available for databases that use the Developer Pro or Enterprise Service Plans. Clusters using the Basic service plan deploy all nodes to the same availability zone. |
Configuration Options
Databases deployed onto AWS can be customized to suit your needs.
Nodes
Clusters have a minimum of 3 nodes and a maximum of 27.
Clusters consist of service groups that include the Couchbase services deployed and system resources. Each service group has a node quantity to represent the number of nodes in the database with that configuration. Individual service groups can have between 2 and 27 nodes but cannot collectively exceed 27. The service group that includes the Data Service requires at least 3 nodes.
| As they’re intended for evaluation purposes only, self-service trial databases only include 1 node. |
Compute and Memory
Capella provides the following compute configurations for databases deployed onto AWS.
| vCPU | Memory |
|---|---|
8 GB |
|
4 vCPUs |
16 GB |
4 vCPUs |
32 GB |
8 vCPUs |
16 GB |
8 vCPUs |
32 GB |
8 vCPUs |
64 GB |
16 vCPUs |
32 GB |
16 vCPUs |
64 GB |
16 vCPUs |
128 GB |
32 vCPUs |
128 GB |
32 vCPUs |
256 GB |
36 vCPUs |
72 GB |
48 vCPUs |
96 GB |
48 vCPUs |
192 GB |
48 vCPUs |
384 GB |
64 vCPUs |
256 GB |
64 vCPUs |
512 GB |
72 vCPUs |
144 GB |
96 vCPUs |
192 GB |
96 vCPUs |
384 GB |
96 vCPUs |
768 GB |
This configuration is only available for self-service trial databases in Capella.
Storage Size
Capella databases deployed onto AWS use the SSDs in AWS EBS. You have the option to choose between the GP3 and IO2 volume types per service group.
The amount of storage available per node in your database is configurable from a minimum of 50 GB to a maximum of 16 TB.
Storage Speed
Each service group has an input/output operations per second (IOPS) rate. This storage speed is configurable based on the volume type used:
-
gp3: 3000 to 16000 IOPS
-
io2: 1000 to 64000 IOPS
|
Adjusting the IOPS rate affects performance and cost. When creating or modifying a database with gp3 or io2 volume types and choosing a storage option, Capella uses recommended defaults for the IOPS field. You can replace the default IOPS value with one higher than the default but not lower. For the recommended IOPS values for databases using AWS gp3 or io2 volume types with typical enterprise workloads, see IOPS Defaults. |