Deploy Other Teradata SW With AWS CloudFormation | Teradata Vantage on AWS (DIY) - 2.2 - Deploying Other Teradata Software Using AWS CloudFormation - Teradata Vantage on AWS

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

Teradata Vantage on AWS
Release Number
Release Date
May 2021
Content Type
Publication ID
English (United States)
PrerequisiteUse the Planning Worksheet for Vantage on AWS (DIY) to prepare details of the deployment.

Deploy Vantage before deploying other Teradata software.

Use this procedure to deploy Teradata Data Mover.
  • Data Mover: If you are deploying Teradata components separately on AWS, you can use AWS CloudFormation to deploy a single Data Mover agent or a cluster of up to 4 agents. In general, the greater the number of agents, the better the throughput for larger Vantage systems and high Data Mover workload.
  1. If you have not already subscribed to the software you want to deploy, do so now.
  2. Log in to AWS Marketplace.
  3. From your account menu in the upper-right corner, select Your Marketplace Software.
  4. Select Launch More Software under the subscription name of the software you want to deploy.
  5. Select an appropriate value under each of the following categories:
    Category Action
    Software Pricing Select your subscription term.
    Software Version Select the release version from which to deploy the instance.
    Region Select a region.
    Deployment Options Select one of the following:
    • Teradata Data Mover MPP system with EBS storage
    • Server Management in VPC for multi-app monitoring
  6. Under Launch, select Launch with CloudFormation Console.
    The template URL is automatically specified under Specify an Amazon S3 template URL.
  7. Select Next.
  8. Under Specify Details, verify the stack name is unique to your region.
  9. Under Parameters, specify the values for the appropriate software, then select Next.
  10. [Optional] Under Tags, specify up to 10 unique key-value pairs for resources in your stack so you can search later for the resources you deployed.
  11. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy.
    To troubleshoot a stack failure, change the Rollback on failure setting to No. The default setting is Yes.
  12. Select Next.
  13. Review the information, then select the I acknowledge check box at the bottom.
  14. Select Create to create the stack.
    This process can take up to 45 minutes, 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 CREATE_COMPLETE appears in the Status column or you receive a failure notification.
  15. [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.