Deploying a Software Ecosystem - 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
Use the Planning Worksheet for Teradata Software for AWS to prepare details of 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. From https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/Instructions, select one of the following links and follow the steps.
    Link Text Description
    Hourly (On-Demand) For short-term usage.
    1-Year or 3-Year For BYOL.
    For more information, see Teradata Software Purchase Options.
  3. From the Teradata Web site, select one of the following links to launch the appropriate Teradata ecosystem.
    License Tier Link Text
    Base, Advanced, Enterprise
    • Launch
    • Launch with IntelliSphere
    • Launch BYOL
    • Launch BYOL with IntelliSphere
    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 console, select a Region and click 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 click 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 click 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. Click Create. This process can take several minutes 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 displays 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, ensure CREATE_IN_PROGRESS displays in the Status column.
    2. After the stack is created, ensure CREATE_COMPLETE displays in the Status column.
    3. From the AWS EC2 console, click Instances in the left column and ensure 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 Teradata Database is ready and started. You do not need to run tdc-init or tdc-start.
  13. [BYOL only] If you receive licensing errors, see Licensing Issues.
  14. [BYOL only] Continuously monitor the AWS CloudWatch logs for errors, warnings, and alerts until you stop or terminate your instance. See Accessing AWS CloudWatch Logs (look for log group Teradata/DBS/stack-name and log stream telm_stack-name ).
Some Teradata Database features require manual installation or configuration. See Teradata Database Features. Some Teradata software requires additional configuration. See Configuring Teradata Software for AWS.