This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Options
Topics on this page:
MariaDB SkySQL supports VPC Peering as an option:
This feature is not enabled by default. By default, network traffic to MariaDB SkySQL traverses the public internet.
When enabled, VPC Peering connects your Google Cloud Platform (GCP) Virtual Private Cloud (VPC) network to MariaDB SkySQL with connectivity over Google's network.
VPC Peering improves network latency, improves security, and reduces egress bandwidth costs when communicating between servers in separate GCP regions.
VPC Peering is available to Power Tier customers.
For AWS, see AWS PrivateLink.
Single Node Analytics
Single Node Transactions
Enable VPC Peering
VPC Peering can't be configured if you have any existing SkySQL services deployed in the GCP region which will be peered. Contact us for assistance.
Gather the required information, then contact SkySQL Support to request VPC Peering configuration:
Identify two unused
/16subnets which do not collide with addressing used in your existing GCP environment. See GCP subnetting instructions for additional guidance.
Identify your existing GCP Project ID.
Identify the name of your GCP VPC that you would like peered.
Identify the SkySQL-supported GCP region which will be used for your SkySQL database services.
Determine the level of network security you would like between SkySQL and your existing GCP environment:
Allow ALL private IP addresses (suggested), or
Deny ALL and provide specific IP addresses to allow.
Launch a SkySQL service. The service must be launched with GCP selected as cloud provider, and the previously-selected GCP region.
Connect over VPC Peering
VPC Peering changes the way you connect to SkySQL services, allowing connections which do not transit the public internet. Configurations are customer-specific and cloud-specific. If VPC Peering is enabled, please refer to the connection instructions provided by MariaDB Support.