Access management in Certificate Manager
In this section, you will learn:
- Which resources you can assign roles to.
- Which roles exist in the service.
- Which roles are required for particular actions.
About access management
All transactions in Nebius Israel are checked by the Identity and Access Management service. If a subject doesn't 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 Google account, a service account, federated users, a user group, or a system group. For more information, see How access management works in Nebius Israel.
Only users with the admin or resource-manager.clouds.owner role for a resource can assign roles for this resource.
Which resources you can assign roles to
You can assign a role to a cloud, a folder, or a certificate. These roles also apply to nested 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
Active roles in the service:
-
certificate-manager.admin: Lets you manage certificates and access them. -
certificate-manager.certificates.downloader: Lets you get the contents of a certificate. -
resource-manager.clouds.owner: Grants you full access to the cloud and the resources in it. You can only assign this role for a cloud. -
resource-manager.clouds.memberis required for everyone except the cloud owners and service accounts to access resources in a cloud not owned by the organization.
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 you to manage resources, e.g., create, edit, and delete them.
admin
Allows you to manage your resources and access to them.
For more information about primitive roles, see Roles.
What roles do I need
The table below lists the roles needed to perform a particular action. You can always assign a role granting more permissions than the role specified. For example, you can assign the editor role instead of the viewer one.
| Action | Methods | Required roles |
|---|---|---|
| Certificate Manager | ||
| Get a list of certificates or domains | list |
viewer for a folder |
| Get certificate or domain details | get |
viewer for a certificate or folder |
| Add a Let's Encrypt certificate | requestNew |
editor for the folder |
| Update and delete a Let's Encrypt certificate | update, delete |
editor for the certificate or folder |
| Add a custom certificate | create |
editor for the folder |
| Renew, update, or delete a custom certificate | update, delete |
editor for the certificate or folder |
| Get the contents of a custom certificate or a Let's Encrypt certificate | get-content |
certificate-manager.certificates.downloader for the certificate or folder |
| Create a domain | create |
editor for the folder |
| Update a domain and delete a domain | update, delete |
editor for the domain or folder |
| Update a domain certificate | setPrimaryCertificate |
editor for the domain or folder |
| IAM | ||
| Grant a role, revoke a role, and view the roles assigned for a folder or cloud | setAccessBinding, updateAccessBindings, listAccessBindings |
admin or certificate-manager.admin for the certificate, domain, or folder |