Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • container_registry
          • container_registry_iam_binding
          • container_registry_ip_permission
          • container_repository
          • container_repository_iam_binding
          • container_repository_lifecycle_policy

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Container Registry
  4. Resources
  5. container_registry_ip_permission

yandex_container_registry_ip_permission (Resource)

Written by
Yandex Cloud
Updated at August 7, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

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

Example usageExample usage

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

  labels = {
    my-label = "my-label-value"
  }
}

resource "yandex_container_registry_ip_permission" "my_ip_permission" {
  registry_id = yandex_container_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"]
}

SchemaSchema

RequiredRequired

  • registry_id (String) The ID of the registry that ip restrictions applied to.

OptionalOptional

  • pull (Set of String) List of configured CIDRs, from which pull is allowed.
  • push (Set of String) List of configured CIDRs, from which push is allowed.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • id (String) The ID of this resource.

Nested Schema for Nested Schema for timeouts

Optional:

  • default (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 the resource ID you can use Yandex Cloud Web Console or YC CLI.

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

Was the article helpful?

Previous
container_registry_iam_binding
Next
container_repository
© 2025 Direct Cursus Technology L.L.C.