Set Up a Service Endpoint for AWS PrivateLink | Teradata Vantage on AWS - Setting Up a Service Endpoint for AWS PrivateLink - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS Getting Started Guide

Teradata Vantage on AWS
Release Number
June 2020
English (United States)
Last Update
Product Category
  • Confirm with your AWS administrator that you have the necessary IAM permissions.
  • A program to test port connectivity.
If you have chosen AWS PrivateLink for network connectivity, you must create a service endpoint after Teradata has authorized your AWS account. Endpoints allow direct, secure network connectivity between AWS VPCs without traversing the public Internet.
AWS PrivateLink is the default network connectivity option. Contact Teradata if you prefer to use AWS Direct Connect or VPN.
  1. Log in to both the target AWS account and the Amazon VPC Management Console at
  2. From the VPC Dashboard, click Security Groups.
  3. Update the database security group to allow the inbound ports for Advanced SQL Engine (port 1025) and Viewpoint (ports 80 and 443) from the VPC CIDR.
  4. From the VPC Dashboard, click Endpoints > Create Endpoint.
  5. In Service Category, select Find service by name.
  6. In Service Name, enter the PrivateLink service endpoint value for your site.
    You can copy this string from Network Settings in the Management Console or from the email you received from Teradata.
  7. Click Verify.
    If the PrivateLink service endpoint is active, the message Service name found appears.
  8. Select the VPC, subnet, and security group you will use to connect to Advanced SQL Engine and Viewpoint, then click Create Endpoint.
    Status: available
    The endpoint was successfully created.
    Status: pending
    Report the status by creating an incident in the Management Console.
  9. After the status shows available, use Telnet or an alternative program to test connectivity between your VPC and Vantage site for each port number (1025, 80, 443).