Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc][ybm] Add reasoning behind no access to yugabyte user #21105 #23930

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions docs/content/preview/faq/yugabytedb-managed-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ rightNav:
##### YugabyteDB

- [What version of YugabyteDB does my cluster run on?](#what-version-of-yugabytedb-does-my-cluster-run-on)
- [Why does the database admin user not have superuser privileges?](#why-does-the-database-admin-user-not-have-superuser-privileges)
- [Can I test YugabyteDB locally?](#can-i-test-yugabytedb-locally)

##### Support
Expand All @@ -57,6 +58,7 @@ rightNav:
##### Backups

- [How are clusters backed up?](#how-are-clusters-backed-up)
- [Where are clusters backed up?](#where-are-clusters-backed-up)
- [Can I download backups?](#can-i-download-backups)

## YugabyteDB Aeon
Expand Down Expand Up @@ -156,6 +158,10 @@ Once a cluster is created, it is upgraded with releases from the track that was

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.

### Why does the database admin user not have superuser privileges?

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. For information on database roles and privileges in YugabyteDB Aeon clusters, refer to [Database authorization](../../yugabyte-cloud/cloud-secure-clusters/cloud-users/).

### Can I test YugabyteDB locally?

To test locally, download and install YugabyteDB on a local machine. Refer to [Quick Start](../../quick-start/). For accurate comparison with cloud, be sure to download the version that is running on YugabyteDB Aeon.
Expand Down Expand Up @@ -294,14 +300,20 @@ Sandbox clusters are paused after 10 days of inactivity. To keep your cluster fr

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 runs full backups, not incremental.

Backups are retained in the same region as the cluster.
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](https://learn.microsoft.com/en-us/azure/storage/common/storage-service-encryption#client-side-encryption-for-blobs-and-queues).

Currently, YugabyteDB Aeon does not support backups of Sandbox clusters.

### Where are clusters backed up?

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](/preview/yugabyte-cloud/cloud-basics/create-clusters/create-clusters-multisync/) 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](/preview/yugabyte-cloud/cloud-basics/create-clusters/create-clusters-geopartition/) 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.

### Can I download backups?

Currently, YugabyteDB Aeon does not support self-service backup downloads. Contact {{% support-cloud %}} for assistance.
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ To review previous backups, click **Backup**. To review previous restores, click

## Location of backups

Backups are located in cloud storage of the provider where the cluster is deployed. The storage is located is the same region os the cluster. For example, for a cluster deployed in AWS and located in us-east-2, backups are stored in an S3 bucket in us-east-2.
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 example, for a cluster deployed in AWS and located in us-east-2, backups are stored in an S3 bucket in us-east-2.

For [Replicate across region](../../cloud-basics/create-clusters-topology/#replicate-across-regions) clusters, the backup is stored in one of the cluster regions, as determined automatically by Aeon when the cluster is created.

Expand Down