Create a single-region cluster
Single-region dedicated clusters support multi-node and highly available deployments and are suitable for production deployments.
Single-region dedicated clusters include the following features:
- Multi node clusters with replication factor (RF) of 3, and 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 regions.
- 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. Refer to VPC network.
- Create a billing profile and add a payment method before you can create a Dedicated cluster. Refer to Manage your billing profile and payment method.
Create a single-region cluster
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:
Set the following options:
- Cluster Name: Enter a name for the cluster.
- Provider: Choose a cloud provider - AWS or GCP.
- Database Version: By default, dedicated clusters are deployed using a stable release. Before deploying a production cluster using a preview release, contact Support. If you have arranged a custom build with Yugabyte, it is also be listed here.
Select Single-Region Deployment and set the following options.
Select a fault tolerance for your cluster
Fault tolerance determines how resilient the cluster is to node and cloud zone failures. Choose one of the following:
- Availability Zone Level: Minimum of 3 nodes spread across multiple availability zones with a replication factor (RF) of 3. YugabyteDB can continue to do reads and writes even in case of a cloud availability zone failure. This configuration provides the maximum protection for a data center failure. Recommended for production deployments. For horizontal scaling, nodes are scaled in increments of 3.
- Node Level: Minimum of 3 nodes deployed in a single availability zone with a RF of 3. YugabyteDB can continue to do reads and writes even in case of a node failure, but this configuration is not resilient to cloud availability zone outages. For horizontal scaling, you can scale nodes in increments of 1.
- None: Single node, with no replication or resiliency. Recommended for development and testing only.
You can't change the Fault tolerance of a cluster after it's created.
Choose a region and size your cluster
Region: Choose the region 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.
Dedicated clusters support both horizontal and vertical scaling; you can change the cluster configuration after the cluster is created using the Edit Configuration settings. Refer to Scale and configure clusters.
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 Cluster costs.
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 VPC networking.
YugabyteDB Managed only allows access to clusters from trusted IP addresses. For applications in peered VPCs to be able to connect, you need to add the CIDR of the peered VPC to the cluster IP allow list. You can also assign IP allow lists to your cluster any time after the cluster is created.
You can add IP addresses using any combination of the following options.
|Add Current IP Address||Creates an allow list using the public IP address of your computer and adds it to the cluster IP allow list.|
|Add Peered VPC Networks||Only available for clusters being deployed in a VPC. VPCs must be peered, and the peering connection active for the peered networks to be added to the IP allow list.
Choose Add All Peered Networks to create an IP allow list from every network peered with the cluster VPC, and add it to the cluster.
Choose Add Individual Peered Networks to select specific peered networks to add to the cluster IP allow list.
|Add Existing IP Allow List||Choose from a list of IP allow lists already created for your account.|
|Create New IP Allow List||Create a new IP allow list and manually enter the CIDR and public IP addresses.|
Enable Public Access for this Cluster - To connect to a cluster deployed in a VPC from a public IP address (including your current address), you must enable Public Access for the cluster. When enabled, a public IP address is added to each region of the cluster. You can view the private and public host addresses under Connection Parameters on the cluster Settings tab.
In addition to the volume encryption that YugabyteDB Managed uses to encrypt your data, you can enable YugabyteDB encryption at rest (EAR) for clusters. When enabled, your YugabyteDB cluster (including backups) is encrypted using a customer managed key (CMK) residing in a cloud provider Key Management Service (KMS). (Currently, only AWS KMS is supported.)
You must be signed in as an Admin user to enable EAR.
To use a CMK to encrypt your cluster, make sure you have configured the CMK in AWS KMS, and created an access key for an IAM identity that has been granted permission to encrypt and decrypt using the CMK. For more information on AWS KMS, refer to AWS Key Management Service in the AWS documentation.
Set the following options:
- Customer managed key (CMK): Enter the Amazon Resource Name (ARN) of the CMK to use to encrypt the cluster.
- Access key: Provide an access key of an IAM identity with permissions for the CMK. An access key consists of an access key ID and the secret access key.
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 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 Database authorization in YugabyteDB Managed clusters.
After the cluster is provisioned, you can add more users and change your password.
Download the credentials, and click Create Cluster.
ImportantSave your database credentials. If you lose them, you won't be able to use the database.
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 Overview tab is displayed.
You now have a fully configured YugabyteDB cluster provisioned in YugabyteDB Managed with the database admin credentials you specified.