6 PrivateLink

PrivateLink for HeatWave on AWS allows you to configure private network paths between your MySQL DB System and your AWS account. You can use PrivateLink to ensure that all traffic to or from your DB System stays on a private network connection and does not transit the public internet.

At a high level, AWS PrivateLink works by establishing network components within two AWS accounts—your AWS Account and the HeatWave on AWS account. Within one account, an Endpoint service is created, and in the other account, a VPC endpoint is created to link to the Endpoint service through a uniquely identified connection. The architecture of PrivateLink and the involved components are explained in AWS PrivateLink concepts.

You can use a PrivateLink to connect your applications to your DB System, or to allow your DB System to connect to services hosted in your AWS account. HeatWave on AWS supports two types of PrivateLinks:

• Query PrivateLinks: For applications running in your AWS account to access a HeatWave on AWS DB System over a private connection in order to manage it or to run queries. See Deploying a Query PrivateLink for details, and see Troubleshooting a Query PrivateLink for help on common issues.
• Egress PrivateLinks: For your DB System to access an external service running in your AWS account—for example, to support Inbound Replication from a MySQL source server. See Deploying an Egress PrivateLink for details, and see Troubleshooting an Egress PrivateLink for help on common issues.

This chapter contains the following topics on PrivateLinks.

• Deploying a Query PrivateLink
  
• Deploying an Egress PrivateLink
  
• Managing a PrivateLink
  
• PrivateLink Limitations