How to Resolve the AWS Redshift-Managed VPC Endpoint Already Exists Error

Issue

You receive one of the following error messages:

AWS Redshift-managed VPC Endpoint already exists

DNS record(s) {dnsRecord}.privatelink.postgres.database.azure.com already exist(s)

Environment

• All database connectors
• Connection method: Private networking

Resolution

Find your existing PrivateLink.

In the Fivetran dashboard

1. Log in to your Fivetran dashboard.
2. Go to Account Settings > General.
3. Select the Connection Methods tab.
4. Find the relevant PrivateLink service in the list.

REST API users

1. Use Fivetran’s List All Private Links endpoint to return both the host and id fields in order to match them.
2. Use the id you got in step 1 as private_link_id when you perform these REST API actions:
   • Create a connection
   • Update a connection
   • Create a destination
   • Update a destination

Terraform provider for Fivetran users

1. Use the fivetran_private_links data source to return both the host and id fields.
2. Use the id you got in step 1 as private_link_id when you perform the following Terraform provider for Fivetran actions:
   • Create or update with fivetran_connector resource.
   • Create or update with fivetran_destination resource.