Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Creating an access policy for a resource

Written by
View in Markdown

Access policies are a Yandex Identity and Access Management mechanism that allows you to manage permissions for specific operations with Yandex Cloud resources. Access policies are based on templates and complement the role system for more flexible access management.

You can create an access policy for a folder, cloud, or organization.

Note

To manage access policies, a user must have one of the following roles:

Creating an access policy for a folder

To create a folder access policy from a template without parameters:

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

  1. Get a list of supported access policy templates with their IDs.

  2. Run this command:

    yc resource-manager folder bind-access-policy \
  --name <folder_name> \
  --access-policy-template-id=<policy_template_ID>

    Where:

    • --name: Name of the folder to create the policy for. Instead of the folder name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the template to use as the basis for the new access policy for the folder.

  3. Make sure the policy was created.

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 guides 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.

  1. Get the ID of the access policy template without parameters.

  2. Add the yandex_resource_manager_folder_iam_policy_binding resource to the configuration:

    resource "yandex_resource_manager_folder_iam_policy_binding" "policy" {
  folder_id = "<folder_ID>"
  access_policy_template_id = "<policy_template_ID>"
}

    Where folder_id is the folder ID, and access_policy_template_id is the access policy template ID. This resource creates a policy template binding rather than assigning a role to a subject.

    For more information, see this provider guide.

  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.

Use the bindAccessPolicy REST API method for the Folder resource or the FolderService/BindAccessPolicy gRPC API call.

The created access policy will apply to all resources in the specified folder.

Creating an access policy for a cloud

To create an access policy for a cloud based on a template without parameters:

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

  1. Get a list of supported access policy templates with their IDs.

  2. Run this command:

    yc resource-manager cloud bind-access-policy \
  --name <cloud_name> \
  --access-policy-template-id=<policy_template_ID>

    Where:

    • --name: Name of the cloud to create the policy for. Instead of the cloud name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the template to use as the basis for the new access policy for the cloud.

  3. Make sure the policy was created.

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 guides 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.

  1. Get the ID of the access policy template without parameters.

  2. Add the yandex_resource_manager_cloud_iam_policy_binding resource to the configuration:

    resource "yandex_resource_manager_cloud_iam_policy_binding" "policy" {
  cloud_id = "<cloud_ID>"
  access_policy_template_id = "<policy_template_ID>"
}

    Where cloud_id is the cloud ID, and access_policy_template_id is the access policy template ID. This resource creates a policy template binding rather than assigning a role to a subject.

    For more information, see this provider guide.

  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.

Use the bindAccessPolicy REST API method for the Cloud resource or the CloudService/BindAccessPolicy gRPC API call.

The new access policy will apply to resources within all folders in the specified cloud.

Creating an access policy for an organization

To create an access policy for an organization based on a template without parameters:

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

  1. Get a list of supported access policy templates with their IDs.

  2. Run this command:

    yc organization-manager organization bind-access-policy \
  --name <organization_name> \
  --access-policy-template-id=<policy_template_ID>

    Where:

    • --name: Name of the organization you want to create a policy for. Instead of the organization name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the template you want to use as the basis for the new access policy for the organization.

  3. Make sure the policy was created.

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 guides 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.

  1. Get the ID of the access policy template without parameters.

  2. Add the yandex_organization_manager_organization_iam_policy_binding resource to the configuration:

    resource "yandex_organization_manager_organization_iam_policy_binding" "policy" {
  organization_id = "<organization_ID>"
  access_policy_template_id = "<policy_template_ID>"
}

    Where organization_id is the organization ID, and access_policy_template_id, the access policy template ID. This resource creates a policy template binding rather than assigning a role to a subject.

    For more information, see this provider guide.

  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.

Use the bindAccessPolicy REST API method for the Organization resource or the OrganizationService/BindAccessPolicy gRPC API call.

The new access policy will apply to resources within all clouds in the specified organization.

All access policy templates without parameters are assigned for resources in the same way. For information on how to assign a policy template with parameters for a resource, see Examples.

Examples

Creating an access policy for a folder based on the serverless.containers.restrictNetworkAccess template

The serverless.containers.restrictNetworkAccess policy prohibits calling and managing containers in Yandex Serverless Containers from any addresses except explicitly specified IP addresses or Yandex Virtual Private Cloud cloud networks.

To assign the serverless.containers.restrictNetworkAccess policy template for a folder:

yc resource-manager folder bind-access-policy \
  --name my-folder \
  --access-policy-template-id=serverless.containers.restrictNetworkAccess \
  --parameters '"allowed_src_ips=[<IP_address_range_1>,<IP_address_range_2>,<IP_address_range_3>]","allowed_vpc_network_ids=[<network_1_ID>,<network_2_ID>,<network_3_ID>]"'

Where:

  • --parameters: Access policy parameters:

    Alert

    Restrictions specified in parameters are applied using the OR logic.

    • allowed_src_ips: List of IP addresses or IP address ranges in CIDR notation to allow calling and managing containers.

      If you do not want to list IP addresses or IP address ranges, provide an empty list in the parameter: "allowed_src_ips=[]".

    • allowed_vpc_network_ids: List of IDs of cloud networks that allow calling and managing containers via a configured service connection.

      If you do not want to list cloud network IDs, provide an empty list in the parameter: "allowed_vpc_network_ids=[]".

Useful links

Previous
Getting a list of supported policy templates
Next
Viewing policies created for a resource