Learn how to create DNS records for Reltio services in AWS Route 53.

1. Get VPC endpoint network interface IP addresses.
   1. Navigate to VPC and select Endpoints.
   2. Select your Reltio PrivateLink endpoint.
   3. Select the Details tab.
   4. Under Network Interfaces, note the Private IP addresses for each ENI.
   5. In the AWS Management Console, navigate to Services and select Route 53.
      You typically have one ENI per subnet or Availability Zone.

      Note: Alternatively, you can also use the following AWS CLI:

      aws ec2 describe-vpc-endpoints \
        --vpc-endpoint-ids vpce-YOUR-ENDPOINT-ID \
        --query 'VpcEndpoints[0].NetworkInterfaceIds[]' \
        --output text | xargs -I {} aws ec2 describe-network-interfaces \
        --network-interface-ids {} \
        --query 'NetworkInterfaces[].PrivateIpAddress' \
        --output text

      Example output:

      10.0.1.50
      10.0.2.50
      10.0.3.50

2. Create a private hosted zone
   1. Open the Route 53 console.
   2. In the Route 53 Dashboard, under DNS management, select Create hosted zone.
   3. In the Domain name field, enter reltio.com.
   4. From the Type dropdown, select Private hosted zone.
   5. In the VPCs to associate with the hosted zone section, select the region, VPC, and subnets configured during the VPC endpoint creation.
   6. Select Create hosted zone.
      Note: This private hosted zone affects only DNS queries originating from the selected VPC. Other environments continue to resolve using public DNS.
3. Create an A record for your Reltio environment
   1. In the reltio.com private hosted zone, select Create record.
   2. In the Record name field, enter your environment name (for example, {environment}).
   3. From the Record type dropdown, select A – IPv4 address.
   4. In the Value field, enter all VPC endpoint ENI private IP addresses, one per line.
      For example,

      10.0.1.50

      10.0.2.50

      10.0.3.50

   5. In the Routing policy field, select Simple routing.
   6. Set TTL to 300 seconds.
   7. Select Create records.
      Important: The record name must exactly match your Reltio environment hostname. If your environment URL is https://{environment}.reltio.com, create a record named {environment}.

      If you use multiple environments, create a separate A record for each environment. All records can point to the same VPC endpoint ENI IP addresses.

4. Associate Additional VPCs:
   If you need access from multiple VPCs, associate them with the same private hosted zone.

   aws route53 associate-vpc-with-hosted-zone \
     --hosted-zone-id Z1234567890ABC \
     --vpc VPCRegion=us-east-1,VPCId=vpc-ADDITIONAL-VPC-ID \
     --comment "Associate additional VPC for Reltio PrivateLink access"

   All associated VPCs must have their own VPC endpoints created, or must be able to route to the VPC where the endpoint exists.

5. Test DNS Resolution:
   1. From an EC2 instance in your VPC, verify that DNS resolution now returns private IP addresses.

      nslookup {environment}.reltio.com

      The response should return private ENI IP addresses from your VPC CIDR range.

   2. Test connectivity to confirm traffic is using PrivateLink.

      curl -v https://{environment}.reltio.com/health

   3. Confirm that the resolved IP address is private and that the request succeeds.