Deploy a Teradata SW Ecosystem | Teradata Vantage on AWS (DIY) - 2.2 - Deploying a Teradata Software Ecosystem - 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)
PrerequisiteUse the Planning Worksheet for Vantage on AWS (DIY) to prepare the deployment.
You can deploy multiple Teradata software products simultaneously, collectively known as a software ecosystem. Each software ecosystem option links to an AWS CloudFormation template hosted on Amazon S3.
You cannot deploy a Teradata ecosystem directly from the AWS Marketplace. An ecosystem must be launched from the Teradata Web site.

This procedure provides options to encrypt your data volumes and the root disk using a default CMK.

  1. Subscribe to Teradata software.
  2. In the Deployment Instructions section at https://www.teradata.com/Cloud/AWS/Do-it-Yourself, select one of the following links and follow the steps.
    Link Text Description
    Hourly (On-Demand) For short-term usage.
    Annual For longer term usage.
  3. Select one of the following links to launch the appropriate Teradata ecosystem.
    License Tier Link Text
    Base, Advanced, Enterprise
    • Launch
    Developer Launch
    The Select Template page appears and the template URL is automatically specified under Choose a template.
  4. In the upper-right corner of the console, select a Region, then select Next.
  5. Verify the stack name that is automatically specified is unique to your region.
  6. Under Parameters, specify the values you chose in the planning worksheet, then select Next.
  7. [Optional] Under Tags, specify up to 10 unique key-value pairs for resources in your stack.
  8. [Optional] Under Advanced, set additional options for your stack, then select Next.
    If you want the ability to troubleshoot failures, change the Rollback on failure setting to Yes.
  9. On the Review page, select the I acknowledge check box.
  10. Select Create.
    This process may take up to an hour, depending on your configuration.
    Trying to SSH into the instance may cause the stack creation to fail. Do not try to SSH into the instance until either CREATE_COMPLETE appears in the Status column or you receive a failure notification.
  11. [Optional] To monitor the stack creation progress, do the following:
    1. From the AWS CloudFormation console, make sure CREATE_IN_PROGRESS appears in the Status column.
    2. After the stack is created, make sure CREATE_COMPLETE appears in the Status column.
    3. From the AWS EC2 console, select Instances in the left column and make sure your instances are listed under the Name column.
      The name appears as the stack name followed by the node name.
  12. [Optional] To SSH into the system with the public IP/DNS of any of the nodes, type the following command:
    ssh -i private-key-file.pem ec2-user@instance-DNS-name-or-IP
    Vantage is ready and started. You do not need to run tdc-init or tdc-start.
  13. [Optional] To SSH into the system with the Proxy Server configuration using Private IP of any of the nodes, type the following command
    ssh -o ProxyCommand="ssh -i private-key-file.pem -W %h:%p ec2-user@proxy-server-public-IP" -i private-key-file.pem ec2-user@instance-private-IP
PostrequisiteSome Vantage features require manual installation or configuration. See Vantage Features. Some Teradata software requires additional configuration. See Configuring Teradata Software on AWS.