Teradata QueryGrid between the Public Cloud and On-Premises

When configuring Teradata QueryGrid for connections between a Teradata Database instance on AWS and an on-premises Teradata Database, Teradata Aster, or Hadoop system, define network settings in the AWS VPC Network ACL as follows:

The following terms are used in the table below:
  • Local system as the system on which the user logs on.
  • Remote system as the system that the user accesses using the foreign server grammar.
Software Direction Ports Description
Teradata Database instance (VPC) Outbound

Allows connection from the Teradata Database instance in the network to the on-premises Teradata Database, Teradata Aster, or Hadoop system.

Teradata Database instance (VPC) Inbound

Allows connection from the on-premises Teradata Database, Teradata Aster, or Hadoop system to the Teradata Database instance in the network.

Teradata Database instance (VPC) Outbound Allows connection to a remote on-premises Teradata Database, Teradata Aster, or Hadoop system.
Teradata Database instance (VPC) Inbound PTL Listen:
  • 5000 (Teradata Database)
  • 5001 (Teradata Aster)
  • 5002 (Hadoop)

Allows connection and data transfer from a remote on-premises Teradata Database or Hadoop system.

On-premises Hadoop system Inbound
  • 8080
  • 21337
Allows communication with the Teradata Distribution for Presto on a remote on-premises Hadoop system.
Note:
These ports must also be opened on all on-premises Hadoop nodes running the Teradata Distribution for Presto.
On-premises Teradata Aster Inbound
  • 8080
  • 21337
Allows communication with the remote on-premises Teradata Aster system.
Note:
The ports must also be opened on all on-premises Teradata Aster nodes.

Finally, define the foreign server object using the public IP address of the Teradata Database instance on AWS and the IP address of the on-premises Teradata Database, Teradata Aster queen node, or Hadoop system.

results matching ""

    No results matching ""