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 Licensing | |||
Purchase Method
[BYOL only] |
Entitlement ID | Enter the entitlement ID. See Bring Your Own License. | |
Term of License | Select the license period. See Bring Your Own License. | ||
Teradata Deployment Planning | |||
Teradata Software | See Supported Teradata Software for AWS. | ||
Software Packaging Options | Choose the Teradata® IntelliSphere™ software bundle or individual software components. See Teradata Software Purchase Options. | ||
Software Purchasing Methods | Choose whether to purchase software from Teradata and bring that license to AWS or purchase from AWS on an hourly basis. For BYOL, see Bring Your Own License and Obtaining Teradata Licensing Information for BYOL. |
||
Software Deployment Methods | Learn about deploying Teradata Database simultaneously with other Teradata software products (recommended method). See Teradata Software Ecosystem. Learn about deploying Teradata products one at a time. See Methods for Deploying Software Solutions Separately. |
||
Subscribing | Whether you use BYOL or an hourly subscription, you must subscribe to the software on AWS before deploying it. See Subscribing to Teradata Software. | ||
Teradata Database License Tier | Developer, Base, Advanced, or Enterprise. | ||
Teradata Support Account [B, A, E only*] |
Register for support at https://www.teradata.com/Products/Cloud/Do-it-yourself/AWS. Existing Teradata customers with a site ID must obtain a new site ID, as you cannot use your existing site ID for Teradata Software for 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 Software Ecosystem | Test and Development, Minimum
Production, or Full Production. See https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/Instructions. |
||
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. | ||
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. See Hot Standby 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 and Storage Considerations, including the sub-topics. |
||
Scale Out/In
[B, A, E only*] |
|
||
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). See Encryption. |
||
Root Disk
Encryption
[B, A, E only*] |
Supported only on m4 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. Teradata Software for AWS 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
[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 |
|
||
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 database system. See Time Zone Considerations and AWS Regions. 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. Use subnets if you want to deploy Teradata Database MPP instances. For subnets, you must enable auto-assignment of public IP addresses. When you secure your VPC, make sure the Teradata Database instances can still access the AWS service endpoints they require. See AWS Service Endpoints. |
|
Database Subnet | Select a subnet to use for the database. Ensure the subnet you select has a sufficient number of IPs available. The Teradata Database 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. column for that specific subnet.nullnull |
||
Ecosystem Subnet | Create one or more subnets, which require a
sufficient number of available IPs:
|
||
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. To configure ports, see Security Groups for Teradata Database and 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 of 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. | |
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 |
|
*License tiers: B/Base, A/Advanced, E/Enterprise |
Planning worksheet for deploying
Teradata Software for AWS. For more information, see:
Parameter names in the ecosystem
templates are shown in bold.