Project: YugabyteDB (App Definition and Development / Database)
File: yugabytedb-managed-faq.md

title: YugabyteDB Managed FAQ linkTitle: YugabyteDB Managed FAQ description: YugabyteDB Managed frequently asked questions. aliases: /preview/yugabyte-cloud/cloud-faq/ menu: preview_faq: identifier: yugabytedb-managed-faq parent: faq weight: 30 type: docs unversioned: true rightNav: hideH3: true hideH4: true YugabyteDB Managed is a fully managed YugabyteDB-as-a-Service that allows you to run YugabyteDB clusters on Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). You access your YugabyteDB Managed clusters via and client APIs, and administer your clusters using . See also at yugabyte.com. YugabyteDB Managed runs on top of . Yugabyte bills for its services as follows: Charges by the minute for your YugabyteDB Managed clusters. Tabulates costs daily. Displays your current monthly costs under Invoices on the Usage & Billing tab. For information on YugabyteDB Managed pricing, refer to the . For a description of how cluster configurations are costed, refer to . Refer to for a list currently supported regions. YugabyteDB Managed supports all the regions that have robust infrastructure and sufficient demand from customers. If there are regions you would like added, reach out to {{% support-cloud %}}. Use the free Sandbox cluster to get started with YugabyteDB. The Sandbox cluster is limited to a single node and 10GB of storage. Although not suitable for production workloads or performance testing, the cluster includes enough resources to start exploring the core features available for developing applications with YugabyteDB. Sandbox clusters are provisioned with a . You can only have one Sandbox cluster. Sandbox clusters that are inactive for 10 days are ; after 15 days they are deleted. Dedicated clusters can have unlimited nodes and storage and are suitable for production workloads. They also support horizontal and vertical scaling - nodes and storage can be added or removed to suit your production loads. Dedicated clusters also support VPC networking, and scheduled and manual backups. By default, Dedicated clusters are provisioned using a . A YugabyteDB Managed account is limited to a single Sandbox cluster; you can add as many Dedicated clusters as you need. | Feature | Sandbox | Dedicated | | : | : | :-- | | Cluster | Single Node | Any | | vCPU/Storage | Up to 2 vCPU / 4 GB Memory / 10 GB storage | Any | | | All | All | | Upgrades | Automatic | Automatic with customizable | | | No | Yes | | | None (Single node, RF-1) | Multi node RF-3 clusters with region, availability zone, and node level | | | Up to 15 simultaneous connections | 15 per vCPU per node | | | None | Horizontal and Vertical | | | None | Scheduled and on-demand | | | Innovation<br>Preview | Production<br>Innovation | | Price | Free | <br> | | Support | Slack Community | Enterprise Support | If you want to continue testing YugabyteDB with more resource-intensive scenarios, you can: to try out bigger clusters with more resources. Download and run YugabyteDB on a local machine. For instructions, refer to

to upgrade to a fault-tolerant . Currently self-service migration is not supported. Contact {{% support-cloud %}} for help with migration. Upgrades are automatically handled by Yugabyte. There are two types of upgrades: During a , YugabyteDB Managed may be in read-only mode and not allow any edit changes. The upgrade has no impact on running clusters. Yugabyte will notify you in advance of the maintenance schedule. To keep up with the latest bug fixes, improvements, and security fixes, Yugabyte upgrades your cluster database to the . The database is upgraded to the latest release in the that was selected when the cluster was created (Innovation or Production for dedicated clusters, or Innovation or Preview for Sandbox clusters). Sandbox clusters are always in the preview track. Yugabyte only upgrades clusters during scheduled maintenance windows. Yugabyte notifies you in advance of any upcoming upgrade via email. Updates to fault-tolerant clusters are done on a rolling basis to avoid any downtime. For more information, refer to . Dedicated clusters are provisioned with a stable release, from a YugabyteDB series. When creating a dedicated cluster, you can choose one of the following tracks: Innovation, which has more frequent updates for faster access to new features. Production, which has a slower update cadence and features only select stable release builds. In addition to the Innovation track, Sandbox clusters can be provisioned with a preview release, from the YugabyteDB series. Once a cluster is created, it is upgraded with releases from the track that was assigned at creation (that is, either Innovation or Production for dedicated clusters, or Innovation or Preview for Sandbox clusters). To view the database version running on a particular cluster, navigate to the Clusters page; the database version is displayed next to the cluster name; hover over the version to see the release track. To test locally, download and install YugabyteDB on a local machine. Refer to . For accurate comparison with cloud, be sure to download the version that is running on YugabyteDB Managed. Enterprise Support is included in the base price for Dedicated clusters. Refer to the . Sandbox and Dedicated cluster customers can also use the . The YugabyteDB Managed Service Level Agreement (SLA), terms of service, acceptable use policy, and more can be found on the page. The page displays the current uptime status of YugabyteDB Managed, customer clusters, and the . The status page also provides notices of scheduled maintenance, current incidents and incident history, and historical uptime. Subscribe to the status page by clicking Subscribe to Updates. Email notifications are sent when incidents are created, updated, and resolved. Your data is processed at the YugabyteDB Managed account level, and each account is a single tenant, meaning it runs its components for only one customer. Clusters in your account are isolated from each other in a separate VPC, and access is limited to the IP addresses you specify in allow lists assigned to each cluster. Resources are not shared between

