Cassandra

A role used to control access to a cluster. A role can hold permissions of its own (see grants), inherit the permissions of other roles (see role memberships), and optionally be used by an application to connect. Roles that can connect get a generated password stored in Vault.

A managed database cluster that hosts your keyspaces, roles and grants. Clusters are provisioned for you and cannot be created, changed or deleted through this service.

A permission given to a role on a resource such as a keyspace or a table. A grant carries exactly one permission on one resource, so create one grant per permission you want to give.

A named person's access to a cluster. A human role holds read-only access to every keyspace of its tenant, and can be granted write access for a limited period through the elevate action. Its permissions are not configurable: they follow from the role being a human role. The password is generated and stored in Vault, and password_location tells you where to read it.

A keyspace: the top-level container that holds your tables inside a cluster. Deleting a keyspace permanently destroys every table and row it contains.

A role used to control access to a cluster. A role can hold permissions of its own (see grants), inherit the permissions of other roles (see role memberships), and optionally be used by an application to connect. Roles that can connect get a generated password stored in Vault.

Takes exclusive ownership of the permissions held directly by a role. Every permission the role holds directly and that is absent from grant_ids is removed. This does not give permissions: list here the permissions the role is allowed to keep, and create each of them as a grant. Deleting this releases the ownership, it does not remove any permission.

The inheritance of one role's permissions by another role. The role named by role_id receives every permission held by the role named by member_of_role_id. Create one role membership per inherited role.