To connect to an AWS instance, configure instances and software for your scenario.
| Scenario | Configuration |
|---|---|
| If you plan to use EC2 instances within the AWS public cloud |
|
| If you plan to use EC2 instances to connect from the AWS public cloud to an on-premises Teradata system | Configure the software using public IP addresses to connect to the on-premises Teradata system |
| Before deploying an instance using a public VLAN |
|
| Before deploying an instance using a private VLAN |
|
Instance location determines whether to use internal (private) or external (public) addresses when configuring the following software:
- Teradata Data Mover
- Teradata Ecosystem Manager
- Teradata Query Service
- Teradata Unity
- 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 at those locations.