docs/content/stable/faq/yugabytedb-managed-faq.md
YugabyteDB Aeon (previously known as 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 Aeon clusters via YSQL and YCQL client APIs, and administer your clusters using the YugabyteDB Aeon UI.
YugabyteDB Aeon runs on top of YugabyteDB Anywhere.
Yugabyte bills for its services as follows:
{{<lead link="https://www.yugabyte.com/pricing/">}} YugabyteDB Aeon Pricing {{</lead>}}
{{<lead link="/stable/yugabyte-cloud/cloud-admin/cloud-billing-costs/">}} For a description of how cluster configurations are costed, refer to Cluster costs. {{</lead>}}
YugabyteDB Aeon 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 %}}.
{{<lead link="../../yugabyte-cloud/cloud-basics/create-clusters-overview/#cloud-provider-regions">}} Refer to Cloud provider regions for a list currently supported regions. {{</lead>}}
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 preview release. You can only have one Sandbox cluster. Sandbox clusters that are inactive for 10 days are paused; 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 stable release.
A YugabyteDB Aeon 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 |
| Regions | All | All |
| Upgrades | Automatic | Automatic with customizable maintenance windows |
| VPC networking | No | Yes |
| Fault tolerance | None (Single node, RF-1) | Multi node RF-3 clusters with region, availability zone, and node level |
| Connections | Up to 15 simultaneous connections | 15 per vCPU per node |
| Scaling | None | Horizontal and Vertical |
| Backups | None | Scheduled and on-demand |
| YugabyteDB version | Innovation | |
| Preview | ||
| Early Access | Production | |
| Innovation | ||
| Early Access | ||
| Price | Free | Pay-as-you-go and subscription |
| Free trial available | ||
| Support | Slack Community | Enterprise Support |
If you want to continue testing YugabyteDB with more resource-intensive scenarios, you can:
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 maintenance window, YugabyteDB Aeon 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 latest version. The database is upgraded to the latest release in the release track that was selected when the cluster was created.
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.
{{<lead link="../../yugabyte-cloud/cloud-clusters/cloud-maintenance/">}} Manage cluster maintenance windows and set exclusion periods {{</lead>}}
Dedicated clusters are provisioned with a stable release, from a YugabyteDB stable release series. When creating a dedicated cluster, you can choose one of the following tracks:
In addition to the Innovation and Early Access tracks, Sandbox clusters can be provisioned with a preview release, from the YugabyteDB preview release series.
Once a cluster is created, it is upgraded with releases from the track that was assigned at creation.
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.
For security reasons, in YugabyteDB Aeon you can't use the yugabyte or postgres users that are available in open-source YugabyteDB, and the cluster database admin user does not have YSQL superuser privileges. Instead, the admin is a member of yb_superuser, a role specific to YugabyteDB Aeon clusters.
{{<lead link="../../yugabyte-cloud/cloud-secure-clusters/cloud-users/">}} Default YugabyteDB users and roles in YugabyteDB Aeon clusters {{</lead>}}
To test locally, download and install YugabyteDB on a local machine. Refer to Quick Start. For accurate comparison with cloud, be sure to download the version that is running on YugabyteDB Aeon.
Enterprise Support is included in the base price for Dedicated clusters. Refer to the YugabyteDB Aeon Support Services Terms and Conditions.
Sandbox and Dedicated cluster customers can also use the YugabyteDB Slack community.
The YugabyteDB Aeon Service Level Agreement (SLA), terms of service, acceptable use policy, and more can be found on the Yugabyte Legal page.
The YugabyteDB Aeon Status page displays the current uptime status of YugabyteDB Aeon, customer clusters, and the Yugabyte Support Portal.
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 Aeon 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 clusters.
YugabyteDB Aeon uses both encryption in transit and encryption at rest to protect clusters and cloud infrastructure. YugabyteDB Aeon also provides DDoS and application layer protection, and automatically blocks network protocol and volumetric DDoS attacks.
YugabyteDB Aeon uses a shared responsibility model for security.
{{<lead link="../../yugabyte-cloud/cloud-security/">}} Security architecture {{</lead>}}
Using YugabyteDB Aeon, 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 Aeon:
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.
{{<lead link="../../yugabyte-cloud/cloud-basics/create-clusters-topology/">}} Topologies {{</lead>}}
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 ysqlsh or ycqlsh 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 Quick Start Guide, 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 ysqlsh and ycqlsh 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 Assign IP Allow Lists.
{{% /tab %}}
{{% tab header="psql" lang="psql" %}}
Because YugabyteDB is PostgreSQL-compatible, you can use psql to connect to your clusters. The connection string to use is similar to what you would use for ysqlsh, as follows:
psql --host=<HOST_ADDRESS> --port=5433 --username=<DB USER> \
--dbname=yugabyte \
--set=sslmode=verify-full \
--set=sslrootcert=<ROOT_CERT_PATH>
For detailed steps for configuring other popular third party tools, see GUI clients.
{{% /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 Aeon clusters using smart drivers.
For information on drivers supported by YugabyteDB, refer to Drivers and ORMs. For sample applications using popular drivers, refer to Build an application.
For information on obtaining the connection parameters for your cluster, refer to Connect applications.
Clusters have SSL (encryption in-transit) enabled so make sure your driver details include SSL parameters.
Before you can connect, your application has to be able to reach your YugabyteDB Aeon. To add inbound network access from your application environment to YugabyteDB Aeon, add the public IP addresses to the cluster IP allow list, or use VPC networking to add private IP addresses.
{{% /tab %}}
{{< /tabpane >}}
{{<lead link="../../yugabyte-cloud/cloud-connect/">}} Connect to clusters {{</lead>}}
Sandbox clusters are paused after 10 days of inactivity.
{{<lead link="../../yugabyte-cloud/cloud-basics/create-clusters/create-clusters-free/#inactive-sandbox-clusters">}} Inactive Sandbox clusters {{</lead>}}
Sandbox clusters are paused after 10 days of inactivity. To keep a cluster from being paused, perform an action as described in What qualifies as activity on a cluster?
To keep a paused cluster from being deleted, sign in to YugabyteDB Aeon, 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 Aeon, 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 Aeon supports full backups, and incremental backups.
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 GCM mode with AES.
Currently, YugabyteDB Aeon does not support backups of Sandbox clusters.
Backups are located in cloud storage of the provider where the cluster is deployed. The storage is located is the same region as the cluster.
For Replicate across region clusters, the backup is stored in one of the cluster regions, as determined automatically by Aeon when the cluster is created.
For Partition by region clusters, the database schema and tablet details are stored in the primary region, and the regional tablespace data is stored in its respective region to preserve data residency.
Currently, YugabyteDB Aeon does not support self-service backup downloads. Contact {{% support-cloud %}} for assistance.