Correcting Instance Connections - Aster Analytics on AWS

Teradata Aster Analytics on AWS Getting Started Guide

Product
Aster Analytics on AWS
Release Number
1.5
Published
October 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
gkp1499384139306.ditamap
dita:ditavalPath
AWS.ditaval
dita:id
tsu1471542219751
lifecycle
previous
Product Category
Cloud
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.
Issue Steps
If you cannot connect to an instance, but have successfully connected before
  1. From the AWS Console, click EC2.
  2. Click Instances.
  3. If the public IP address changed from the previous setting, then create a new instance using elastic IP addresses.

The public IP address changes every time you restart the instance.

If you were never able to successfully connect to an instance
  1. From the AWS Console, click EC2.
  2. Click Instances.
  3. Click the name of the security group where the instance resides, and then click the Security Groups tab.
  4. Click the name of the security group that the instance belongs to.
  5. Click the Inbound tab and then click Edit.
  6. If you don't have inbound rules for port ranges 22 and 1025, click Add rule and use the information in the following table to create two new inbound rules.
  7. Click Save.
  • Type:
  • Protocol:
  • Port Range:
  • Source:
  • SSH
  • TCP
  • 22
  • MyIP
  • Type:
  • Protocol:
  • Port Range:
  • Source:
  • Custom TCP Rule
  • TCP
  • 10 25
  • MyIP