Was this page helpful?
ScyllaDB Cloud FAQ¶
Costs and Billing¶
How can I switch my cluster billing from on-demand to an annual reserved instance?¶
Open a support ticket with your request.
Subject: Change billing method
How can I review my costs and when do I receive an invoice?¶
Open a support ticket with your request.
Subject: Request for billing information
We will send you a detailed invoice at the end of the month.
Deployment Location¶
How can I change an existing cluster deployment location to work in my AWS account?¶
Open a support ticket with your request.
Subject: Change deployment location
The ScyllaDB Cloud team will make the requested change.
Scaling¶
How can I scale up my cluster to a larger instance type?¶
Open a support ticket with your request:
Subject: Scaling my cluster
Note that scaling up will require changing all your cluster nodes to the new type.
How can I scale down my cluster to a smaller instance type?¶
Open a support ticket with your request:
Subject: Scaling my cluster
Backups¶
How often does ScyllaDB Cloud backup my data? What is the backup retention time?¶
How to restore a cluster from backup?¶
Open a support ticket with your request.
Subject: Restore
Make sure you open the ticket with the needed urgency.
Other¶
How can I enable experimental features for ScyllaDB Cloud?¶
ScyllaDB Cloud does not support experimental features. The service deploys the latest ScyllaDB Enterprise version with experimental features disabled.
How can I enable DNS names for my cluster nodes?¶
If you create a new cluster, DNS names are already enabled, and no action is required from you. DNS names are automatically
generated by ScyllaDB and may resemble the following: node-0.aws_us_east_1.5493c518df7fdc22b724.clusters.scylla.cloud
.
For existing clusters, you may need to manually enable DNS names in your cluster’s view:
Go to the General tab.
Click the Enable button next to “DNS”.
Wait for the DNS feature to be enabled. The time to complete this process may vary, depending on your cluster size.
Using DNS names eliminates the need to update the IP in the connection strings when there’s a change in the cluster, for example, when a node is replaced. In such cases, the node’s DNS name remains unchanged, sparing you the time and effort to update your application and drivers.