PDF (US Ltr)
- 1.0Mb
6.2 Deploying an Egress PrivateLink
Overview
Certain features like inbound replication require egress connections from your HeatWave on AWS DB System to your AWS account. To allow your DB System to connect to an endpoint in your AWS account using a private network path, you first configure your account’s network infrastructure and then create an Egress PrivateLink inside HeatWave on AWS. During the creation of the Egress PrivateLink, you configure a set of Egress Endpoints that define the network parameters your DB System will use to connect to your AWS account over the Egress PrivateLink.
Figure 6-2 shows the components and steps required to configure your account’s network infrastructure and create an Egress PrivateLink. It illustrates the use case of configuring inbound replication from a source in your AWS account to a HeatWave DB System using a replication Channel over an Egress PrivateLink.
Figure 6-2 Components to Configure for Inbound Replication Using an Egress PrivateLink
Steps for Deploying an Egress PrivateLink for Inbound Replication
Follow these steps to create the inbound replication scenario as illustrated in Figure 6-2.
- Configure your replication source by:
- Following the instructions given in Source Configuration
- Creating a Replication User On a Source Server
- Create the requisite networking resources in your AWS account by following the instructions given in Configuring the Network Infrastructure for an Egress PrivateLink.
- Create an Egress PrivateLink on your DB System by following the instructions given in Creating an Egress PrivateLink.
- Create the Replication Channel in the following the instructions in Creating a Channel, selecting Egress PrivateLink for Channel over PrivateLink.
The following sections explain some of the above-mentioned steps in details and provide additional information on the deployment of Egress PrivateLinks.