6.3.4 Updating Egress Endpoints for a Egress PrivateLink

You need to update the Egress Endpoints if the service in your account is listening on a different port, or you want to make it accessible to your DB System with a different DNS hostname. You may also wish to connect a different DB System. Use the HeatWave Console to update the Egress Endpoints of a Egress PrivateLink. You can also add or remove an endpoint.

This task requires the following:

• A PrivateLink in the Active state.
• Knowledge of the new hostname or port in your AWS account, or the new DB System ID for which you want to allow connectivity.

Do the following to update, remove, or add Egress Endpoints of a PrivateLink:

1. In the HeatWave Console, select the Resources tab.
2. On the PrivateLinks tab, in the list of PrivateLinks, find the Egress PrivateLink for which you want to update the Egress endpoints, and do one of the following:
   • Click the row of the Egress PrivateLink to highlight it, and under Actions, click Update Egress Endpoints.
   • Click the name of the Egress PrivateLink to open the PrivateLink Details page, and click Update Egress Endpoints.
3. In the Configure PrivateLink section, do one of the following:
   • To update the DNS hostname or port on which the PrivateLink is accessible, or the HeatWave on AWS DB System connected to this PrivateLink:
     • Under Source, update the following fields:
       • Hostname: Update the DNS hostname for which traffic will be routed over the Egress PrivateLink. For inbound replication, this is only required if you want to support TLS certificate identity verification; leave blank otherwise.
       • Port: Update the port on which the service in your account is listening for traffic (for inbound replication, it is the port of the source database).
     • Under Target DB System: Update the DB System connected to this Egress PrivateLink.
   • To remove an endpoint: Click the X beside it.
   • To add an endpoint: Click Add Egress Endpoint, then fill in the information.

     Note:

     Currently, only a single egress endpoint is supported for each DB System. If you would like to configure more egress endpoints, create a separate egress PrivateLink for each of the endpoints.
4. Click Save.

Note:

Removing and adding Egress Endpoints must be done in two separate update requests..

Parent topic: Managing a PrivateLink