Set Up the Mercury VPC Endpoint
[!NOTE] This can be done only once per AWS account, regardless of whether it is initiated from this application, another application, or a CLI tool. The registration application simply requires a working communication channel to Mercury.
Prerequisites
- The AWS account needs to have a VPC and respective routing tables (set up by the CDX team).
- The AWS account needs to have a proper network setup:
- Documentation about network setup: [https://docs.statista.dev/pit-shared/remix-tools/cdk/network]
- Use the CDK-Remix-Setup CLI tool: [https://github.com/PIT-Shared/cdk-remix-setup]
- The infrastructure the application is running on needs to be deployed into the VPC.
Steps
The CDK-Remix-Setup CLI tool will guide you through the 3-step process of creating the VPC endpoint:
Step 1: Create the VPC endpoint, but with Secure DNS disabled. Step 2: Let the Mercury team approve the VPC endpoint on their end. Step 3: Enable Secure DNS.
In the AWS account, under VPC -> Endpoints, the created VPC endpoint should
be visible.
Related
- Service configuration:
MercuryService(app/services/mercury/mercury.server.ts) - Inspect Mercury events in Argus [./setup-mercury-vpc-endpoint.md]
- Mercury Connection Documentation [https://github.com/PIT-Tracking-Analytics/tracking-data-ingestion/blob/main/PRIVATELINK_SETUP_GUIDE.md]