Planning Worksheet for a Teradata Software Ecosystem

More information:

Teradata® Software for AWS Installation and Administration Guide
Amazon User Guide for Linux Instances
Amazon Virtual Private Cloud User Guide
AWS CloudFormation Documentation
https://aws.amazon.com/marketplace/help
https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/Instructions

Parameter names in the ecosystem templates are shown in bold.

Category	Item/Parameter	Description
Account Planning
	AWS Account	See Amazon User Guide for Linux Instances .
	IAM Users/Groups	The IAM user 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.
	Subscribing	You must subscribe to the software on AWS before deploying it. See Subscribing to Teradata Software: Quick Deployment.
Teradata Ecosystem Planning
	Teradata Database License Tier	Developer, Base, Advanced, or Enterprise. See Teradata Database License Tiers.
	Teradata Support Account [B, A, E only*]	Register for support at https://www.teradata.com/Products/Cloud/Do-it-yourself/AWS. After completing registration, you will receive email containing your Master Customer Record, site ID, and the user ID and password for the Teradata Customer Support site.
	Teradata Database Ecosystem	Test and Development, Minimum Production, or Full Production. See https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/Instructions.
	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 the Teradata® Software for AWS Installation and Administration Guide for information about NFR.
	Stack Name	Must be unique to the deployment region.
Teradata Database	Version
	System Name
	System Nickname	Used to monitor Teradata Database instances in Teradata Viewpoint.
	DBC Password	New Teradata Database password.
	Number of Nodes	Maximum supported number depends on the license tier.
	Number of Hot Standby Nodes	Maximum supported number depends on the license tier. Do not exceed the number of database nodes.
	Instance and Storage Type	Storage size is per node. For an MPP system, Teradata recommends supported m4 instance types (EBS storage). See Teradata Database Instance Types.
	Scale Out/In [B, A, E 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 or Scale-Out-4x to deploy the system in a 4x scaled out state. These options deploy a half or a quarter of the EBS volumes per instance, respectively, enabling you to scale in the system after deploying
	Data Storage	Supported only on m4 instance types (EBS storage). 5 to 72 TB per node.
	EBS Encryption [B, A, E only*]	Supported only on m4 instance types (EBS storage).
	Root Disk Encryption [B, A, E only*]	Supported only on m4 instance types (EBS storage).
	Japanese Support	Enable to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes.
	Elastic IPs [Minimum and Full Production ecosystems only]	Enable to allocate an elastic IP address to each node.
	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 [A, E 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® Database Utilities and the Teradata® Intelligent Memory Orange Book. To find an Orange Book, go to https://access.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.
Date and Time	System Timezone	[Optional] Default: time zone of the AWS region. Can be changed to the operating system time zone of the database system. Data Mover, DSC, Viewpoint, and Query Service default to the same time zone set for the database.
VPC/Network	VPC	Create an AWS virtual private cloud. Do not use the default Amazon VPC. When you secure your VPC, make sure the Teradata Database instances can still access the AWS service endpoints they require. See AWS Service Endpoints: Quick Deployment.
	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 database or create a new one.
	Data Mover Placement Group	[Optional] Either use the same placement group as the database or create a new one.
Security Group	Remote Access From	Create one or more AWS security groups and configure appropriate ports. See the Amazon User Guide for Linux Instances . To configure ports, see Teradata Software Ecosystems, Security Groups for Other Teradata Applications. In this field, enter the CIDR block to lock down SSH and enable access to nodes.
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 two for high availability.
	Admin Password
	REST Password
	Site ID [B, A, E only*]	String that identifies this Teradata deployment for Teradata Customer Support (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 Teradata Database 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.
Options	Advanced	[Optional] Additional options for your stack, such as notifications and a stack policy.
Custom Tags	Custom Tags	[Optional] Custom tags are added to all instances, in the format key:value. For example, cloud:aws, dbs:teradata
*License tiers: B/Base, A/Advanced, E/Enterprise

Planning Worksheet for a Teradata Software Ecosystem - Teradata Software for AWS

Teradata Vantage™ on AWS (DIY) Quick Deployment Guide