Configuring access permissions for a bucket using Identity and Access Management

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

1. See the description of the CLI command for updating bucket settings:

   yc storage bucket update --help
   

2. Assign a role for the bucket:

   yc storage bucket update \
     --name <bucket_name> \
     --grants grantee-id=<account_ID>,grant-type=<subject_type>,permission=<permission>
   

   Where:

   • --name: Bucket name.
   • --grants: ACL access permission settings:
     • grantee-id: ID of the account the permissions are granted to. Used when the value is grant-type=grant-type-account.
     • grant-type: Type of entity the permissions are granted to. The possible values are:
       • grant-type-account: User or service account.
       • grant-type-all-authenticated-users: All authenticated users.
       • grant-type-all-users: All users.
     • permission: Permission. The possible values are:
       • permission-full-control: Full access to the bucket and objects in it.
       • permission-write: Writing objects to the bucket.
       • permission-write-acp: Editing bucket ACL.
       • permission-read: Reading objects in the bucket.
       • permission-read-acp: Reading bucket ACL.

If the yc storage bucket update command is called, the bucket's assigned ACL roles are overwritten, not appended. To preserve existing permissions settings, they must be re-listed in the --grants parameter.

Learn more about the yc storage bucket update command in the YC CLI reference.

ExampleExample

To assign a service account full access to a bucket using the CLI:

1. Get a list of buckets in the default folder:

   yc storage bucket list
   

   Result:

   +------------------+----------------------+----------+-----------------------+---------------------+
   |       NAME       |      FOLDER ID       | MAX SIZE | DEFAULT STORAGE CLASS |     CREATED AT      |
   +------------------+----------------------+----------+-----------------------+---------------------+
   | my-bucket        | b1gmit33ngp3******** | 10       | STANDARD              | 2022-12-16 13:58:18 |
   +------------------+----------------------+----------+-----------------------+---------------------+
   

2. Get a list of service accounts in the default folder:

   yc iam service-account list
   

   Result:

   +----------------------+--------------+--------+---------------------+-----------------------+
   |          ID          |     NAME     | LABELS |     CREATED AT      | LAST AUTHENTICATED AT |
   +----------------------+--------------+--------+---------------------+-----------------------+
   | ajeg2b2et02f******** | my-robot     |        | 2024-09-08 18:59:45 | 2025-02-18 10:10:00   |
   | ajegtlf2q28a******** | account-name |        | 2023-06-27 16:18:18 | 2025-02-18 10:20:00   |
   +----------------------+--------------+--------+---------------------+-----------------------+
   

3. Assign a role for the bucket:

   yc storage bucket update \
     --name my-bucket \
     --grants grantee-id=ajeg2b2et02f********,grant-type=grant-type-account,permission=permission-full-control
   

Result:

name: my-bucket
folder_id: b1g0ijbfaqsn********
default_storage_class: STANDARD
versioning: VERSIONING_DISABLED
max_size: "53687091200"
acl:
  grants:
    - permission: PERMISSION_FULL_CONTROL
      grant_type: GRANT_TYPE_ACCOUNT
      grantee_id: ajeg2b2et02f********
created_at: "2026-04-30T09:48:38.836171Z"
resource_id: e3ev6mif5rb1********

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

To assign a role for a bucket using Terraform:

1. In the Terraform configuration file, describe the resources you want to create:

   resource "yandex_storage_bucket_iam_binding" "mybucket-viewers" {
     bucket  = "<bucket_name>"
     role    = "<role>"
     members = [
                 "<subject_type>:<subject_ID>",
                 "serviceAccount:<service_account_ID>",
                 "userAccount:<user_ID>"
               ]
   }
   
   # Example of assigning the `storage.editor` role to service accounts
   resource "yandex_storage_bucket_iam_binding" "sa-editors" {
     bucket  = "<bucket_name>"
     role    = "storage.editor"
     members = [
                 "serviceAccount:<service_account_1_ID>",
                 "serviceAccount:<service_account_2_ID>"
               ]
   }
   
   # Example of assigning the `storage.admin` role to users 
   resource "yandex_storage_bucket_iam_binding" "users-admins" {
     bucket  = "<bucket_name>"
     role    = "storage.admin"
     members = [
                 "userAccount:<user_1_ID>",
                 "userAccount:<user_2_ID>"
               ]
   }
   

   Where:

   • bucket: Bucket name.

   • role: Role to assign.

     Warning

     You cannot use the yandex_storage_bucket_iam_binding resource to assign primitive roles, such as viewer, editor, or admin for a bucket if the yandex_storage_bucket_grant resource or the acl or grant parameters of the yandex_storage_bucket resource are used simultaneously.

   • members: Types and IDs of entities getting the role. Specify it as userAccount:<user_ID> or serviceAccount:<service_account_ID>.

   For more information about the yandex_storage_bucket_iam_binding resource properties, see this provider guide.

2. If you intend to use the yandex_storage_bucket_iam_binding resource together with yandex_storage_bucket_grant for the same bucket, we recommend creating them sequentially. To do this, add a dependency on the yandex_storage_bucket_grant resource to the yandex_storage_bucket_iam_binding section.

   resource "yandex_storage_bucket_iam_binding" "mybucket-viewers" {
     ...
   
     depends_on = [
       yandex_storage_bucket_grant.my_bucket_grant
     ]
   }
   

3. Apply the configuration:

   1. In the terminal, navigate to the configuration file directory.

   2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      

   3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

   4. Apply the configuration changes:

      terraform apply
      

   5. Type yes and press Enter to confirm the changes.

   You can check the resource update using the management console.

Use the updateAccessBindings REST API method for the Bucket resource or the BucketService/UpdateAccessBindings gRPC API call.