Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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 Serverless Containers
  • Comparing with other Yandex Cloud services
    • All guides
    • Getting an IAM token for a service account using a container
      • Making a revision active
      • Changing the container operation mode
      • Adding environment variables
      • Providing Yandex Lockbox secrets
      • Specifying a cloud network
      • Setting the number of concurrent container instance calls
      • Viewing monitoring charts
      • Migrating to the ru-central1-d availability zone
      • Deleting a container
    • Viewing operations with service resources
  • Access management
  • Tools
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Managing a container
  3. Migrating to the ru-central1-d availability zone

Migrating containers to the ru-central1-d availability zone

Written by
Yandex Cloud
Updated at May 14, 2026

To migrate subnets for Cloud Functions, Serverless Containers, or API Gateway to a different zone, follow these steps:

  1. In the cloud network hosting the subnets, create a new subnet.

    The requirements are as follows:

    • The subnet must be in the zone you want to migrate your resources to.
    • Make sure the subnet is the same for all functions, containers, and API gateways.
    • It must not contain any resources except functions, containers, and API gateways.
  2. Provide the new subnet ID to technical support.

The support team will migrate your resources to the specified subnet for you.

Was the article helpful?

Previous
Writing logs
Next
Deleting a container
© 2026 Direct Cursus Technology L.L.C.