Planning worksheet | Teradata Vantage on AWS (DIY) - 2.2 - Planning Worksheet for Vantage on AWS (DIY) - 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)
Parameter names in the ecosystem templates are shown in bold.
Category Item / Parameter Description Your Information
Account Planning
  AWS Account See Amazon User Guide for Linux Instances .  
IAM Users/Groups IAM users must have permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles.  
Region The AWS region where you deploy your stack.  
AWS Service Limits Increase service limits, particularly for EBS, EC2 instances, and VPC elastic IP addresses, as well as increase instance limits to support NFR.

See AWS Service Limits.

 
Teradata Deployment Planning
  Teradata Software See Supported Teradata Software on AWS.  
Software Packaging Options Choose the software bundle or individual software components. See Teradata Software Purchase Options.  
Software Purchasing Methods Purchase from AWS on an hourly basis or contact Teradata for an annual license. See Teradata Software Purchase Options.  
Software Deployment Methods Learn about deploying Vantage simultaneously with other Teradata software products (recommended method). See Deploying Teradata Ecosystem Using AWS CloudFormation.

Learn about deploying Teradata products one at a time. See Methods for Deploying Teradata Components Separately.

 
Subscribing Whether you use an annual or an hourly subscription, you must subscribe to the software on AWS before deploying it. See Subscribing to Teradata Software.

See https://aws.amazon.com/marketplace/help.

 
Vantage License Tier Developer, Base, Advanced, or Enterprise.

See Teradata Vantage License Tiers.

 
Teradata Support Account

[Base, Advanced, Enterprise only*]

Register for support at https://www.teradata.com/Cloud/AWS/Do-it-Yourself/Support-Registration.

Existing Teradata customers with a site ID must obtain a new site ID, as you cannot use your existing site ID for Vantage on AWS (DIY).

After completing registration, you will receive email containing your Master Customer Record and site ID. Once you receive it, login to support.teradata.com and register with your preferred email and Customer Master Record provided. This will provide access to Teradata Support portal.

 
Vantage Ecosystem Test and Development, Minimum Production, or Full Production.

See https://www.teradata.com/Cloud/AWS/Do-it-Yourself.

 
Public vs. private IP/DNS addresses See Connection Configurations.  
Node Failure Recovery Before deploying an instance, make sure there is at least one free IP address in the subnet in case a node failure occurs. Assign EC2-VPC elastic IP addresses to the public IP addresses of each instance to reconnect without having to update the Teradata COP entry IP addresses if a node fails.

See Node Failure Recovery.

 
Stack Name Must be unique to the deployment region.  
Vantage Version 2.2.x  
System Name    
System Nickname Used to monitor Vantage instances in Teradata Viewpoint.  
DBC Password New Vantage password.  
Number of Nodes Maximum supported number depends on the license tier.  
Number of Hot Standby Nodes (HSN) Maximum supported number depends on the license tier. Do not exceed the number of Vantage nodes. See Hot Standby Nodes.  
Instance and Storage Type Storage size is per node. For an MPP system, Teradata requires supported r5 instance types (EBS storage) for Advanced and Enterprise tiers.

See Vantage Instance Types and Storage Considerations.

 
Scale Out/In

[Base, Advanced, Enterprise only*]

  • Select None to disable this feature (default). If you select None, you can still scale out after deployment.
  • Select Scale-Out-Ready to automatically allocate extra IP addresses from the subnet.
  • Select Scale-Out-2x to deploy the system in a 2x scaled out state. This option deploys a half of the EBS volumes per instance, enabling you to scale in the system after deploying. If choosing this option, the Number of Nodes parameter must be in multiples of 2.
  • Select Scale-Out-4x to deploy the system in a 4x scaled out state. This option deploys a quarter of the EBS volumes per instance, enabling you to scale in the system after deploying. If choosing this option, the Number of Nodes parameter must be in multiples of 4.
See Scaling Vantage Out or In.
 
Data Storage Supported only on r5 instance types (EBS storage). 5 to 72 TB per node.  
EBS Encryption

[Base, Advanced, Enterprise only*]

Supported only on r5 instance types (EBS storage).

See Encryption.

 
Root Disk Encryption

[Base, Advanced, Enterprise only*]

Supported only on r5 instance types (EBS storage).

See Encryption.

 
Japanese Support Enable to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes.  
Elastic IPs Enable to allocate an elastic IP address to each node.

Vantage on AWS (DIY) uses EC2-VPC elastic IP addresses. Although you can use EC2-VPC elastic IP addresses for all Teradata ecosystems, we strongly recommend you use them for Minimum Production and Full Production Teradata ecosystems.

 
Enable Temporal Select yes to enable, no to disable.  
Enable Secure Zones Select yes to enable, no to disable.  
Enable Row-Level Security Select yes to enable, no to disable.  
Enable Teradata Intelligent Memory

[Advanced, Enterprise only*]

