Access management in Load Testing

Load Testing uses roles to manage access permissions.

In this section, you will learn:

• Resources you can assign a role for.
• What roles this service has.
• What roles are required for specific actions.

Access managementAccess management

Yandex Identity and Access Management checks all operations in Yandex Cloud. If an entity does not have required permissions, IAM returns an error.

To grant permissions for a resource, assign the relevant resource roles to an entity performing operations. You can assign roles to a Yandex account, service account, local user, federated user, user group, system group, or public group. For more information, see How access management works in Yandex Cloud.

To assign roles for a resource, you need to have one of the following roles for that resource:

• admin
• resource-manager.admin
• organization-manager.admin
• resource-manager.clouds.owner
• organization-manager.organizations.owner

Resources you can assign a role forResources you can assign a role for

You can assign a role to an organization, cloud, or folder. The roles assigned to organizations, clouds, and folders also apply to their nested resources.

Roles this service hasRoles this service has

The chart below shows service’s roles and their permission inheritance. For example, editor inherits all viewer permissions. You can find role descriptions below the chart.

Service rolesService roles

loadtesting.viewerloadtesting.viewer

The loadtesting.viewer role allows you to view info on load generators and tests, as well as folder metadata.

Users with this role can:

• View info on load tests and reports on their run.
• View info on load test configurations.
• View info on load test regression dashboards.
• View info on agents.
• View info on Yandex Object Storage buckets used in load tests.
• View info on the relevant folder.

loadtesting.editorloadtesting.editor

The loadtesting.editor role enables managing agents, load tests and their settings, data stores, and regression dashboards. It also allows you to register agents created outside Load Testing.

Users with this role can:

• View info on load tests and reports on their run.
• Create, modify, delete, run and stop load tests and load test data into them.
• View info on load test configurations, as well as create, modify, and delete such configurations.
• View info on agents and create, modify, delete, run, restart, and stop them.
• Register external agents in Load Testing.
• View info on Yandex Object Storage buckets used in load tests, upload test data to them, and create, modify, and delete buckets.
• View info on regression dashboards, as well as create, modify, and delete such dashboards.
• View information on the relevant folder.

This role includes the loadtesting.viewer, loadtesting.loadTester, and loadtesting.externalAgent permissions.

loadtesting.adminloadtesting.admin

The loadtesting.admin role enables managing agents, load tests and their settings, data stores, and regression dashboards. It also allows you to register agents created outside Load Testing.

Users with this role can:

• View info on load tests and reports on their run.
• Create, modify, delete, run and stop load tests and load test data into them.
• View info on load test configurations, as well as create, modify, and delete such configurations.
• View info on agents and create, modify, delete, run, restart, and stop them.
• Register external agents in Load Testing.
• View info on Yandex Object Storage buckets used in load tests, upload test data to them, and create, modify, and delete buckets.
• View info on regression dashboards, as well as create, modify, and delete such dashboards.
• View information on the relevant folder.

This role includes the loadtesting.editor permissions.

loadtesting.loadTesterloadtesting.loadTester

The loadtesting.loadTester role enables managing agents, load tests and their settings, data stores, and regression dashboards.

Users with this role can:

• View info on load tests and reports on their run.
• Create, modify, delete, run and stop load tests and load test data into them.
• View info on load test configurations, as well as create, modify, and delete such configurations.
• View info on agents and create, modify, delete, run, restart, and stop them.
• View info on Yandex Object Storage buckets used in load tests, upload test data to them, and create, modify, and delete buckets.
• View info on regression dashboards, as well as create, modify, and delete such dashboards.
• View information on the relevant folder.

loadtesting.generatorClientloadtesting.generatorClient

The loadtesting.generatorClient role allows you to create, modify, and run load tests using an agent, as well as enables uploading test results to the storage.

Users with this role can:

• Create, edit, and run load tests.
• Create and edit load test configurations.
• Upload the test result data to the storage.

Assign this role to the service account under which you create a VM with an agent.

loadtesting.externalAgentloadtesting.externalAgent

The loadtesting.externalAgent role enables registering external agents in Load Testing, as well as creating, modifying, and running load tests using an agent.

Users with this role can:

• Register external agents in Load Testing.
• Create, edit, and run load tests.
• Create and edit load test configurations.
• Upload the test result data to the storage.

This role includes the loadtesting.generatorClient permissions.

Assign this role to the service account under which you create a VM with an agent.

Primitive rolesPrimitive roles

Primitive roles allow users to perform actions in all Yandex Cloud services.

auditorauditor

The auditor role grants a permission to read configuration and metadata of any Yandex Cloud resources without any access to data.

For instance, users with this role can:

• View info on a resource.
• View the resource metadata.
• View the list of operations with a resource.

auditor is the most secure role that does not grant any access to the service data. This role suits the users who need minimum access to the Yandex Cloud resources.

viewerviewer

The viewer role grants the permissions to read the info on any Yandex Cloud resources.

This role includes the auditor permissions.

Unlike auditor, the viewer role provides access to service data in read mode.

editoreditor

The editor role provides permissions to manage any Yandex Cloud resources, except for assigning roles to other users, transferring organization ownership, removing an organization, and deleting Key Management Service encryption keys.

For instance, users with this role can create, modify, and delete resources.

This role includes the viewer permissions.

adminadmin

The admin role enables assigning any roles, except for resource-manager.clouds.owner and organization-manager.organizations.owner, and provides permissions to manage any Yandex Cloud resources (except for transferring organization ownership and removing an organization).

Prior to assigning the admin role for an organization, cloud, or billing account, make sure to check out the information on protecting privileged accounts.

This role includes the editor permissions.

Instead of primitive roles, we recommend using service roles with more granular access control, allowing you to implement the least privilege principle.

For more information about primitive roles, see the Yandex Cloud role reference.

What's nextWhat's next

• How to assign a role.
• How to revoke a role.
• Learn more about access management in Yandex Cloud.
• Learn more about role inheritance.