Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for MySQL®
  • Getting started
    • Resource relationships
    • High availability clusters
    • Networking in Managed Service for MySQL
    • Quotas and limits
    • Storage in Managed Service for MySQL®
    • Backups
    • Load balancer for hosts
    • Replication
    • Maintenance
    • User permissions
    • MySQL settings
    • SQL command limits
    • Comparing MySQL® 5.7 and 8.0
    • MySQL® versioning policy
  • Access management
  • Inspections and recommendations
  • 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
  • Connecting to cluster hosts
  • Security groups
  • Use cases
  1. Concepts
  2. Networking in Managed Service for MySQL

Network and clusters in Managed Service for MySQL®

Written by
Yandex Cloud
Updated at September 23, 2026
View in Markdown
  • Host name and FQDN
  • Public access to a host
  • Connecting to cluster hosts
  • Security groups
  • Use cases

When creating a MySQL® cluster, you can:

  • Specify a network for the cluster.
  • Specify subnets for each host in the cluster.
  • Request public access to connect to the cluster from outside Yandex Cloud.

You can create a cluster without specifying any subnets for hosts if the availability zone selected for each host contains exactly one cluster network subnet.

Host name and FQDNHost name and FQDN

Managed Service for MySQL® generates a name for each cluster host when creating it. This name will be the host's fully qualified domain name (FQDN). You cannot change the host name and, consequently, FQDN.

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

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

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 or editing a host. To connect to such a host, use its FQDN.

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

Connecting to cluster hostsConnecting to cluster hosts

You can connect to Managed Service for MySQL® cluster hosts:

  • Via the internet, if you configured public access for the host. You can connect over the internet in the following ways:

    • Use an SSL connection.
    • Use IAM authentication.
  • From Yandex Cloud virtual machines located in the same cloud network. For hosts without public access, SSL is not required to connect to them from these virtual machines.

The maximum number of connections is defined by the max_connections setting, which depends on the host class.

In addition to host names, to connect to a cluster, you can use special FQDNs that point to the current master host and the replica that is least lagging from it.

Security groupsSecurity groups

Security groups follow the rule that all traffic is denied unless you explicitly allow it. 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 the 10.128.0.0/16 subnet, whereas the inbound rules only allow 10.133.0.0/24.
  • The VM is in the 10.133.0.0/24 subnet but attempts to access a port not exposed 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 it resides in, configure security groups not just for the cluster but also for the host you are connecting from.

Features of using security groups:

  • Even if the cluster and host share the same security group, you still need rules allowing traffic between them to be able to connect to the cluster from the host. By default, such rules are included in the security group created along with the cloud network. These are the Self rules that allow unlimited traffic within the security group.

  • Security group settings only determine whether connecting to the cluster is possible. They do not affect cluster features, such as replication, sharding, and backups.

For more information, see this Virtual Private Cloud article.

Use casesUse cases

  • Migrating a database from a third-party MySQL® cluster
  • Exporting a database to Yandex Data Processing
  • Syncing data from a third-party MySQL® cluster to Yandex Managed Service for MySQL® using Yandex Data Transfer
  • Creating an online store on 1C-Bitrix: Site Management
  • Building a 1C-Bitrix website
  • Creating an OpenCart online store

Was the article helpful?

Previous
High availability clusters
Next
Quotas and limits
© 2026 Direct Cursus Technology L.L.C.