Access management in SpeechKit
In this section, you will learn:
Access 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.
Resources 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 existing in this service
Service roles
ai.speechkit-stt.user
The ai.speechkit-stt.user role allows you to use Yandex SpeechKit for speech recognition, as well as view info on the relevant cloud, folder, and quotas.
ai.speechkit-tts.user
The ai.speechkit-tts.user role allows you to use Yandex SpeechKit for speech synthesis, as well as view info on the relevant cloud, folder, and quotas.
ai.auditor
The ai.auditor role enables viewing the quotas for Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex AI Studio, viewing the info on AI assistants, datasets, and text generation models in Yandex AI Studio, as well as reading folder metadata.
This role includes the ai.assistants.auditor, ai.datasets.auditor, and ai.models.auditor permissions.
ai.viewer
The ai.viewer role enables viewing the info on quotas for Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex AI Studio, on AI assistants, datasets, and text generation models in Yandex AI Studio, as well as on the relevant folder.
This role includes the ai.auditor, ai.assistants.viewer, ai.datasets.viewer, and ai.models.viewer permissions.
ai.editor
The ai.editor role enables using Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex AI Studio.
Users with this role can:
- Use Yandex Translate to translate texts.
- Use Yandex Vision OCR to analyze images.
- Use Yandex SpeechKit for speech recognition and synthesis.
- Use YandexGPT API language models for text generation, YandexART models for image generation, and AI assistants within Yandex AI Studio.
- View info on datasets, as well as create, modify, and delete them.
- Fine-tune text generation models in Yandex AI Studio, as well as create, modify, and delete such models.
- View info on the relevant cloud and folder.
- View information on Translate, Vision, SpeechKit, and AI Studio quotas.
This role includes the ai.viewer, ai.translate.user, ai.vision.user, ai.speechkit-stt.user, ai.speechkit-tts.user, ai.languageModels.user, ai.imageGeneration.user, ai.assistants.editor, and ai.datasets.editor permissions.
ai.admin
The ai.admin role enables using Yandex Translate, Yandex Vision, Yandex SpeechKit, and Yandex AI Studio.
Users with this role can:
- Use Yandex Translate to translate texts.
- Use Yandex Vision OCR to analyze images.
- Use Yandex SpeechKit for speech recognition and synthesis.
- Use YandexGPT API language models for text generation, YandexART models for image generation, and AI assistants within Yandex AI Studio.
- View info on datasets, as well as create, modify, and delete them.
- Fine-tune text generation models in Yandex AI Studio, as well as create, modify, and delete such models.
- View info on the relevant cloud and folder.
- View information on Translate, Vision, SpeechKit, and AI Studio quotas.
This role includes the ai.editor, ai.assistants.admin, ai.datasets.admin, and ai.models.admin permissions.
For more information about service roles, see Roles in the Yandex Identity and Access Management documentation.
Roles of other services
When working with SpeechKit, you may need roles of other services, for example, to upload results and source materials to an Object Storage bucket.
resource-manager.clouds.owner
The resource-manager.clouds.owner role enables running any operations within the cloud and its child resources.
It also allows you to manage linking the cloud to a billing account (for that purpose, you also need permissions for that billing account). For more information on managing access to a billing account, see the Yandex Cloud Billing documentation.
By default, the users with this role get notifications on what happens to the cloud and its folders.
You can only assign this role for a cloud. Any user creating a cloud automatically gets such a role for the cloud.
This role includes the admin and resource-manager.clouds.member permissions.
storage.uploader
The storage.uploader role allows you to upload objects into buckets with or without overwriting the previously uploaded ones, read data in buckets, view info on buckets and objects inside them, as well as info on the Object Storage folder and quotas. The role does not allow you to delete objects or configure buckets.
Users with this role can:
- View the list of buckets.
- View the lists of objects in buckets, object info and content.
- Upload objects into a bucket.
- View info on access permissions assigned for buckets and objects inside them.
- View bucket CORS configuration info.
- View bucket static website hosting configuration info.
- View bucket access protocol info.
- View bucket action logging settings.
- View bucket versioning settings.
- View bucket encryption settings.
- View bucket default storage class info.
- View bucket labels.
- View bucket region info.
- View object lifecycle configuration info.
- View lists of object versions and version info.
- View info on object version locks and set up such locks.
- View object and object version labels, modify such labels.
- View info on current multipart uploads of objects and their parts, delete partially uploaded objects.
- View cloud, folder, and Object Storage statistics.
- View info on Object Storage quotas.
- View folder info.
This role includes the storage.viewer permissions.
kms.keys.encrypterDecrypter
The kms.keys.encrypterDecrypter role enables viewing info on symmetric encryption keys and using such keys to encrypt or decrypt data.
This role includes the kms.keys.encrypter and kms.keys.decrypter permissions.
Primitive roles
Primitive roles allow users to perform actions in all Yandex Cloud services.
auditor
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.
viewer
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.
editor
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.
admin
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.