Network and clusters in Managed Service for MySQL
When creating a MySQL 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 Nebius AI.
You can create a cluster without specifying any subnets for the hosts if the availability zone selected for each host contains exactly one subnet of the cluster network.
Host name and FQDN
Managed Service for MySQL 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.
You can use the FQDN to access the host within a single cloud network. For more information, see the Virtual Private Cloud documentation.
Public access to a host
Any cluster host can be accessible from outside Nebius AI if you requested public access when creating or editing a host. To connect to such kind of a host, use its FQDN.
When deleting a host with a public FQDN, the assigned IP address is revoked.
Connecting to cluster hosts
You can connect to Managed Service for MySQL cluster hosts:
-
Over the internet, if you configured public access for the appropriate host. You can only connect to such hosts over an SSL connection.
-
From Nebius AI virtual machines located in the same cloud network. If there is no public access to a host, using SSL for connections from such virtual machines is not required.
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.