Was this page helpful?
ScyllaDB Cloud Security Best Practices¶
There are two separate systems of ScyllaDB Cloud users:
ScyllaDB Cloud User logs into cloud.scylladb.com. Depending on the assigned role, ScyllaDB Cloud User can manage clusters (create, delete, scale, etc.), access monitoring data, access billing information, and more (see User Roles for details). ScyllaDB Cloud Users act as ScyllaDB Database administrators.
ScyllaDB Database User logs in to a ScyllaDB cluster. ScyllaDB Database User can access the data in the DB.
The two systems are separated and isolated from each other. Once a ScyllaDB Cloud User creates a cluster, a default ScyllaDB Database User is created as a superuser. As the account administrator, you can request support to add more users.
This ScyllaDB Database superuser can create and manage other ScyllaDB Database roles and users using the CQL API.
Security Recommendations for ScyllaDB Cloud User¶
Use VPC Peering¶
Secure your data and make sure all traffic between ScyllaDB’s cluster and the application layer is done via a private network and never traverses the public internet. AWS encrypts all data transferred on VPC peering by default. More on VPC Peering.
Minimal IP Whitelist¶
When launching a cluster, you are asked to list the IP ranges (CIDR) which will connect to the cluster. Choose the minimal ranges as possible, and add ranges only when required.
Bring Your Own Account (BYOA)¶
When using BYOA for AWS, it is recommended to have a dedicated AWS sub-account for ScyllaDB Cloud by using AWS Organizations and following the procedure using this dedicated account. This will give you better control and visibility of ScyllaDB Cloud permissions and actions.
Encryption at Rest¶
In ScyllaDB Cloud, your data is encrypted on the storage level by your cloud provider. See Storage-level Encryption . In addition we have database-level encryption at rest. See Database-level Encryption for details.
Security Recommendations for ScyllaDB Database User¶
Role Based Access¶
Role-Based Access Control (RBAC), a method of reducing lists of authorized users to a few roles assigned to multiple users. RBAC is sometimes referred to as role-based security. It is recommended to:
Set roles per keyspace/table.
Use the principle of least privilege per keyspace/table. Start by granting no permissions to all roles, then grant read access only to roles who need it, write access to roles who need to write, etc. It’s better to have more roles, each with fewer permissions.
Password policy¶
It is recommended to rotate the ScyllaDB database user passwords or user/passwords periodically. One way to do it is to create a new user/password, switch to it, and only then remove or update the old user’s password. Note not to break the connectivity with your running apps in the process.