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

title: Create a single-region cluster linkTitle: Single region description: Deploy dedicated single-region clusters in YugabyteDB Managed. headcontent: Deploy availability zone- and node-level fault tolerant clusters aliases: /preview/deploy/yugabyte-cloud/create-clusters/ /preview/yugabyte-cloud/create-clusters/ menu: preview_yugabyte-cloud: identifier: create-single-region parent: create-clusters weight: 50 type: docs Single-region dedicated clusters support multi-node and highly available deployments and are suitable for production deployments. {{< youtube id="1eo7YXs3uTw" title="Deploy a fault tolerant cluster in YugabyteDB Managed" >}} Single-region dedicated clusters include the following features: Multi-node clusters with availability zone- and node-level fault tolerance. 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 support. Automated and on-demand backups. Available in all . Enterprise support. If you want to use dedicated VPCs for network isolation and security, create the VPC before you create your cluster. YugabyteDB Managed supports AWC and GCP for peering, and AWC and Azure for private linking. Single-region clusters on Azure must be deployed in a VPC. Refer to . A billing profile and a payment method. Refer to . To create a single-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 Single-Region Deployment and set the following options. determines how resilient the cluster is to node and zone outages (planned or unplanned). Choose one of the following: | Fault tolerance | Description | Scaling | | : | : | : | | Zone | Resilient to a single zone outage. 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. result in downtime (no rolling restart is possible). Recommended for development and testing only. | Nodes are scaled in increments of

| You can't change the Fault tolerance of a cluster after it's created. Region: Choose the where the cluster will be located. Nodes: Enter the number of nodes for the cluster. Node and Availability Zone Level clusters have a minimum of 3 nodes; Availability Zone Level clusters increment by 3. vCPU/Node: Enter the number of virtual CPUs per node. Disk size/Node: Enter the disk size per node in GB. Disk IOPS/Node (AWS only): Enter the disk input output (I/O) operations per second (IOPS) per node. The node throughput will be scaled according to this 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. Dedicated clusters support both horizontal and vertical scaling; you can 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 . To use a VPC for network isolation and security, choose Select a VPC to use a dedicated network isolated from others, then select the VPC. Only VPCs using the selected cloud provider are listed. The VPC must be created before deploying the cluster. 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.