Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Setting up Yandex Cloud Terraform provider authentication
  • Solution library
    • Overview
    • Release notes
          • cloudregistry_folder
          • cloudregistry_folder_iam_binding
          • cloudregistry_folder_iam_member
          • cloudregistry_lifecycle_policy
          • cloudregistry_registry
          • cloudregistry_registry_iam_binding
          • cloudregistry_registry_iam_member
          • cloudregistry_registry_ip_permission
          • cloudregistry_scan_policy

In this article:

  • Example usage
  • Arguments & Attributes Reference
  • Import
  1. Terraform reference
  2. Resources
  3. Cloud Registry
  4. Resources
  5. cloudregistry_registry_ip_permission

yandex_cloudregistry_registry_ip_permission (Resource)

Written by
Yandex Cloud
Updated at April 9, 2026
View in Markdown
  • Example usage
  • Arguments & Attributes Reference
  • Import

Creates a new Cloud Registry IP Permission. For more information, see the official documentation

Example usageExample usage

//
// Create a new Cloud Registry and new IP Permissions for it.
//
resource "yandex_cloudregistry_registry" "my_registry" {
  name      = "test-registry"
  folder_id = "test_folder_id"

  labels = {
    my-label = "my-label-value"
  }
  kind      = "DOCKER"
  type      = "LOCAL"

  description = "Some desctiption"
}

resource "yandex_cloudregistry_registry_ip_permission" "my_ip_permission" {
  registry_id = yandex_cloudregistry_registry.my_registry.id
  push        = ["10.1.0.0/16", "10.2.0.0/16", "10.3.0.0/16"]
  pull        = ["10.1.0.0/16", "10.5.0/16"]
}

Arguments & Attributes ReferenceArguments & Attributes Reference

  • id (Read-Only) (String). The ID of IP permission.
  • pull (Set Of String). List of configured CIDRs from which pull operations are allowed.
  • push (Set Of String). List of configured CIDRs from which push operations are allowed.
  • registry_id (Required)(String). The ID of the registry that IP restrictions are applied to.
  • timeouts [Block].
    • create (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
    • delete (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
    • read (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
    • update (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting it you can use Yandex Cloud Web Console or Yandex Cloud CLI.

# terraform import yandex_cloudregistry_registry_ip_permission.<resource Name> <registry_id>
terraform import yandex_cloudregistry_registry_ip_permission.my_ip_permission crps9**********k9psn

Was the article helpful?

Previous
cloudregistry_registry_iam_member
Next
cloudregistry_scan_policy
© 2026 Direct Cursus Technology L.L.C.