Configure SecureCRT Connections | Teradata VantageCloud Enterprise on AWS (DIY) - Configuring SecureCRT Connections for Teradata Vantage on AWS (DIY) - Teradata® VantageCloud Enterprise on AWS

VantageCloud Enterprise on AWS (DIY) Installation and Administration Guide - 2.4

Deployment
VantageCloud
Edition
Enterprise
Product
Teradata® VantageCloud Enterprise on AWS
Release Number
2.4
Published
June 2023
Language
English (United States)
Last Update
2023-06-30
dita:mapPath
kma1662437965174.ditamap
dita:ditavalPath
nat1649317391363.ditaval
dita:id
B035-2800
Product Category
Cloud
PrerequisiteThis procedure assumes you have SecureCRT installed.
You can configure SecureCRT to allow connections to Vantage on AWS (DIY) instances.
  1. From the AWS Management Console, select EC2 > Instances.
  2. Record the Public IP of the instance to which you want to connect.
  3. Run SecureCRT.
  4. On the Session Manager, select "" to start a new session.
    You can also press Alt+N.
    The New Session Wizard opens.
  5. At SecureCRT protocol, select SSH2, and click Next.
  6. At Hostname, enter the public IP address you previously recorded.
  7. At Port, type 22.
  8. At Username, type ec2-user, then select Next.
  9. At SecureFX protocol, select SFTP, then select Next.
  10. At Session name, enter a name for the session, then select Finish.
    The New Session Wizard closes.
  11. In the Session Manager, right-click on the new session you just created, then select Properties.
  12. Under Category, select SSH2 to view the SSH2 options.
  13. At Authentication, select PublicKey, then select Properties.
    The Public Key Properties window opens.
  14. Select Use global public key setting.
  15. Select Use identity or certificate file, and browse to the Amazon key pair *.pem file that was created when you deployed the instance.
  16. Select OK to return to the SSH2 settings.
  17. At Key exchange, select every line that contains diffie-hellman,then select OK.
    Diffie-Hellman is a method of securely exchanging keys over a public channel.
  18. Back on the Session Manager, double-click your session to connect to your instance.