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.
Yandex StoreDoc
  • Getting started
    • Resource relationships
    • Networking in Yandex StoreDoc
    • Quotas and limits
    • Storage in Yandex StoreDoc
    • Backups
    • Replication and fault tolerance
    • Sharding
    • Users and roles
    • Maintenance
    • Supported clients
    • Yandex StoreDoc settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Host name and FQDN
  • Public access to a host
  • Security groups
  • Use cases
  1. Concepts
  2. Networking in Yandex StoreDoc

Networking in Yandex StoreDoc

Written by
Yandex Cloud
Updated at September 25, 2025
  • Host name and FQDN
  • Public access to a host
  • Security groups
  • Use cases

When creating a cluster, you can:

  • Specify a network for the entire cluster.

  • Specify subnets for each host in the cluster.

  • Request public access to connect to the cluster from outside Yandex Cloud.

You do not need to specify subnets for the hosts if the availability zone of each host contains only one subnet of the cluster network.

Host name and FQDNHost name and FQDN

Yandex StoreDoc generates the name of each cluster host when creating it. This name will be the host's fully qualified domain name (FQDN). The host name and, consequently, FQDN cannot be changed.

To learn how to get host FQDN, see this guide.

You can use the FQDN to access the host within a single cloud network. For more information, see the Yandex Virtual Private Cloud documentation.

Public access to a hostPublic access to a host

Any cluster host can be accessible from outside Yandex Cloud if you requested public access when creating the host. To connect to such a host, use its FQDN.

You cannot request a public address after creating a host; however, you can replace one of the existing hosts with a new one that has a public address.

When deleting a host with a public FQDN, the assigned IP address is revoked.

Security groupsSecurity groups

Security groups follow the All traffic that is not allowed is prohibited principle. To connect to a cluster, configure security group rules. These rules allow traffic from certain ports, IP addresses, or other security groups. For example, a VM will not be able to connect to a cluster in the following cases:

  • The VM is in subnet 10.128.0.0/16, whereas the incoming traffic rules only specify subnet 10.133.0.0/24.
  • The VM is in subnet 10.133.0.0/24 but attempts to access a port not specified in the security group rules.

For information on how to configure security groups, see Configuring security groups.

Tip

When connecting to a cluster from the same cloud network, configure security groups both for the cluster and the connecting host.

Specifics of working with security groups:

  • Even if the cluster and host are in the same security group, rules allowing traffic between them must be in place to establish a connection to the cluster from that host. By default, such rules are included in the security group created together with the cloud network. They are the Self rules that allow unlimited traffic within a security group.

  • Security group settings only affect whether it will be possible to connect to the cluster. They do not affect cluster features, such as replication, sharding, and backups.

For more information, see the Virtual Private Cloud documentation.

Use casesUse cases

  • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer

Was the article helpful?

Previous
Using deprecated host classes
Next
Quotas and limits
© 2025 Direct Cursus Technology L.L.C.