Connection Considerations

If you use EC2 instances within the AWS public cloud, configure these instances to reside in the same VPC. When configuring the software, use private IP addresses to connect to these instances.

If you use EC2 instances to connect from the AWS public cloud to an on-premises Teradata system, use public IP addresses to connect to the on-premises Teradata system when configuring the software.

You need only public IP addresses if you deploy an instance using a public VLAN. If you deploy an instance using a private VLAN, the instances have private IPs and require a VPC connection for SSH access.

When deploying an instance, make a note of the IP and DNS addresses of both the Teradata Database instance and the additional software. Use this information when configuring the additional software instances. Instance location determines whether to use internal or external addresses when configuring the following software:
  • Teradata Data Mover
  • Teradata Ecosystem Manager
  • Teradata REST Services
  • Teradata Viewpoint

For example, use Teradata Database private IP addresses in Data Mover job XML and Data Mover portlets if all AWS instances reside in the same VPC. In Data Mover portlets, use the private IP address of the Data Mover instance to connect to a Teradata Database system. If source and target systems reside outside AWS, such as an on-premises system, use the public IP addresses instead.

Only the software listed above can connect to an on-premises system if you opened the appropriate inbound ports in the corporate firewall on those premises.

results matching ""

    No results matching ""