Correcting Instance Connections | Teradata Vantage on AWS (DIY) - 2.2 - Correcting Instance Connections - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.2
Release Date
May 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2800-041K
Language
English (United States)
If you cannot connect to an instance, but have successfully connected before or if you were never able to successfully connect to an instance, try one of the following options to correct the issue.
  • If you cannot connect to an instance, but have successfully connected before, follow these steps:
    1. From the AWS Console, select EC2.
    2. Select Instances.
    3. If the public IP address changed from the previous setting, then check the current public IP address and use it to connect to the instance.
      The public IP address changes every time you restart the instance. If you do not want the public IP address to change, assign elastic IP addresses to the instances.
  • If you were never able to connect to an instance, follow these steps:
    1. From the AWS Console, select EC2.
    2. Select Instances.
    3. Select the name of the security group where the instance resides, then select the Security Groups tab.
    4. Select the name of the security group that the instance belongs to.
    5. Select the Inbound tab, then select Edit.
    6. If you don't have inbound rules for port ranges 22 and 1025, select Add rule and use the information in the following table to create two new inbound rules.
    7. Select Save.
    • Type:
    • Protocol:
    • Port Range:
    • Source:
    • SSH
    • TCP
    • 22
    • MyIP
    • Type:
    • Protocol:
    • Port Range:
    • Source:
    • Custom TCP Rule
    • TCP
    • 1025
    • MyIP