Access management in Managed Service for Greenplum®
In this section, you will learn:
- Which resources you can assign a role for.
- Which roles exist in the service.
- Which roles are required for particular actions.
About access management
In Yandex Cloud, all transactions are checked in Yandex Identity and Access Management. If a subject does not have the required permission, the service returns an error.
To grant permission for a resource, assign roles for this resource to the subject that will perform operations. Roles can be assigned to a Yandex account, a service account, federated users, a user group, or a system group. For more information, see How access management works in Yandex Cloud.
Only users with the admin
, resource-manager.clouds.owner
, or organization-manager.organizations.owner
role for a resource can assign roles for this resource.
Which resources you can assign a role for
As with other services, you can assign roles for clouds, folder and service accounts. The roles assigned for clouds and folders also apply to nested resources.
To allow access to Managed Service for Greenplum® service resources (DB clusters and hosts, cluster backups, databases, and their users), assign the user the appropriate roles for the folder or cloud hosting the resources.
Which roles exist in the service
The chart below shows which roles are available in the service and how they inherit each other's permissions. For example, the editor
role includes all the permissions of viewer
. You can find the description of each role under the chart.
Service roles
managed-greenplum.auditor
The managed-greenplum.auditor
role allows you to view information about Greenplum® clusters and hosts, as well as quotas and resource operations for Managed Service for Greenplum®.
managed-greenplum.viewer
The managed-greenplum.viewer
role allows you to view information about Greenplum® clusters and hosts, their logs, as well as information about quotas and service resource operations.
Users with this role can:
- View information about Greenplum® clusters.
- View information about Greenplum® cluster hosts.
- View information about Greenplum® backups.
- View Greenplum® cluster logs.
- View information about the results of Greenplum® cluster performance diagnostics.
- View information about quotas of Managed Service for Greenplum®.
- View information about resource operations for Managed Service for Greenplum®.
This role also includes the managed-greenplum.auditor
permissions.
managed-greenplum.editor
The managed-greenplum.editor
role allows you to manage Greenplum® clusters and view their logs, as well as get information about quotas and service resource operations.
Users with this role can:
- View information about Greenplum® clusters, as well as create, modify, delete, run, and stop them.
- View information about Greenplum® cluster hosts, as well as create, modify, and delete them.
- View information about Greenplum® backups, as well as create and delete them.
- View Greenplum® cluster logs.
- View information about the results of Greenplum® cluster performance diagnostics.
- View information about quotas of Managed Service for Greenplum®.
- View information about resource operations for Managed Service for Greenplum®.
This role also includes the managed-greenplum.viewer
permissions.
To create Greenplum® clusters, you also need the vpc.user
role.
managed-greenplum.admin
The managed-greenplum.admin
role allows you to manage Greenplum® clusters and view their logs, as well as get information about quotas and service resource operations.
Users with this role can:
- Manage access to Greenplum® clusters.
- View information about Greenplum® clusters, as well as create, modify, delete, run, and stop them.
- View information about Greenplum® cluster hosts, as well as create, modify, and delete them.
- View information about Greenplum® backups, as well as create and delete them.
- View Greenplum® cluster logs.
- View information about the results of Greenplum® cluster performance diagnostics.
- View information about quotas of Managed Service for Greenplum®.
- View information about resource operations for Managed Service for Greenplum®.
This role also includes the managed-greenplum.editor
permissions.
To create Greenplum® clusters, you also need the vpc.user
role.
mdb.auditor
The mdb.auditor
role grants the minimum permissions required to view information about managed database clusters (without access to data or runtime logs).
Users with this role can view information about managed database clusters, quotas, and folders.
This role also includes the managed-elasticsearch.auditor
, managed-opensearch.auditor
, managed-kafka.auditor
, managed-mysql.auditor
, managed-sqlserver.auditor
, managed-postgresql.auditor
, managed-greenplum.auditor
, managed-clickhouse.auditor
, managed-redis.auditor
, and managed-mongodb.auditor
permissions.
mdb.viewer
The mdb.viewer
role grants read access to managed database clusters and cluster runtime logs.
Users with this role can read from databases, inspect the logs of managed database clusters, and view information about clusters, quotas, and folders.
This role also includes the mdb.auditor
, managed-elasticsearch.viewer
, managed-opensearch.viewer
, managed-kafka.viewer
, managed-mysql.viewer
, managed-sqlserver.viewer
, managed-postgresql.viewer
, managed-greenplum.viewer
, managed-clickhouse.viewer
, managed-redis.viewer
, managed-mongodb.viewer
, and dataproc.viewer
permissions.
mdb.admin
The mdb.admin
role grants full access to managed database clusters.
Users with this role can create, edit, delete, run, and stop managed database clusters, manage cluster access, read and write to databases, and view information about clusters, runtime logs, quotas, and folders.
This role also includes the mdb.viewer
, vpc.user
, managed-elasticsearch.admin
, managed-opensearch.admin
, managed-kafka.admin
, managed-mysql.admin
, managed-sqlserver.admin
, managed-postgresql.admin
, managed-greenplum.admin
, managed-clickhouse.admin
, managed-redis.admin
, managed-mongodb.admin
, and dataproc.admin
permissions.
vpc.publicAdmin
The vpc.publicAdmin
role allows you to manage NAT gateways, public IP addresses, and external network connectivity, as well as view information on the quotas, resources, and resource operations. This role grants administrator privileges for multi-interface instances that provide connectivity between multiple networks.
- View information on cloud networks and configure external access to them.
- Manage connectivity of multiple cloud networks.
- Manage multi-interface instances that provide connectivity between multiple networks.
- View information on subnets and modify them.
- View information on NAT gateways, as well as create, modify, and delete them.
- Connect NAT gateways to route tables.
- View information on cloud resource addresses, as well as create, update, and delete public IP addresses.
- View information on route tables, as well as link route tables to subnets.
- View information on security groups.
- View information on the IP addresses used in subnets.
- View information on Virtual Private Cloud quotas.
- View information on resource operations for Virtual Private Cloud.
- View information on resource operations for Compute Cloud.
- View information on the relevant cloud.
- View information on the relevant folder.
This role also includes the vpc.viewer
permissions.
You can assign a role for a cloud or folder. Important: If a network and subnet are in different folders, the vpc.publicAdmin
role is checked for the folder where the network is located.
Primitive roles
auditor
Grants permission to view service configuration and metadata without access to data.
viewer
Enables you to view information about resources.
editor
Allows managing (creating, editing, and deleting) resources.
admin
Allows you to manage your resources and access to them.
For more information about primitive roles, see the Yandex Cloud role reference.
Roles required
To use the service, you need the managed-greenplum.editor
role or higher for the folder where a cluster is created. The managed-greenplum.viewer
role only enables you to view the cluster list.
You can always assign a role with more permissions. For instance, you can assign managed-greenplum.admin
instead of managed-greenplum.editor
.
What's next
- How to assign a role.
- How to revoke a role.
- Learn more about access management in Yandex Cloud.
- Learn more about inheriting roles.
Greenplum® and Greenplum Database® are registered trademarks or trademarks of VMware, Inc. in the United States and/or other countries.