YugabyteDB Managed uses both encryption in transit and encryption at rest to protect clusters and cloud infrastructure. YugabyteDB Managed also provides DDoS and application layer protection, and automatically blocks network protocol and volumetric DDoS attacks. YugabyteDB Managed uses a shared responsibility model for security. For more information on YugabyteDB Managed security, refer to . Using YugabyteDB Managed, you can create single- and multi-region clusters that can be deployed across multiple and single availability zones. The Fault Tolerance of a cluster determines how resilient the cluster is to failures and, by extension, the cluster configuration. You can configure clusters with the following fault tolerances in YugabyteDB Managed: Region Level - a minimum of 3 nodes spread across 3 regions with a (RF) of 3. YugabyteDB can continue to do reads and writes even in case of an region failure. This configuration provides the maximum protection for a region failure. For horizontal scaling, nodes are scaled in increments of 3. Availability Zone Level - a minimum of 3 nodes spread across multiple availability zones with a RF of 3. YugabyteDB can continue to do reads and writes even in case of an availability zone failure. This configuration provides the protection for a data center failure. For horizontal scaling, nodes are scaled in increments of 3. Node Level - a 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 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. For production clusters, a minimum of Availability Zone Level is recommended. Whether you choose Region or Availability Zone Level depends on your application architecture, design, and latency requirements. For multi-region deployments, you can deploy a variety of topologies, including synchronously replicated, geo-level partitioned, and read replicas. For more information, refer to . Sandbox clusters are limited to a single node in a single region. You can connect to clusters in the following ways: {{< tabpane text=true >}} {{% tab header="Cloud Shell" lang="Cloud Shell" %}} Run the or shell from your browser to connect to and interact with your YugabyteDB database. Cloud Shell does not require a CA certificate or any special network access configured. When you connect using Cloud Shell with the YSQL API, the shell window also incorporates a , with a series of pre-built queries for you to run. {{% /tab %}} {{% tab header="Client Shell" lang="Client Shell" %}} Connect to your YugabyteDB cluster using the YugabyteDB and client shells installed on your computer. Before you can connect using a client shell, you need to add your computer to the cluster IP allow list. Refer to . You must be running the latest versions of the client shells (Yugabyte Client 2.6 or later), which you can download using the following command on Linux or macOS: ```sh $ curl -sSL

| bash ``` Windows client shells require Docker: ```sh docker run -it yugabytedb/yugabyte-client ysqlsh -h <hostname> -p <port> ``` {{% /tab %}} {{% tab header="psql" lang="psql" %}} Because YugabyteDB is PostgreSQL-compatible, you can use to connect to your clusters. The connection string to use is similar to what you would use for `ysqlsh`, as follows: ```sh psql --host=<HOST_ADDRESS> --port=5433 --username=<DB USER> \ --dbname=yugabyte \ --set=sslmode=verify-full \ --set=sslrootcert=<ROOTCERTPATH> ``` For detailed steps for configuring other popular third party tools, see . {{% /tab %}} {{% tab header="Applications" lang="Applications" %}} Applications connect to and interact with YugabyteDB using API client libraries (also known as client drivers). Before you can connect an application, you need to install the correct driver and configure it with the required connection parameters. You can also connect to YugabyteDB Managed clusters using smart drivers. For information on drivers supported by YugabyteDB, refer to . For sample applications using popular drivers, refer to . For information on obtaining the connection parameters for your cluster, refer to . Clusters have SSL () enabled so make sure your driver details include SSL parameters. Before you can connect, your application has to be able to reach your YugabyteDB Managed. To add inbound network access from your application environment to YugabyteDB Managed, add the public IP addresses to the , or use to add private IP addresses. {{% /tab %}} {{< /tabpane >}} For more details, refer to . Sandbox clusters are paused after 10 days of . For more details, refer to . Sandbox clusters are paused after 10 days of inactivity. To keep a cluster from being paused, perform an action as described in To keep a paused cluster from being deleted, sign in to YugabyteDB Managed, select the cluster on the Clusters page, and click Resume. Sandbox clusters are paused after 10 days of inactivity. To keep your cluster from being paused, you (or, where applicable, an application connected to the database) can perform any of the following actions: Any SELECT, UPDATE, INSERT, or DELETE database operation. Create or delete tables. Add or remove IP allow lists. If the cluster is already paused, resume the cluster by signing in to YugabyteDB Managed, selecting the cluster on the Clusters page, and clicking Resume. By default, every cluster is backed up automatically every 24 hours, and these automatic backups are retained for 8 days. The first automatic backup is triggered 24 hours after creating a table, and is scheduled every 24 hours thereafter. You can change the default backup intervals by adjusting the backup policy settings. YugabyteDB Managed runs full backups, not incremental. Backups are retained in the same region as the cluster. Backups for AWS clusters are encrypted using AWS S3 server-side encryption. Backups for GCP clusters are encrypted using Google-managed server-side encryption keys. Backups for Azure clusters are encrypted using Azure-managed server-side encryption keys and client-side encryption is done using . Currently, YugabyteDB Managed does not support backups of Sandbox clusters. Currently, YugabyteDB Managed does not support self-service backup downloads. Contact {{% support-cloud %}} for assistance.