With RBAC, you can limit access to certain commands and assign roles to authorized users. You have four system-defined roles to get started, and can create additional, more granular roles with privileges to run commands that used to require the superuser privilege. This granting of privileges is performed at a role level, without the need to grant permissions for the individual user or user groups.

In Amazon Redshift, RBAC applies the same principle to users based on their specific work-related role requirements, regardless of the type of database objects involved. Overview of RBAC in Amazon RedshiftĪs a security best practice, it’s recommended to design security by applying the principle of least privileges. We also cover new system views and functions introduced alongside RBAC. In this post, we explore the role-based access control (RBAC) features of Amazon Redshift and how you can use roles to simplify managing privileges required to your end-users. By assigning different privileges to different roles and assigning these roles to different users, enterprises can have more granular control of elevated user access. Instead, enterprises want to design their overarching security posture based on the specific duties performed via roles and assign these elevated privilege roles to different users. One of the challenges with security is that enterprises don’t want to have a concentration of superuser privileges amongst a handful of users.

With Amazon Redshift, you can analyze all your data to derive holistic insights about your business and your customers. Amazon Redshift is a fully managed, petabyte-scale data warehouse service in the cloud.

Redshift create user super