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

title: Partition by region linkTitle: Partition by region description: Deploy geo-partitioned clusters in YugabyteDB Managed. headcontent: Use geo-partitioning to pin data to regions menu: preview_yugabyte-cloud: identifier: create-clusters-geopartition parent: create-clusters weight: 70 type: docs Use clusters to geo-locate data in specific regions. Clusters consist of a primary region and any number of additional secondary regions, where the partitioned, region-specific data resides. You can add or remove regions as required. When first deploying, you can deploy a single cluster in the primary region. {{< youtube id="9ESTXEa9QZY" title="Create a geo-partitioned cluster in YugabyteDB Managed" >}} You place data in regions of the cluster using tablespaces. Tables that don't belong to any tablespace are stored in the primary region. YugabyteDB Managed automatically creates tablespaces in the regions of your cluster named `regionnamets`. For example, if you add the us-central1 region, the tablespace is named `uscentral1ts`. To view your cluster tablespaces, you can enter the following command: ```sql SELECT * FROM pg_tablespace; ``` Note that data pinned to a single region via tablespaces is not replicated to other regions, and remains subject to the fault tolerance of the cluster (Node- or Availability Zone-level). For more information on specifying data placement for tables and indexes, refer to . Partition-by-region clusters include the following features: Multi node clusters with availability zone- or node-level fault tolerance. No limit on cluster size - choose any cluster size based on your use case. Size each region to its load - add extra horsepower in high-traffic regions, and provision lower-traffic regions with fewer nodes. 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. Partition-by-region clusters must be deployed in a VPC. 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 partition-by-region 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 Partition by region. Select a Fault Tolerance for the regions. determines how resilient each region is to node and zone outages (planned or unplanned). Choose one of the following: | Fault tolerance | Description | Scaling | | : | : | : | | Zone | Resilient to a single zone

Minimum of 3 nodes spread across 3 availability zones. This configuration provides the maximum protection for a data center outage. Recommended for production deployments. | Nodes are scaled in increments of 3 (each zone has the same number of nodes). | | Node | Resilient to 1, 2, or 3 node outages, with a minimum of 3, 5, or 7 nodes respectively, deployed in a single availability zone. Not resilient to zone outages. | Nodes are scaled in increments of 1. | | None | Minimum of 1 node, with no replication or resiliency. Recommended for development and testing only. | Nodes are scaled in increments of 1. | Fault tolerance is applied to all regions in the cluster, including those added after cluster creation. Regions - For each region, choose the following: where the nodes will be located. VPC in which to deploy the nodes. Only VPCs using the selected cloud provider and available in the selected region are listed. For multi-region GCP clusters, the same VPC is used for all regions. VPCs must be created before deploying the cluster. Refer to . number of nodes to deploy in the region. number of virtual CPUs per node. disk size per node. disk input output (I/O) operations per second (IOPS) per node (AWS only). To add additional regions to the cluster, click Add Region. Partiton-by-region clusters support both horizontal and vertical scaling; you can add regions and change the cluster configuration 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.