MySQL Network Communications

This topic describes MySQL internal network communication paths with other Elastic Runtime components.

These communications only apply to deployments where internal MySQL is selected as the ERT database.

Inbound Communications

The following table lists network communication paths that are inbound to MySQL.

Source VM Destination VM Port Protocol Security and Authentication
cloud_controller mysql_proxy 3306 MySQL MySQL authentication
cloud_controller_worker mysql_proxy 3306 MySQL MySQL authentication
clock_global mysql_proxy 3306 MySQL MySQL authentication
diego_database mysql_proxy 3306 MySQL MySQL authentication
mysql mysql (Galera) 4567 MySQL MySQL authentication
mysql_monitor mysql (Galera health check) 9200 MySQL Basic authentication
mysql_monitor mysql_proxy (Proxy health check) 1936 MySQL Basic authentication
mysql_proxy mysql (MySQL Server) 3306 MySQL MySQL authentication
mysql_proxy mysql (Proxy API) 8080 HTTP Basic authentication
uaa mysql_proxy 3306 MySQL MySQL authentication

Outbound Communications

The following table lists network communication paths that are outbound from MySQL.

Source VM Destination VM Port Protocol Security and Authentication
mysql_proxy (Route Registrar) nats 4222 NATS Basic authentication

Consul Communications

All MySQL Proxy instances register themselves with Consul, which enables ERT components that use Consul for service discovery to find available proxies. For more information, see Consul Network Communications.

Create a pull request or raise an issue on the source for this page in GitHub