Project: YugabyteDB (App Definition and Development / Database)
File: create-clusters-multisync.md

title: Replicate across regions linkTitle: Replicate across regions description: Deploy multi-region synchronous clusters in YugabyteDB Managed. headcontent: Deploy region-level fault tolerant clusters menu: preview_yugabyte-cloud: identifier: create-clusters-multisync parent: create-clusters weight: 60 type: docs Clusters include a minimum of 3 nodes across 3 regions, providing region-level . You can add or remove nodes in increments of 1 per region (each region has the same number of nodes). {{< youtube id="fCjTB8IuTuA" title="Create a multi-region cluster in YugabyteDB Managed" >}} You can optionally designate one region in the cluster as preferred. The preferred region handles all read and write requests from clients. Designating one region as preferred can reduce the number of network hops needed to process requests. For lower latencies and best performance, set the region closest to your application as preferred. If your application uses a smart driver, set the to target the preferred region. When no region is preferred, YugabyteDB Managed distributes requests equally across regions. You can set or change the preferred region after cluster creation. Regardless of the preferred region setting, data is replicated across all the regions in the cluster to ensure region-level fault tolerance. You can enable to serve reads from non-preferred regions. In cases where the cluster has read replicas and a client connects to a read replica, reads are served from the replica; writes continue to be handled by the preferred region. Multi-region replicated clusters include the following features: Replicated synchronously across 3 to 7 regions. No limit on cluster size - choose any cluster size based on your use case. Horizontal and vertical scaling - add or remove nodes and vCPUs, and add storage to suit your production loads. VPC networking required. Automated and on-demand backups. Available in all . Enterprise support. Multi-region clusters must be deployed in VPCs. Create a VPC for each region where you want to deploy the nodes in the cluster. Refer to . By default, clusters deployed in VPCs do not expose any publicly-accessible IP addresses. Unless you enable , you can only connect from resources inside the VPC network. Refer to . A billing profile and payment method. Refer to . To create a multi-region replicated cluster, on the Clusters page, click Add Cluster, and choose Dedicated to start the Create Cluster wizard. The Create Cluster wizard has the following pages: {{% includeMarkdown "include-general-settings.md" %}} Select Multi-Region Deployment and set the following options. Set Data Distribution to Replicate across regions. Select the for the cluster, as follows: Resilient to 1 region outage; requires a minimum of 3 nodes across 3 regions. Resilient to 2 region outages; requires a minimum of 5 nodes across 5 regions. Resilient to 3 region outages; requires a minimum of 7 nodes across 7

Clusters can be scaled in increments of 1 node per region; for example, a cluster with fault tolerance of 2 regions can be scaled in multiples of 5 nodes, one per region. Regions: For each region, choose the following: the where the nodes will be located. the VPC in which to deploy the nodes. Only VPCs using the selected cloud provider and available in the selected region are listed. For AWS clusters, choose a separate VPC for each region. For GCP clusters, the same VPC is used for all regions. VPCs must be created before deploying the cluster. Refer to . The number of nodes to deploy in the regions. Each region has the same number of nodes. Preferred region: Optionally, assign one region as to handle all reads and writes. Node size: Enter the number of virtual CPUs per node, disk size per node (in GB), and disk input output (I/O) operations per second (IOPS) per node (AWS only). You must choose the regions before you can set the node size. The node throughput will be scaled according to the IOPS value. For large datasets or clusters with high concurrent transactions, higher IOPS is recommended. As disk IOPS is capped by vCPU, your vCPU and IOPS should be scaled together. Reference your current read and write IOPS performance for an estimation. Clusters replicated across regions support both horizontal and vertical scaling; you can change the cluster configuration and preferred region after the cluster is created. Refer to . Monthly total costs for the cluster are based on the number of vCPUs and estimated automatically. + Usage refers to any potential overages from exceeding the free allowances for disk storage, backup storage, and data transfer. For information on how clusters are costed, refer to . {{% includeMarkdown "network-access.md" %}} {{% includeMarkdown "include-security-settings.md" %}} The database admin credentials are required to connect to the YugabyteDB database that is installed on the cluster. You can use the default credentials generated by YugabyteDB Managed, or add your own. For security reasons, the database admin user does not have YSQL superuser privileges, but does have sufficient privileges for most tasks. For more information on database roles and privileges in YugabyteDB Managed, refer to . After the cluster is provisioned, you can . Download the credentials, and click Create Cluster. {{< warning title="Important" >}} Save your database credentials. If you lose them, you won't be able to use the database. {{< /warning >}} After you complete the wizard, the Clusters page appears, showing the provisioning of your new cluster in progress. When the cluster is ready, the cluster tab is displayed. You now have a fully configured YugabyteDB cluster provisioned in YugabyteDB Managed with the database admin credentials you specified.