Methods to Deploy Teradata Components Separately | Teradata Vantage on AWS (DIY) - 2.2 - Methods for Deploying Teradata Components Separately - 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)

If you are deploying Vantage with other Teradata software solutions on AWS, Teradata recommends deploying a Teradata ecosystem using AWS CloudFormation. You can also deploy some products separately using AWS CloudFormation, Manual Launch, or 1-Click Launch methods described here. Deploy Vantage before deploying other Teradata components separately.

Supported deployment methods vary by product.

Deployment Method Description
AWS CloudFormation Templates used to deploy the following software and automate some configuration:
  • Vantage using a choice of templates
  • Teradata Data Mover agent or cluster using a single template
Manual Full control of all settings provided before deploying Teradata product instances based on AMIs; more time-consuming than AWS CloudFormation deployment due to post-deployment configuration requirements
  • Involves additional configuration steps after instance deployment
  • Allows deployment of multiple AWS instances of a single Teradata product from one AMI based on the same configuration settings of your choosing
  • Provides for modification of all settings, including storage type and capacity
  • Automatically sets EBS root device volume for deletion on instance termination; requires manual setting of the attached EBS storage volumes for deletion
  • Provides for deploying instances in placement groups and availability zones other than the default; Vantage on AWS (DIY) software benefits particularly from inclusion in placement groups
  • Requires some knowledge in setting up an instance
1-Click Easiest and fastest deployment of a single instance of Teradata products, requiring minimum configuration
  • Allows deployment of a single AWS instance from one AMI with predefined settings recommended by Teradata
  • Uses only the predefined Teradata instance types
  • Presents difficulty modifying some settings after the instance is deployed
  • Cannot modify the predefined storage size and type
  • Automatically sets EBS storage volumes for deletion on instance termination
  • Does not provide for deploying of instances in Placement Groups and Availability Zones other than the default