Logging in and accessing resources
How do I log in to the management console?
Go to the management console page
If not logged in to your Yandex or Yandex 360 account yet, click Log in. If you do not have an account yet, click Register. For more information, see (https://yandex.com/support/passport/auth.html).
How do I grant a user access to the management console and a folder?
To grant access to the management consoleresource-manager.clouds.member role for the cloud. Assign resource access permissions for the specific folder or resource. Here is an example:
- A user holding the
resource-manager.clouds.memberrole for a cloud andcompute.editorfor a folder can work with Compute Cloud resources in that folder via the management console. - A user holding the
resource-manager.clouds.memberrole for a cloud andresource-manager.viewerfor a folder can view information about the folder and access permissions assigned for it.
If a user already has the admin role for a folder but cannot see the folder in the console, check their cloud access role. Assigning the admin role for the entire cloud is excessive, as this role grants permissions for all folders and resources in that cloud.
For other roles that provide console access, see Cloud member. For information on how to assign roles, see this guide.
What do I do if I get the User has to accept the End User License Agreement error when trying to get an IAM token?
When getting an IAM token via the Yandex Cloud CLI, Terraform, or a direct request to the API, you may get one of these errors:
User has to accept the End User License Agreement to get an IAM tokenUser has to accept the End User License Agreement and Privacy Policy to get an IAM token
The error means that the user requesting the IAM token has not accepted the required agreements yet.
To solve the error, log in to the user’s account and accept the license agreement and privacy policy on the agreement acceptance page
If instead of the agreement acceptance page you see a folder in the management console, log out of the account and then log back in. You can also try opening the link in incognito mode or in another browser.
If the agreements are already accepted, make sure the token in the CLI profile, Terraform provider settings, or the API request belongs to the same user. For an OAuth token, you can figure out the owner by requesting user infologin field of the response will contain the Yandex account login.
To work in the CLI as a federated or local user, configure authentication appropriately:
- Authenticating with the Yandex Cloud CLI as a federated user
- Authenticating in the Yandex Cloud CLI as a local user
How are access permissions verified?
Before performing an operation with a resource, such as creating a VM, IAM checks whether the user has all the required permissions. If any of the required permissions are missing, the operation will fail and Yandex Cloud will report an error. For more information, see How access management works in Yandex Cloud.
What is a resource?
A resource is a Yandex Cloud entity you can manage through operations, such as creating, updating, viewing, or deleting. Here are some examples of resources: VMs, disks, service accounts, clouds, and folders. For more information, see Yandex Cloud resource hierarchy in the Resource Manager guides.
How do I change the cloud owner?
- Add the new owner to the organization if they are not already a member.
- On behalf of the current owner, assign the user the
resource-manager.clouds.ownerrole for the cloud. - Check the new owner’s access. Then revoke the
resource-manager.clouds.ownerrole from the previous owner. Optionally, assign them other roles in accordance with their responsibilities.
A cloud must have at least one owner. Changing the organization owner is a separate operation.
If facing any issues when trying to change the owner, contact support
How do I change the organization owner?
On behalf of the current owner, assign the organization-manager.organizations.owner role to the new owner. The new owner must be the organization member.
After verifying the new owner’s access, revoke this role from the previous owner. Do not remove the previous owner from the organization unless they no longer need access.
If facing any issues when trying to perform these actions, contact support