Configuring SecureCRT for Teradata Software for AWS Connections - Teradata Software for AWS

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

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
upc1519757374969.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud
This procedure assumes you have SecureCRT installed.
You can configure SecureCRT to allow connections to Teradata Software for AWS instances.
  1. From the AWS 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, click 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, enter 22.
  8. At Username, enter ec2-user, and click Next.
  9. At SecureFX protocol, select SFTP, and click Next.
  10. At Session name, type a name for the session, and click Finish. The New Session Wizard closes.
  11. In the Session Manager, right-click on the new session you just created, and select Properties.
  12. Under Category, select SSH2 to display the SSH2 options.
  13. At Authentication, select PublicKey, and click 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. Click OK to return to the SSH2 settings.
  17. At Key exchange, select every line that contains diffie-hellman, and click 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.