Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex IoT Core
  • Service shutdown
    • All guides
    • Sending messages
    • Subscribing a device or registry to receive messages
    • Exporting messages to Data Streams
    • Viewing a connection log
      • Getting information about a registry
      • Creating a registry
      • Updating a registry
      • Disabling and enabling a registry
      • Deleting a registry
    • Viewing operations with service resources
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Managing registries
  3. Creating a registry

Creating a registry

Written by
Yandex Cloud
Improved by
Danila N.
Updated at August 6, 2026
View in Markdown

Warning

Yandex IoT Core is no longer available to new users.

Current users can create resources until November 1, 2026. Afterwards, the service will go read-only and cease to operate on December 1, 2026. For more information on the timing and procedure, see Service shutdown.

Management console
CLI
Terraform
API
  1. In the management console, select the folder where you want to create your registry.

  2. Navigate to IoT Core.

  3. In the left-hand panel, select Registries.

  4. Click Create registry.

  5. Under General information, specify the following:

    • Registry Name, e.g., my-registry.

    • Optionally, Description with additional information about the registry.

    • Password to use when accessing the registry. To create a password, you can use this password generator.

      Note

      Save the password, as you will need it for authentication.

    • Optionally, to assign a label to the registry, fill out the Key and Value fields and click Add label.

  6. Optionally, add a certificate:

    • To add a file:

      1. Select the File method.
      2. Click Attach file.
      3. Select the file with the certificate’s public key and click Open.
      4. Click Add.
    • To add text:

      1. Select the Text method.
      2. Paste the certificate’s public key into the Content field.
      3. Click Add.
  7. Click Create.

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. Create a registry:

    yc iot registry create --name <registry_name>
    

    The registry naming requirements are as follows:

    • Length: between 3 and 63 characters.
    • It can only contain lowercase Latin letters, numbers, and hyphens.
    • It must start with a letter and cannot end with a hyphen.

    Result:

    id: b91hafek85**********
    folder_id: aoek49ghmk*********
    created_at: "2019-05-27T13:40:06.923Z"
    name: <registry_name>
    status: ACTIVE
    log_group_id: ckghotead**********
    
  2. Optionally, set a password for the registry for username and password authentication:

    yc iot registry password add --registry-name <registry_name>
    

    You will be prompted to enter a password. Follow these password requirements:

    • The password must contain numbers, uppercase and lowercase letters, and special characters.
    • The password must be at least 14 characters long.

    Result:

    registry_id: b91hafek85**********
    id: aoek49ghmk*********
    created_at: "2019-05-27T13:44:06.923Z"
    
  3. Optionally, add a certificate to the registry for certificate-based authentication:

    yc iot registry certificate add \
       --registry-name <registry_name> \
       --certificate-file <certificate>
    

    Where:

    • --registry-name: Registry name.
    • --certificate-file: Path to the public key of the certificate, e.g., cert.pem.

    Result:

    registry_id: b91hafek85**********
    fingerprint: 589ce16050****
    certificate_data: |
       -----BEGIN CERTIFICATE-----
       MIIE/jCCAuagAwIBAgIJAPRA...
       -----END CERTIFICATE-----
    created_at: "2019-05-27T13:41:45.295Z"
    

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.

Note

To add certificates to a registry, create them in advance.

To create a device registry:

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

    • yandex_iot_core_registry: Registry settings:

      • name: Registry name.
      • description: Registry description.
      • labels: Registry labels in key:value format.
      • passwords: List of registry passwords for username and password authentication.
      • certificates: List of registry certificates for certificate-based authentication.

    Note

    Use only one of the two authentication methods.

    Here is an example of a resource structure in the configuration file:

    resource "yandex_iot_core_registry" "my_registry" {
      name        = "test-registry"
      description = "test registry for terraform provider documentation"
      labels = {
        test-label = "label-test"
      }
    
      passwords = [
        "<password_1>",
        "<password_2>"
      ]
    
      certificates = [
        file("<path_to_first_certificate_file>"),
        file("<path_to_second_certificate_file>")
      ]
    }
    
    output "yandex_iot_core_registry_my_registry" {
      value = "${yandex_iot_core_registry.my_registry.id}"
    }
    

    For more information about the resources you can create with Terraform, see this provider guide.

  2. Make sure the configuration files are correct.

    1. In the terminal, navigate to the directory where you created your configuration file.

    2. Run a check using this command:

      terraform plan
      

    If the configuration is correct, the terminal will display a list of the resources and their settings. Terraform will show any errors detected in the configuration.

  3. Deploy the cloud resources.

    1. If the configuration is correct, run this command:

      terraform apply
      
    2. Confirm creating the resources.

      This will create all the resources you need in the specified folder. You can check the new resources and their settings using the management console or this CLI command:

      yc iot registry list
      

To create a registry, use the create REST API method for the Registry resource or the RegistryService/Create gRPC API call.

Was the article helpful?

Previous
Getting information about a registry
Next
Updating a registry
© 2026 Direct Cursus Technology L.L.C.