To enable, specify the hot cylinder cache as a percentage from 1 to 80 of the FSG cache. To disable, change the setting to 0.

See the ctl utility in Teradata Vantage™ - Database Utilities , B035-1102 and Teradata® Intelligent Memory Orange Book, 541-0009920. To find an Orange Book, go to https://support.teradata.com, log in, and search for the book title.

 
Mainframe Connectivity
  • Select 1 or 2 as the number of parsing engines per node you want for mainframe connectivity.
  • Select 0 if you do not want to connect to a mainframe.
 
Date and Time NTP Servers [Optional] Leave blank to use the default Amazon Time Sync Service local IP address. If you must use different NTP servers, enter the IP addresses separated by commas.  
System Timezone [Optional] Default: time zone of the AWS region. Can be changed to the operating system time zone of the Vantage system. See Time Zone Considerations and AWS Regions.

Data Mover, DSC, Viewpoint, and Query Service default to the same time zone set for the Vantage system.

 
VPC/Network VPC Create an AWS virtual private cloud. Do not use the default Amazon VPC.

Use subnets if you want to deploy Vantage MPP instances. For subnets, you must enable auto-assignment of public IP addresses.

When you secure your VPC, make sure the Vantage instances can still access the AWS service endpoints they require. See AWS Service Endpoints.

 
Vantage Subnet Select a subnet to use for the Vantage system.

Ensure the subnet you select has a sufficient number of IPs available. The Vantage MPP instances require two IPs per node and all AWS subnets have 5 IPs reserved for internal use. If you plan on enabling scale-out with your system, be sure to allocate enough IPs per MPP instance for a fully scaled-out system.

See VPC and Subnet Sizing in the Amazon Virtual Private Cloud User Guide.

Check that the subnet you choose has enough available IPs. From the AWS Web Console, under Networking, select VPC. Under Resources, select Subnets. Check the Available IPs column for that specific subnet.

 
Ecosystem Subnet Create one or more subnets, which require a sufficient number of available IPs:
  • MPP instances require two IPs per node. Be sure to factor in up to four times this number if deploying in a scale-in/scale-out capable state.
  • Teradata ecosystem products require additional IPs in this subnet.
  • AWS subnets reserve five IPs for internal use.

See the Amazon Virtual Private Cloud User Guide.

 
Database Placement Group Create an AWS placement group.  
DSC Placement Group [Optional] Either use the same placement group as the Vantage system or create a new one.  
Data Mover Placement Group [Optional] Either use the same placement group as the Vantage system or create a new one.  
Security Group Remote Access From Create one or more AWS security groups and configure appropriate ports. To configure ports, see Security Groups for Teradata Vantage and Security Groups for Other Teradata Applications.

In this field, enter the CIDR block to lock down SSH and enable access to nodes.

 
Proxy Server Configuration Proxy Server Configuration [Optional]Authenticated Proxy Server configurations to instances in specified VPC for internet connectivity. Also, make sure Proxy Server is deployed and configured properly in the same VPC.

Ex.: http://<username>:<password>@<proxy_server_private_ip>:<proxy_server_port>

Note: Vantage DIY CFT’s doesn’t include deployment & configuration of proxy server.

For more details, see Proxy Server section.

 
Capacity Reservation Capacity Reservation [Optional] On-Demand Capacity Reservations enable you to reserve compute capacity for your Amazon EC2 instances in a specific Availability Zone for any duration.  
Key Pair AWS Key Pair Use to SSH into instances. If a key pair was created in a region, it cannot be used in another region. To use a key pair in all regions, create it using a third-party tool and import the public key to Amazon EC2.  
Teradata Server Management Number of CMICs Server Management instances. Minimum of three for high availability.  
Admin Password    
Site ID

[Base, Advanced, Enterprise only*]

String that identifies this Teradata deployment for Teradata Services (AMZTDB followed by up to 9 numbers). Obtained by registering for support. If you do not have a site ID, you can continue without it, and add it later.  
Teradata DSC

[Minimum and Full Production ecosystems only]

Instance Type See Supporting Software Instance Types.  
Teradata Data Mover

[Full Production ecosystem only]

Instance Type See Supporting Software Instance Types.  
Additional Agents Number of agents (nodes) to deploy in addition to the master (0 to 3).  
DATAMOVER Password Password used to access the internal DATAMOVER repository.  
DBC Password New Vantage password.  
Teradata QueryGrid Manager   Requires Teradata Viewpoint. For software dependencies, see http://knowledge.teradata.com/KCS/id/KCS001621  
Options Tags [Optional] Up to ten unique key-value pairs for resources in your stack.  
Advanced [Optional] Additional options for your stack, such as notifications and a stack policy.  
Custom Tags Custom Tags [Optional] You can specify up to 25 custom tags to be added to each instance of the deployment.

Enter as a list of comma and (optional) whitespace delineated key:value pairs. For example: cloud:aws, dbs:teradata.