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

Deleting an access policy

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 delete an access policy created for a folder, cloud, or organization.

Note

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

Deleting an access policy created for a folder

To delete an access policy created for a folder:

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

  1. Get a list of IDs of access policy templates assigned for the folder.

  2. Run this command:

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

    Where:

    • --name: Name of the folder to delete the policy for. Instead of the folder name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the access policy template you want to delete for the specified folder.

  3. Make sure the policy was deleted.

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. In the configuration, locate the yandex_resource_manager_folder_iam_policy_binding resource with the IDs of the policy template in access_policy_template_id and folder in folder_id.

  2. Remove the section of that resource. Do not delete the folder resource itself.

  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.

    Make sure the plan removes only the correct policy binding. These steps apply to the binding managed by the current Terraform configuration.

Use the unbindAccessPolicy REST API method for the Folder resource or the FolderService/UnbindAccessPolicy gRPC API call.

The specified access policy will no longer apply to resources in the specified folder.

Deleting an access policy created for a cloud

To delete an access policy created for a cloud:

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

  1. Get a list of IDs of access policy templates assigned for the cloud.

  2. Run this command:

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

    Where:

    • --name: Name of the cloud to delete the policy for. Instead of the cloud name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the access policy template you want to delete for the specified cloud.

  3. Make sure the policy was deleted.

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. In the configuration, locate the yandex_resource_manager_cloud_iam_policy_binding resource with the IDs of the policy template in access_policy_template_id and cloud in cloud_id.

  2. Remove the section of that resource. The cloud resource itself should not be deleted.

  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.

    Make sure the plan removes only the correct policy binding. These steps apply to the binding managed by the current Terraform configuration.

Use the unbindAccessPolicy REST API method for the Cloud resource or the CloudService/UnbindAccessPolicy gRPC API call.

The specified access policy will no longer apply to resources within all folders in the given cloud.

Deleting an access policy created for an organization

To delete an access policy created for an organization, follow these steps:

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

  1. Get a list of IDs of access policy templates assigned for the organization.

  2. Run this command:

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

    Where:

    • --name: Name of the organization to delete the policy for. Instead of the organization name, you can provide its ID in the --id parameter.
    • --access-policy-template-id: ID of the access policy template you want to delete for the specified organization.

  3. Make sure the policy was deleted.

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. In the configuration, locate the yandex_organization_manager_organization_iam_policy_binding resource with the IDs of the policy template in access_policy_template_id and organization in organization_id.

  2. Remove the section of that resource. The organization resource itself should not be deleted.

  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.

    Make sure the plan removes only the correct policy binding. These steps apply to the binding managed by the current Terraform configuration.

Use the unbindAccessPolicy REST API method for the Organization resource or the OrganizationService/UnbindAccessPolicy gRPC API call.

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

Useful links

Previous
Viewing policies created for a resource
Next
Overview