Teradata Database on AWS Getting Started Guide

Transcription

1 What would you do if you knew? Teradata Database on AWS Getting Started Guide B K November 2016

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Applications-Within, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. Amazon Web Services, AWS, [any other AWS Marks used in such materials] are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. CENTOS is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Cloudera, CDH, [any other Cloudera Marks used in such materials] are trademarks or registered trademarks of Cloudera Inc. in the United States, and in jurisdictions throughout the world. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/os are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLib are registered trademarks of Simba Technologies Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright 2016 by Teradata. All Rights Reserved.

3 Table of Contents Preface...7 Purpose... 7 Audience...7 Revision History...7 Additional Information...8 Links: Teradata... 8 Links: Teradata on AWS... 8 Teradata Documentation: Teradata Database and Supporting Utilities...9 Teradata Documentation: Upgrade...9 Teradata Documentation: Ecosystem Support Teradata Documentation: Backup and Recovery...11 AWS Documentation Product Safety Information...11 Chapter 1: Teradata Database on AWS Teradata Database on AWS Overview...13 Assumptions Teradata Database on AWS Software Teradata Database on AWS Software Suite...15 Teradata Database on AWS Use Cases Chapter 2: Preparing for Teradata Database on AWS...17 Quick Start Teradata at Your Service Software Products with Multiple AMIs Site IDs...19 Database Option Management Teradata Database Features...20 Fallback...21 Network Time Protocol Teradata Database Exceptions Key Pairs...22 Virtual Private Cloud Bastion Hosts in Private VPC Subnets...22 Security Groups and Ports...23 Security Groups for Teradata Database Security Groups for Other Teradata Applications Teradata Database on AWS Getting Started Guide 3

4 Table of Contents Elastic IP Addresses Placement Groups...25 Region and Time Zone Considerations Connection Considerations...26 Storage Considerations Local Storage...28 EBS Storage S3 Storage Teradata Database Storage...29 Teradata Database EBS Storage Options Teradata Database Local Storage Options...29 Supporting Software Storage AWS Service Limits Increasing AWS Service Limits...31 Supported Instance Types...31 Teradata Database EBS Storage...32 Teradata Database Local SSD Storage...32 Teradata Database Local HDD Storage Supporting Software EBS Storage...32 Database Templates Database Deployment Illustration...35 Chapter 3: Launching a Teradata Ecosystem Teradata Ecosystem Overview Launching a Teradata Ecosystem Chapter 4: Launching Teradata Components Separately...43 Launch Paths...43 Launch Options...44 Launching Teradata Database Using CloudFormation...44 Launching Teradata Data Mover Using CloudFormation...48 Data Mover Template Illustration...51 Launching an Instance Using Manual Launch Launching an Instance Using 1-Click Launch...55 Chapter 5: Configuring Teradata Software for AWS Configuration Overview System Console Configuration Configuring PuTTY for Teradata Database on AWS Connections...59 Configuring SecureCRT for Teradata Database on AWS Connections...60 Data Movement Using Teradata Data Mover...60 Configuring Teradata Data Mover Configuring Data Mover Portlets on a Viewpoint Instance Teradata Database on AWS Getting Started Guide

5 Table of Contents Teradata Data Stream Utility Configuration Initializing a DSU Instance...64 Configuring and Initializing ClientHandler on Teradata Nodes...65 Configuring a Teradata Viewpoint Instance for DSU Configuring Additional EBS Storage for a DSU Instance Teradata Ecosystem Manager Configuration Configuring the Teradata Ecosystem Manager Server Configuring the Ecosystem Manager Portlet on the Viewpoint Server Configuring Teradata REST Services Teradata Server Management Configuration Configuring the CMIC Interactively...70 Configuring the CMIC in Batch Mode Configuring ServiceConnect and Alerts for Server Management...74 Changes to the CMIC Configuration...76 Configuring Teradata Viewpoint...76 Chapter 6: Installing and Configuring Other Teradata Applications Teradata QueryGrid Installation Teradata Distribution for Presto Installation...79 Installing and Configuring Teradata QueryGrid...79 Teradata QueryGrid within AWS...80 Teradata QueryGrid between AWS and On-Premises...80 Installing and Configuring Teradata Studio Installing and Configuring Teradata Tools and Utilities Chapter 7: Administrative Tasks...83 Stopping or Terminating a Teradata Database on AWS...83 Setting EBS Storage for Deletion on Instance Termination...83 Deleting a CloudFormation Stack Chapter 8: Data Backup and Recovery...85 Backup Summary Backup and Restore Using Data Stream Utility...85 Using S3 Storage as the Backup Target...85 Using EBS Storage as the Backup Target...86 Chapter 9: Upgrading Teradata Software for AWS Upgrade Overview Obtaining Software Bundles for Upgrade Upgrading Teradata Components Other than Server Management Teradata Database on AWS Getting Started Guide 5

6 Table of Contents Upgrading Server Management...89 Creating a Post-Upgrade Restore Image Chapter 10: Backing Down Teradata Software for AWS Backdown Summary...91 Backing Down Overview...91 Backing Down Server Management Chapter 11: Troubleshooting Teradata Database on AWS...93 Customer Support...93 Connection Issues Correcting Instance Connections IP Address Changes Database Issues...94 Logon Problems Crashdumps...94 Data Corruption...94 Node Failure Recovery Configuring the Instance State for Node Failure Recovery Rebuilding AMPs after Failure...96 Running the Script to Rebuild AMPs...96 Server Management Issues...98 Validating the CMIC Configuration File...98 Server Management Connections with Viewpoint Site ID Errors Appendix A: Acronyms Acronyms Teradata Database on AWS Getting Started Guide

7 Preface Purpose Learn about Teradata software on AWS, including how to launch and configure Teradata Database on AWS components to run a self-managed Teradata Database single-node or multi-node (MPP) instance in the AWS public cloud. Audience This guide is intended for use by System Administrators and others involved in configuring Teradata Database and supporting Teradata software in the AWS public cloud. Revision History Date November 2016 September 2016 Description Implemented the following changes: You can now launch a Teradata Database instance up to 64 nodes. If launching Teradata Database using CloudFormation, you no longer need to specify the type of storage under deployment options. When launching a Teradata Ecosystem or Teradata Database using CloudFormation, you can now select new or existing subnets and placement groups, and have the option to encrypt your EBS volumes. Also, removed BYNET subnets. Added enhancements to node failure recovery. Added Rebuilding AMPs after Failure and Running the Script to Rebuild AMPs to fully restore a local storage instance after a node failure. Added Stopping or Terminating a Teradata Database on AWS. Added support for m4.16xlarge instance type for Teradata Database EBS storage. Teradata Secure Zones is no longer enabled by default. Teradata QueryGrid for Aster supports querying between Teradata Database and Teradata Aster instances. Added support for the following: Teradata Database MPP instances, including supporting software. Launching a Teradata Ecosystem. S3 storage for backing up and restoring your Teradata Database using Teradata DSU. Automatic node failure recovery. Also added Configuring the Instance State for Node Failure Recovery. New Teradata QueryGrid connectors, including Cloudera, IBM BigInsights, and Presto. Teradata Database on AWS Getting Started Guide 7

8 Preface Additional Information Date Description June 2016 Added Bastion Hosts in Private VPC Subnets including information on using SSH agent forwarding. Removed EBS Storage Expansion after Instance Launch. Although you can add EBS storage volumes for storing files and data, the volumes cannot be used by Teradata Database instances. April 2016 March 2016 Added the following new topics: Quick Start Acronyms Increasing EBS Limits on a Teradata Database 20 TB Instance Initial release Additional Information Links: Teradata URL index.html Description Customer documentation for using Teradata products Orange Books, technical alerts, knowledge repositories, and access to downloading software packages Teradata Developer Exchange is a collaborative website connecting Teradata employees with customers to share ideas, ask questions, learn, and solve problems related to Teradata products Documentation for installing and configuring the Teradata Distribution of Presto Links: Teradata on AWS URL Description Overview of Teradata Database on AWS Resources and FAQ for Teradata Database on AWS Teradata services offered for Teradata Database on AWS Support for Teradata Database on AWS, including a link to register and log on to TaYS 8 Teradata Database on AWS Getting Started Guide

9 Preface Additional Information URL Database-on-AWS/bd-p/ Description Forum for Teradata Database on AWS AWS Marketplace Teradata Documentation: Teradata Database and Supporting Utilities To view or download Teradata documentation, access the Teradata Information Products website at Title Publication ID Database Administration B Introduction to Teradata B Release Summary Describes Teradata Database 14.0 features referenced in this guide (B A). Describes Teradata Database features referenced in this guide (B K). B Resource Usage Macros and Tables B Security Administration B SQL Data Definition Language Detailed Topics B SQL Data Definition Language Syntax and Examples B Temporal Table Support Describes temporal tables which store and maintain information with respect to time.using temporal tables, Teradata Database can process statements and queries that include time-based reasoning. Teradata Studio, Studio Express, and Plug-in for Eclipse Installation Guide Describes how to install and configure the software for Teradata Studio, Studio Express, and the Plug-in for Eclipse. Utilities Describes utility programs that support Teradata Database. B B B Teradata Documentation: Upgrade To view or download Teradata documentation, access the Teradata Information Products website at Title Parallel Upgrade Tool (PUT) Reference Describes how to install application software using PUT. Publication ID B Teradata Database on AWS Getting Started Guide 9

10 Preface Additional Information Teradata Documentation: Ecosystem Support To view or download Teradata documentation, access the Teradata Information Products website at Title Teradata Data Lab User Guide Describes how to use Teradata Data Lab portlets. Teradata Data Mover User Guide Describes how to use the Teradata Data Mover portlets and command-line interface. Teradata Ecosystem Manager User Guide Describes how to use Teradata Ecosystem Manager portlets. Teradata QueryGrid: Teradata and Hortonworks Hadoop Installation Guide Describes how to install the software to run Teradata-to-Hadoop queries. Teradata QueryGrid: Teradata Database-to-Cloudera Distribution for Hadoop Installation Guide Describes how to install the software and configure Hadoop to run Teradata-to- Hadoop queries for Cloudera Distribution. Teradata QueryGrid: Teradata Database-to-IBM Installation Guide Describes how to install the software and configure Hadoop to run Teradata-to- Hadoop queries for IBM BigInsights Distribution. Teradata QueryGrid Teradata Database-To-Presto Installation and User Guide Describes how to install the driver for Teradata Database and a connector for Presto to run queries on Presto from Teradata Database. Teradata QueryGrid: Teradata Database-to-Teradata Aster Installation Guide Describes how to install the software to run queries for transferring data between Teradata Database and remote Teradata Aster hosts. Teradata QueryGrid: Teradata Database-to-Teradata Aster User Guide Describes how to configure and use the Teradata-to-Aster connector. Teradata REST Services Installation, Configuration, and Upgrade Guide for Customers Describes how to install the REST container package and configure REST API services. Teradata Server Management Web Services User Guide Describes the SMWeb client and procedures for servicing Teradata hardware. Teradata Viewpoint User Guide Describes the Teradata Viewpoint portal, portlets, and system administration features. Publication ID B B B B B B Not applicable B B B B B Teradata Database on AWS Getting Started Guide

11 Teradata Documentation: Backup and Recovery Preface Product Safety Information To view or download Teradata documentation, access the Teradata Information Products website at Title Data Stream Extensions Installation, Configuration, and Upgrade Guide for Customers Describes how to configure Data Stream Extensions software and devices. Data Stream Utility Installation, Configuration, and Upgrade Guide for Customers Describes how to configure Data Stream Utility software and devices. Teradata Data Stream Architecture User Guide Describes how to use the Teradata Data Stream Architecture (DSA) portlets and command-line interface. Publication ID B B B AWS Documentation Title Getting Started with AWS Describes how to get started with AWS and includes an overview and tutorials. Amazon User Guide for Linux Instances Describes key concepts of Amazon EC2 and instructions for using Amazon EC2 features. Amazon Virtual Private Cloud User Guide Describes the AWS feature that lets you launch resources into a virtual network that you have defined. AWS CloudFormation Documentation Describes AWS CloudFormation and includes instructions on using the various features. AWS Security Best Practices Describes how to build a set of security policies and processes to protect data and assets in the AWS cloud. Publication ID Not applicable Not applicable Not applicable Not applicable Not applicable Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. Teradata Database on AWS Getting Started Guide 11

12 Preface Product Safety Information 12 Teradata Database on AWS Getting Started Guide

13 CHAPTER 1 Teradata Database on AWS Teradata Database on AWS Overview AWS enables you to create a self-managed Teradata Database single-node or MPP instance (up to 64 nodes) directly in the AWS public cloud. As a self-provisioned environment, Teradata Database on AWS is delivered as software that can be deployed in the AWS IaaS environment. Teradata offers a variety of multiterabyte Amazon EC2 instances in the AWS Marketplace for the Teradata Database and supporting software. AWS Marketplace is an online store that helps you find, buy, and immediately start using software and services. Amazon EC2 is a virtual computing environment, allowing you to use web service interfaces to launch Teradata instances with the Linux SLES 11 SP3 operating system, load them with a custom application environment, and manage network access permissions. Running Teradata Database on AWS is similar to running a Teradata Database in your on-site data center. To a database administrator, there are no differences between the two environments. There are, however, a number of AWS considerations relating to configuring software, migrating data, security, and data backup relating to system management that are explained in this guide. An AMI is a template you use to launch a virtual server in the AWS public cloud, called an instance. An instance is launched from an AMI, and you can launch as many instances from the AMI as you need. Teradata provides pre-configured AMIs for Teradata Database and supporting software in the AWS Marketplace to get you up and running immediately. For a list of acronyms used in this documentation, see Acronyms. Assumptions This guide assumes a solid understanding of general cloud computing and the AWS environment, including: Using the AWS Marketplace, AWS EC2 Console, and AWS Command Line Tool Starting, stopping, and terminating an AWS instance, including implications for storage persistence and related costs Teradata Database on AWS Software The following is a list of Teradata software available on AWS. You can launch the software as a Teradata Ecosystem or separately. For more information, see Launching a Teradata Ecosystem and Launching Teradata Components Separately. As AMIs are updated in the AWS Marketplace, the latest software version number is listed under Product Details in the AMI description. Maintenance and efix versions may be updated in the AWS Marketplace so check the Product Details before launching an AMI. Teradata Database on AWS Getting Started Guide 13

14 Chapter 1: Teradata Database on AWS Teradata Database on AWS Software Software Name Teradata Database Teradata Data Mover Teradata Data Stream Utility Teradata Ecosystem Manager Teradata Parallel Upgrade Tool Teradata QueryGrid Teradata REST Services Teradata Server Management Teradata Studio Teradata Tools and Utilities Description Provides the same full-feature data warehouse software that powers analytics at many of the world's greatest companies, and is available with local and attached storage. Leverages all of the established data loading protocols and technologies to meet your data movement needs. You can use the utility for regular periodic tasks including populating a dependent data mart from an enterprise data warehouse as well as special one-time tasks such as moving data to a test system. Provides backup and restore capabilities for data resilience that can help you overcome data loss caused by user error, system hardware failure, application failure, and natural disasters, while also satisfying long-term storage requirements imposed by corporate and government regulations. Provides an end-to-end approach to meeting application service level agreements through monitoring, administration, and control of both single and multi-system environments to let you more effectively manage every part of your data warehouse environment. Provides a way to upgrade Teradata Database and other Teradata software. This software is bundled with Teradata Database. Provides bi-directional data transfer, ad-hoc query capabilities and pushdown processing for running queries using data and analytics on the Teradata Database. Enables querying of metadata, partition pruning, push-down processing, and importing data and joins from Teradata Database to Hadoop file systems (HDP, CDH, and IBM BigInsights), from Teradata Database to Presto, from Teradata Database to Teradata Aster Database, and between Teradata Database systems. This software is bundled with Teradata Database. Provides an interface to Teradata Database allowing application developers a simplified, modern interface to connect to data from a web page or application. Monitors the instance and generates alerts related to database and operating system errors and operational state changes. Events that affect the operation of the system generate alerts. Provides a desktop tool for performing database administration, query development, and management tasks on Teradata Databases, Teradata Aster Databases, and Hadoop systems. This software is accessed from Teradata Developer Exchange. Provides GUIs for integrating your Teradata system into your enterprise and streamlining the daily data warehouse management tasks, such as moving massive volumes of data and accessing multiple data sources in parallel, and improving your overall Teradata system performance on Windows or Linux operating systems. This software is bundled with Teradata Database. 14 Teradata Database on AWS Getting Started Guide

15 Chapter 1: Teradata Database on AWS Teradata Database on AWS Software Suite Software Name Teradata Viewpoint Description Provides a web-based management portal for Teradata performance and health management which is easy to use. It provides a consistent interface using configurable portlets which allows you to customize your own systems management dashboard. Teradata Data Lab, which is included in certain versions of Teradata Viewpoint, allows you to provision and manage analytic workspaces in the Teradata data warehouse. Teradata Database on AWS Software Suite Teradata Database on AWS offers one suite on the AWS Marketplace that includes the rights to use the listed software: Suite Name Teradata Database Enterprise Edition Included Software Teradata Database on Linux SLES 11 SP3 Parallel Upgrade Tool Teradata Active System Management Teradata Data Stream Utility Teradata Parallel Transporter including the Load, Update, Export, and Stream operators Teradata QueryGrid: Teradata-to-Teradata, Teradata-to-Teradata Aster, Teradata-to-Hadoop (HDP, CDH, and IBM BigInsights), and Teradata-to- Presto Teradata REST Services Teradata Server Management Teradata Studio Teradata Tools and Utilities Teradata Viewpoint, not including Teradata Data Lab Other products available include the following for an additional cost: Teradata Data Lab Teradata Data Mover Teradata Ecosystem Manager Teradata monitoring service for Server Management is available for an additional price. Teradata instances run on various instance types that support local or EBS storage for an additional price. For more information, see the topics under Storage Considerations. Note: An evaluation instance of Teradata Database on AWS is available for 30 days and is called Teradata Database Developer (Single Node). During that 30 day period, there are no software charges, but AWS infrastructure charges still apply. Community-driven support is available in the Teradata Database on AWS forum: At the end of the trial, the instance automatically converts to a paid hourly subscription. Teradata Database on AWS Getting Started Guide 15

16 Chapter 1: Teradata Database on AWS Teradata Database on AWS Use Cases Teradata Database on AWS Use Cases Teradata can be used in different ways when a powerful relational database solution is needed in the AWS public cloud. Use Case Analytics Sandbox Backup, Archive, and Restore Database Conversions Migrations Persistent Test and Development Description AWS provides a short-lived, flexible, and evolving analytic environment that can be easily stood up, evolved, scaled, and shut down based on discovery, development, and testing needs. Migrating a portion of your BAR operations to the cloud can reduce hardware and maintenance costs and convert capital expenses to operating expenses. Most solutions include a combination of on-premises and cloud storage based on the need to restore from the backup. Teradata on AWS offers a path to migrate from a third-party database to Teradata, focusing on automatically inventorying, capturing, and recreating data structures on Teradata and the SQL code conversion. Use Teradata Database on AWS to migrate workloads from onpremises to the cloud in total or in part. Migrations include establishing the environment and an initial historical data load/ port. Use Teradata Database on AWS to stand up a persistent and scalable environment for developing and testing solutions prior to deploying into production. The test/dev environment typically includes the other ecosystem components running in your production environment. For more information, see 16 Teradata Database on AWS Getting Started Guide

17 CHAPTER 2 Preparing for Teradata Database on AWS Quick Start Before launching Teradata Database on AWS instances, the following information helps you get started. Steps Sign up for an AWS account. Learn about and create users and groups for identity and access management (IAM). Learn about and create one or more key pairs. Learn about and create a new VPC. Learn about and create one or more security groups and learn which ports should be opened. Learn about and create one or more subnets, if needed. Learn about elastic IP addresses if needed. Learn about placement groups, if needed. Learn about time zones and availability zones. More Information See Sign Up for AWS under Setting Up in the Amazon User Guide for Linux Instances. See Create an IAM User under Setting Up in the Amazon User Guide for Linux Instances. See Key Pairs. To create a key pair, see Create a Key Pair under Setting Up in the Amazon User Guide for Linux Instances. See Virtual Private Cloud and Connection Considerations. To create a VPC, see Create a Virtual Private Cloud (VPC) under Setting Up in the Amazon User Guide for Linux Instances. See Security Groups and Ports. To create a security group, see Create a Security Group under Setting Up in the Amazon User Guide for Linux Instances. To learn about subnets, see Amazon Virtual Private Cloud User Guide. Teradata recommends using subnets especially if you want to launch Teradata Database MPP instances. See Elastic IP Addresses if you plan to launch a Minimum Production or Full Production Teradata Ecosystem. For more information on using elastic IP addresses, see Amazon User Guide for Linux Instances. See Placement Groups, especially if you want to launch Teradata Database MPP, Teradata Data Mover, and Teradata DSU instances. To create a placement group, see Placement Groups under Network and Security in the Amazon User Guide for Linux Instances. See Region and Time Zone Considerations. To learn more, see Regions and Availability Zones under What is Amazon EC2 in the Amazon User Guide for Linux Instances. Teradata Database on AWS Getting Started Guide 17

18 Chapter 2: Preparing for Teradata Database on AWS Quick Start Steps Learn about when to use public IP/DNS addresses versus private IP/DNS addresses. Decide if you want temporary or persistent storage for your data. Learn about available Teradata products. Learn about options for Teradata Database MPP instances. Decide the way you want to launch your Teradata Database instance. Learn about AWS service limits and increase them in advance of the time that you need them. Learn about administrative tasks Learn about subscribing. Learn about managing your AWS Marketplace subscriptions. Register for Teradata Support. Learn about how to use the Teradata Database and the associated software. More Information See Connection Considerations. To learn more, see Instance IP Addressing under Network and Security in the Amazon User Guide for Linux Instances. See Storage Considerations, including the sub-topics in this section. To learn more, see Storage in the Amazon User Guide for Linux Instances. See Teradata Database on AWS Software. For products with more than one AMI, decide which AMI you want to launch. See Software Products with Multiple AMIs. To learn about basic configuration options for Teradata Database MPP instances (up to 64 nodes), see Database Templates. To learn more, see AWS CloudFormation Documentation. If you are launching Teradata Database MPP instances, set up alerts so you will be notified when the database restarts after a node failure. For more information, see Node Failure Recovery. To learn about the recommended method of launching Teradata Database and multiple other Teradata software products simultaneously, see Teradata Ecosystem Overview. To learn about launching Teradata products one at a time, see Launch Paths. Among other limits, Teradata recommends increasing the instance limits to support the Node Failure Recovery process. To learn more, see AWS Service Limits. Learn about important topics to avoid incurring charges, including Stopping or Terminating a Teradata Database on AWS. See Subscribing, Launching, and Managing Products at aws.amazon.com/marketplace/help. Launching an AMI automatically subscribes you to the product. To find paid AMIs for Teradata products using the AWS Marketplace, see Paid AMI under Amazon Machine Images in the Amazon User Guide for Linux Instances. See Managing Your AWS Marketplace Subscriptions in the Amazon User Guide for Linux Instances. When you subscribe to Teradata Database on AWS, you receive a welcome that enables you to register for support. After your support registration is complete, you receive another with your Master Customer Record, Site ID (AMZ followed by 12 numbers), user ID, and password. See for Teradata customer documentation. For example, see the Teradata Viewpoint User Guide to learn how to monitor your Teradata Database. 18 Teradata Database on AWS Getting Started Guide

19 Teradata at Your Service TaYS ( is a secure portal that provides Teradata customers access to Teradata products, services, education, and support and is used to: Request support from Teradata regarding an incident Access educational materials Download software releases Chapter 2: Preparing for Teradata Database on AWS Teradata at Your Service Customers who already use TaYS for products previously purchased from Teradata cannot use their previous TaYS account for Teradata Database on AWS. You must obtain a new TaYS account for Teradata Database on AWS. For information on using TaYS, see the TaYS Admin User Manual at the bottom of the TaYS home page. Software Products with Multiple AMIs To address different ways in which software may be used, some Teradata Database on AWS products offer multiple AMIs. For more information about local and EBS storage, see the topics under Storage Considerations. AMI Teradata Database Developer (Single Node) Teradata Database Enterprise Edition (1-64 Nodes) Teradata Viewpoint (Single Teradata System) Teradata Viewpoint (Multiple Teradata Systems) Teradata Viewpoint (Single Teradata System) with Teradata Data Lab Use Case 30-day evaluation a Teradata Database instance on a single node. See Teradata Database on AWS Software Suite. Able to manage one Teradata instance. Able to manage up to 10 Teradata instances. Able to manage one Teradata instance requiring provisioning and management of analytic workspaces in the Teradata data warehouse. Site IDs A site ID is a unique code to identify your installation of Teradata Database on AWS. Although this site ID is not required to use Teradata Database on AWS, it is required to receive Teradata support. When you subscribe to Teradata Database on AWS, you receive a welcome that enables you to register for support. After your support registration is complete, you receive another with your Master Customer Record, Site ID (AMZ followed by 12 numbers), user ID, and password. Existing Teradata customers who have on-premises Teradata systems cannot use their previous site IDs on Teradata Database on AWS. You must obtain a new site ID. Database Option Management Teradata Database on AWS offers the same features that come with an on-premises Teradata Database system with a couple of exceptions. Teradata Database on AWS Getting Started Guide 19

20 Chapter 2: Preparing for Teradata Database on AWS Database Option Management Teradata Database Features Teradata Database on AWS offers many Teradata Database features including, but not limited to, those listed in this topic. All features listed below are included in the Teradata Database Enterprise Edition. Although the package is included in the Teradata Database AMI, you still need to install and configure it. The following terms are used in the table below: Automatic indicates you do not have to install or configure the feature and can begin using the feature after a Teradata Database instance is launched. Manual indicates you must install and configure the feature using the Teradata Database documentation, similar to on-premises systems. Features that require Teradata Customer Support to enable a feature are noted. For more information, including how to install and configure the listed features, see the Documentation column. Database Feature Block-Level Compression Fallback Node Level Buffering Teradata Columnar Teradata File System Checksum Teradata QueryGrid Description Stores data blocks in compressed format to save storage space and improve performance. See Release Summary for Teradata Database Protects data in case of an AMP vproc failure. See Introduction to Teradata. Use for query row redistribution. Provides the ability to partition a table or join index by column. See Release Summary for Teradata Database Used to detect data corruption, you can specify an amount of data used to compute the checksum for a table. See Release Summary for Teradata Database Provides bi-directional data transfer, ad-hoc query capabilities and Enabled by Default Yes for EBS No for local storage Installation and Configuration Automatic for EBS. Manual for local storage (not recommended). Documentation Database Administration Yes Automatic SQL Data Definition Language Syntax and Examples Yes Automatic Resource Usage Macros and Tables See the ResUsageSpma table. Yes Automatic Must be configured. SQL Data Definition Language Syntax and Examples Yes Automatic Checksum option for DDL: SQL Data Definition Language Detailed Topics Checksum settings in DBS Control: Utilities No Manual Must be installed and configured. Teradata Documentation: Ecosystem Support 20 Teradata Database on AWS Getting Started Guide

21 Chapter 2: Preparing for Teradata Database on AWS Database Option Management Database Feature Teradata Row- Level Security Teradata Secure Zones Teradata Temporal Description more for running queries using data and analytics. Allows you to restrict data access by row in the Teradata Database. See Release Summary for Teradata Database Provides grouping of user and database hierarchies into separate database partitions with restriction of user access to one or more zones. See Release Summary for Teradata Database Provides built-in capabilities that are required in a temporal database management system. Enabled by Default Installation and Configuration Documentation Yes Manual Security Administration No Manual Security Administration No. Contact Teradata Customer Support to enable. Manual Temporal Table Support Fallback Fallback is a Teradata Database feature that protects data in case of an AMP vproc failure. Fallback is especially useful in applications that require high availability. Fallback is enabled by default when you launch a Teradata Database instance in the AWS public cloud. You cannot override the fallback setting during table creation nor after a table is created. Fallback is automatic and transparent. Fallback protects your data by storing a second copy of each row of a table on a different AMP in the same cluster. If an AMP fails, the system accesses the Fallback rows to meet requests. Fallback provides AMP fault tolerance at the table level. With Fallback tables, if one AMP fails, all data is still available. You can continue using Fallback tables without any loss of access to data. Fallback guarantees that the two copies of a row will always be on different AMPs. If either AMP fails, the alternate row is still available on the other AMP. When copying tables without Fallback enabled from another source, either inside or outside the AWS public cloud, Teradata recommends you issue an ALTER TABLE command to enable Fallback. For more information, see the Teradata Database documentation. Network Time Protocol NTP is configured and enabled by default to automatically communicate to AWS NTP servers when you launch the Teradata Database instance. Ensure the outbound port is open for NTP. See Security Groups and Ports. Teradata Database on AWS Getting Started Guide 21

22 Chapter 2: Preparing for Teradata Database on AWS Key Pairs Teradata Database Exceptions Teradata Database on AWS offers the same features that come with an on-premises Teradata Database system with the following exceptions: Data block read ahead count is 15 data blocks. Default PERM DB size for permanent tables is 2047 sectors. Default SPOOL DB size for temporary tables is 2047 sectors. One single transaction can consume 100% of FSG cache. Key Pairs Amazon EC2 uses public-key cryptography to encrypt and decrypt login information. Public-key cryptography uses a public key to encrypt a piece of data, such as a password, then you use the private key to decrypt the data. The public and private key combination is known as a key pair. To log on to your instance, you must create a key pair, specify the name of the key pair when you launch the instance, and provide the private key when you connect to the instance. Linux instances have no password, and you use a key pair to log on using SSH. If you create a key pair in one region, you cannot see or use that key pair in another region. In other words, key pairs cannot be shared between regions. You can create your own key pair that you can use in all regions by using a third-party tool and then importing the key to Amazon EC2. For more information on key pairs, see Amazon User Guide for Linux Instances. Virtual Private Cloud An Amazon VPC allows you to provision a separate, isolated section of the AWS cloud where you can launch AWS resources in a virtual network that you define. You control your virtual networking environment, including selecting your own IP address range, creating subnets, configuring network gateways, and more. In keeping with best practices related to security, do not use the default Amazon VPC when launching Teradata Database on AWS instances. The default VPC is open to the AWS public cloud. To create a VPC, see Create a Virtual Private Cloud (VPC) under Setting Up in the Amazon User Guide for Linux Instances. For information on best practices, see AWS Security Best Practices. For information on Amazon VPC connectivity options, see Amazon Virtual Private Cloud Connectivity Options. Bastion Hosts in Private VPC Subnets Bastion hosts allow you to securely connect to EC2 instances running in VPC private subnets without exposing them to the Internet. A bastion host is set up in the public subnet and acts as a proxy/jump server and it should be configured with a high level of security. Consult your security administrator for configuring a bastion host. 22 Teradata Database on AWS Getting Started Guide

23 Chapter 2: Preparing for Teradata Database on AWS Security Groups and Ports To securely connect to EC2 instances in VPC private subnets, you can use SSH agent forwarding. Using SSH agent forwarding improves security by not exposing the management ports of your EC2 instances to the Internet or to other subnets in your VPC. For information on how to configure SSH agent forwarding, see and type Securely connect to Linux instances running in a private Amazon VPC in the search box. Security Groups and Ports A security group acts as a virtual firewall that controls the traffic allowed to reach one or more instances. When you launch an instance, you associate one or more security groups with the instance. You add rules to each security group that allow traffic to or from its associated instances on specified ports. You can modify the rules for a security group at any time; the new rules are automatically applied to all instances that are associated with the security group. Follow AWS best practices for security group settings. Do not use the default VPC because it is open to the public. See AWS Security Best Practices. For more information on creating a security group, see Amazon User Guide for Linux Instances. Security Groups for Teradata Database When configuring a security group for the Teradata Database, set up the port ranges listed below for each Teradata Database instance so the Teradata Database can be locked down to the local host. Port 1025 is blocked in the local instance until the dbc password is changed. If you are using NTP, ensure the VPC ACL setting is not blocking UDP port 123 for both inbound and outbound traffic. When launching a Teradata Database MPP instance using CloudFormation, add the private IP addresses of Teradata software instances to the public security group of the Teradata Database instance for any TCP port ranges you are using from For CloudFormation, you accomplish this by adding the private IP addresses of the following software instances to the Remote Access From parameter of the Teradata Database instance. For a Manual Launch, add the private IP addresses of the software instances when you configure the security group. Teradata Data Mover Teradata DSU Teradata Ecosystem Manager Teradata REST Teradata Viewpoint Teradata Database on AWS Getting Started Guide 23

24 Chapter 2: Preparing for Teradata Database on AWS Security Groups and Ports Software Direction Protocol Port Range Description Teradata Database Inbound TCP TCP SSH Teradata Database Service to AWS Teradata Database Outbound TCP 123 NTP Security Groups for Other Teradata Applications When configuring a security group for Teradata software applications, set up the following port ranges for each software instance to allow access to and from those ports. Although all outbound ports can be opened, ensure the outbound ports listed below are specifically designated. Only add ports for software being accessed. For example, do not add ports for Server Management unless it is being used. Software Direction Protocol Port Range Description Parallel Upgrade Tool (PUT) Inbound TCP TCP TCP , 8080 SSH RDP Axeda or Teradata Connect to connect to PUT Open the ports listed under Teradata Server Management if applicable to your environment. Teradata Data Mover Inbound TCP TCP TCP TCP TCP TCP TCP TCP , SSH Teradata Database Service REST Server Management ARC Server ARC Access Module Master Sync Service ActiveMQ Teradata Data Stream Utility Inbound TCP TCP TCP TCP TCP TCP SSH Teradata Database Service DSA REST Services BarNC Data Traffic BARNC Web Service ActiveMQ Teradata Ecosystem Manager Inbound TCP TCP TCP TCP TCP SSH Teradata Database to Ecosystem Manager on AWS ActiveMQ Agent packages Ecosystem Manager Control Engine Teradata QueryGrid See Teradata QueryGrid within AWS and Teradata QueryGrid between AWS and On-Premises. Teradata REST Services Inbound TCP TCP SSH REST Teradata REST Services Outbound TCP 1025 Single instance of Teradata REST Services to Teradata Database from AWS Teradata Server Management Managed Instances Inbound TCP TCP TCP Allow SSH over the VPC subnet For sm3gnode; only needs to be allowed from the Server Management (also known as CMIC) instance 5190 is also for sm3gnode. Same as above. Teradata Server Management CMIC Instance Inbound TCP TCP TCP TCP SSH REST (http) REST (https) Java Proxy Tunnel 24 Teradata Database on AWS Getting Started Guide

25 Software Direction Protocol Port Range Description Chapter 2: Preparing for Teradata Database on AWS Elastic IP Addresses TCP TCP UDP TCP TCP Java RMI Java Connections Tunnel SOV Ping CMIC Web (https) JMS Teradata Server Management Outbound UDP TCP TCP NTP HTTPS for ServiceConnect ServiceConnect to policy server; only if policy server is being used Teradata Tools and Utilities Inbound TCP TCP SSH Teradata Database Service Teradata Viewpoint Inbound TCP TCP TCP TCP TCP SSH HTTP for Viewpoint HTTPS for Viewpoint Teradata Alerts ActiveMQ Teradata Viewpoint Outbound TCP 1025 Single instance of Teradata Viewpoint to Teradata Database from AWS Elastic IP Addresses An elastic IP address is a static IP address designed for dynamic cloud computing and is associated with your AWS account. With an elastic IP address, you can mask the failure of an instance of software by rapidly remapping the address to another instance in your account. Teradata Database on AWS uses EC2-VPC elastic IP addresses. Although you can use EC2-VPC elastic IP addresses for all Teradata Ecosystems, we strongly recommended you use them for Minimum Production and Full Production Teradata Ecosystems. In case of node failure, assigning EC2-VPC elastic IP addresses to the public IP addresses of each instance enables you to reconnect without having to update the Teradata cop entry IP addresses. For more information on using elastic IP addresses, see Amazon User Guide for Linux Instances. Placement Groups A placement group is a logical grouping of instances within a single availability zone. Placement groups enable applications to participate in a 10 Gbps network. Placement groups are recommended for instances that need low network latency, high network throughput, or both. Create placement groups before launching a Teradata Database instance, especially a Teradata Database MPP instance. If you do not use placement groups, database performance will be impacted. For example, you may experience high CPU skew on a node. Also use placement groups for Teradata Data Mover and Teradata DSU instances to ensure better performance. When you are launching a Teradata Ecosystem, you are given the option to create a placement group so you do not have to create ahead of time. After creating a placement group, you can launch multiple instances into the same group. For example, create a placement group containing the Teradata Database and the Teradata DSU instances. After launching an instance, a placement group should not be modified. Teradata Database on AWS Getting Started Guide 25

26 Chapter 2: Preparing for Teradata Database on AWS Region and Time Zone Considerations The following Teradata Database on AWS software benefits particularly from inclusion in placement groups: Teradata Database Teradata Data Mover Teradata Data Stream Utility Teradata Ecosystem Manager Teradata REST Services Teradata Viewpoint For more information on creating placement groups, deleting placement groups, and placement group limitations, see Amazon User Guide for Linux Instances. Region and Time Zone Considerations Amazon EC2 is hosted in multiple locations worldwide, and these locations are composed of regions and availability zones. Each region is a separate geographic area and has multiple, isolated locations known as availability zones. When launching an instance, you can use the EC2 VPC Console to create a new subnet or select No preference to allow AWS to select the best subnet in any availability zone. Teradata recommends using subnets especially if you want to launch Teradata Database MPP instances. By default, the time zone for Teradata Database instances on AWS is set based on the region you choose when you launch your instance. For example, if you launch an instance using the U.S. West region, instances are in the Pacific time zone. You have the option to change the operating system time zone when you launch the Teradata Database instance. Teradata Data Mover, Teradata Data Stream Utility, Teradata Viewpoint, and Teradata REST Services default to the same availability zone as the Database instance. Teradata Server Management and Teradata Ecosystem Manager time zones default to UTC and cannot be changed. For more information on changing the time zone on an instance or using regions and availability zones, see Amazon User Guide for Linux Instances. Connection Considerations If you are using EC2 instances within the AWS public cloud, configure these instances to reside in the same VPC. When configuring the software, use private IP addresses to connect to these instances. If you are using EC2 instances to connect from the AWS public cloud to an on-premises Teradata system, use public IP addresses to connect to the on-premises Teradata system when configuring the software. You only need to use public IP addresses if you launch an instance using a public VLAN. If you launch an instance using a private VLAN, the instances have private IPs and a VPC connection is required for SSH access. When launching an instance, make a note of the IP and DNS addresses of the Teradata Database instance and the IP and DNS addresses of the additional software. Use this information when configuring the additional software instances. Instance location determines whether to use internal or external addresses when configuring the following software: Teradata Data Mover 26 Teradata Database on AWS Getting Started Guide

27 Teradata Ecosystem Manager Teradata REST Services Teradata Viewpoint Chapter 2: Preparing for Teradata Database on AWS Storage Considerations For example, use Teradata Database private IP addresses in Data Mover job XML and Data Mover portlets if all AWS instances reside in the same VPC. In Data Mover portlets, use the private IP address of the Data Mover instance to connect to a Teradata Database system. If source and target systems reside outside AWS, such as an on-premises system, use the public IP addresses instead. Note: Only the software listed above can connect to an on-premises system if you have opened the appropriate inbound ports in the corporate firewall on those premises. Storage Considerations Before launching a Teradata Database on AWS instance, consider the implications of the available storage types, including media, capacity, data persistence, and cost related to data persistence. Teradata Database on AWS offers the following types of storage: Storage Type Amazon EC2 Instance Local Storage Amazon Elastic Block Storage (EBS) Intended Use Case Local (both SSD and HDD) Storage is ephemeral and requires a running instance Potential for data loss if instance fails Data protection available using Teradata DSU Lower reliability than EBS; HDD is lower reliability than SSD SSD Only Highest performance Highest cost per vcpu per TB Up to 6.4 TB of storage per EC2 instance HDD Only Lower performance than SSD Lower cost per vcpu per TB than SSD Up to 48 TB storage per EC2 instance EBS (SSD) Highest reliability Lower performance (network-attached) Lowest cost per vcpu even with extra charges for EBS Up to 20 TB remote storage (pre-provisioned) on SSD volumes attached to the instance Storage is expandable by attaching additional EBS volumes Data persists independent of running an instance which provides the ability to shut down an instance between sessions to reduce EC2 costs and lower cost of ownership Teradata Database on AWS Getting Started Guide 27

28 Chapter 2: Preparing for Teradata Database on AWS Storage Considerations Storage Type Amazon Simple Storage Service (S3) Intended Use Case Back up and restore your Teradata Database using Teradata DSU Specific storage options for Teradata Database on AWS depend on product and instance type. For information on AWS storage, see Amazon User Guide for Linux Instances. Local Storage Local storage is temporary or ephemeral, but provides better performance compared to EBS storage. Local storage is ideal for testing and development where you do not need to keep data. Local storage uses SSD or HDD media. Although local storage is used for the data disk, the root disk uses 350 GB EBS. A minimal charge occurs at the time you launch any instance that uses a root disk. To avoid data loss, launch a Teradata Database instance from an EBS-based AMI, or use an automated Teradata backup solution such as Teradata Data Stream Utility. Data loss does not occur with certain node events, such as a reboot (init 6) or node panic (oops event); however, data loss does occur with the following node events: Shutdown (init 0) Node hang Machine check (hardware fault such as a double bit memory error) Stop the instance through the Amazon EC2 Console Terminate an instance EBS Storage With EBS storage, the root volume for a Teradata Database on AWS instance and additional EBS volumes that you attach to the instance persist by default. Unless you set attached volumes to delete on termination, all data remains and storage-related charges continue to accrue. You can enable EBS storage deletion either when configuring an instance (see Launching an Instance Using Manual Launch) or after launching an instance (see Setting EBS Storage for Deletion on Instance Termination). For Teradata Database, only the m4.4xlarge, m4.10xlarge, and m4.16xlarge instance types on AWS support EBS storage. Instance types supporting EBS storage may vary across other Teradata Database on AWS products. If you are launching Teradata Database MPP instances, Teradata recommends using either the m4.4xlarge, m4.10xlarge, or m4.16xlarge instance types. Since Teradata Database runs at the speed of the slowest node, using any of these EBS optimized instance types is important to get the maximum EBS volume bandwidth for your instance. For more information on EBS storage, see Amazon EBS Product Details. 28 Teradata Database on AWS Getting Started Guide

29 S3 Storage Chapter 2: Preparing for Teradata Database on AWS Storage Considerations Teradata Database on AWS supports S3 storage if you are using Teradata DSU to back up and restore your Teradata Database. Teradata DSU supports both EBS and S3 storage. For more information, see Backup and Restore Using Data Stream Utility. Teradata Database Storage EBS storage requires an M series instance type. Local storage requires an I or D series instance type. For more information on instance types, see Supported Instance Types. Teradata Database EBS Storage Options EBS storage for Teradata Database requires an M series instance type. Throughput varies with instance type, and each instance type provides two levels of total storage capacity: 5 TB and 20 TB, all with a 350 GB root disk. Instance Type Media Storage Configuration m4.4xlarge SSD 20 x 250 GB 2,000 m4.4xlarge SSD 20 x 1 TB 2,000 m4.10xlarge SSD 20 x 250 GB 4,000 m4.10xlarge SSD 20 x 1 TB 4,000 m4.16xlarge SSD 20 x 250 GB 10,000 m4.16xlarge SSD 20 x 1 TB 10,000 EBS Throughput (Mbps) Teradata Database Local Storage Options Local storage for Teradata Database requires an I or D series instance type. Media type varies based on instance series, and total storage capacity varies based on instance type. Instance Type Media Storage Configuration (GB) i2.xlarge SSD 1 x 800 i2.2xlarge SSD 2 x 800 i2.4xlarge SSD 4 x 800 i2.8xlarge SSD 8 x 800 d2.xlarge HDD 3 x 2000 d2.2xlarge HDD 6 x 2000 d2.4xlarge HDD 12 x 2000 d2.8xlarge HDD 24 x 2000 Teradata Database on AWS Getting Started Guide 29

30 Chapter 2: Preparing for Teradata Database on AWS AWS Service Limits Supporting Software Storage Supporting software for Teradata Database requires EBS storage on AWS, regardless of product and instance type. Teradata Database on AWS also supports S3 storage if you are using Teradata DSU to back up and restore your Teradata Database. Software Instance Type Storage Type Storage Configuration Teradata Data Mover Teradata Data Stream Utility m4.xlarge m4.2xlarge m4.4xlarge m4.10xlarge m4.2xlarge m4.4xlarge m4.10xlarge EBS EBS Root: 350 GB Data: 350 GB (2 x 175) Root: 350 GB Data: 350 GB (2 x 175) Teradata Ecosystem Manager m4.2xlarge EBS Root: 350 GB Data: 512 GB (2 x 256) Teradata REST Services t2.large EBS Root: 350 GB Teradata Server Management m4.xlarge EBS Root: 28 GB Teradata Viewpoint m4.2xlarge EBS Root: 350 GB Data: 512 GB (2 x 256) For more information on instance types, see Supported Instance Types. AWS Service Limits When you create your AWS account, AWS sets default service limits on certain resources on a per-region basis. Before launching instances, check the limits to determine if any should be increased especially for EBS, EC2 instances, and VPC elastic IP address limits. Plan to request limit increases in advance of the time that you need them. AWS has a limit on how much EBS storage an account can use. The default value is 20 TiB in each region. Before launching a Teradata Database instance, you may need to increase the EBS limits for the General Purpose (SSD) volume storage. You must increase the EBS limits in your default region as well as in any other regions where you want to launch additional Teradata Database AMIs. Before launching a multi-node Teradata Database instance, you should increase the instance limits to sufficiently meet your needs. For larger multi-node systems, the launch may still fail after you increase the EBS and instance limits because AWS does not have sufficient resources available in your region and availability zone at the time you launched. To solve this issue, try launching again a short time later. Teradata recommends increasing the instance limits to one more than the size of the system to support the Node Failure Recovery process. If you want to leave the downed node running for diagnostic purposes, Teradata recommends increasing the instance limits even further to two or more. 30 Teradata Database on AWS Getting Started Guide

31 Increasing AWS Service Limits Chapter 2: Preparing for Teradata Database on AWS Supported Instance Types The following procedure is for increasing EBS, EC2 instances, and VPC elastic IP address limits, but can be applied to increasing any AWS service limit. For more information on Amazon EC2 service limits, see Amazon User Guide for Linux Instances. 1. From the EC2 Console, click Limits. 2. Do one of the following:. Under EBS Limits, locate the General Purpose (SSD) volume storage. Under Instance Limits, locate the instance for which you want to increase the limit. 3. Under Action, click Request limit increase. The Support Center opens and the Create Case page displays. 4. Do the following to create a case: a) [Optional] For CC, enter the addresses of people to be notified when the status of the case changes. If you are signed in as an IAM user, include your own address. If you are signed in with your address and password, you do not need to include your address. b) For Regarding, select Service Limit Increase. c) For Limit Type, do one of the following: Select EBS. Select EC2 Instances. Select EC2-VPC Elastic IPs. d) Select or search for the region where you want to apply this change. e) [Optional] Click Add another request if you want to increase the limits in other regions if you are launching additional Teradata Database AMIs. f) For Use Case Description, type the limit you are requesting and the reason you need the increase. Ensure your description is as detailed as possible and includes information that is beneficial to the Amazon Service Team. Depending on how large of increase you are requesting, it may take extra time for the Amazon Service Team to approve your request. For example, if you are requesting an EBS limit increase from 20 TiB to 200 TiB, it may take around hours for your request to be approved. g) For Support Language, select your language. h) For Contact method, select the way you want to be contacted. i) Click Submit. A summary with a Case ID number is sent to you. You will receive additional notifications when the limit has been approved or if the Amazon Service Team needs more information. Supported Instance Types Some Teradata Database on AWS products support multiple instance types. Before launching an instance, select an instance type that suits your needs. Teradata Database on AWS Getting Started Guide 31

32 Chapter 2: Preparing for Teradata Database on AWS Supported Instance Types Teradata Database EBS Storage Instance Type Storage Configuration Virtual CPU Count Memory (GiB) EBS Throughput (Mbps) m4.4xlarge 20 x 250 GB , m4.4xlarge 20 x 1 TB , m4.10xlarge 20 x 250 GB , m4.10xlarge 20 x 1 TB , m4.16xlarge 20 x 250 GB , m4.16xlarge 20 x 1 TB , AMP Count Teradata Database Local SSD Storage Instance Type Storage Configuration (GB) Virtual CPU Count Memory (GiB) AMP Count i2.xlarge 1 x i2.2xlarge 2 x i2.4xlarge 4 x i2.8xlarge 8 x Teradata Database Local HDD Storage Instance Type Storage Configuration (GB) Virtual CPU Count Memory (GiB) AMP Count d2.xlarge 3 x d2.2xlarge 6 x d2.4xlarge 12 x d2.8xlarge 24 x Supporting Software EBS Storage Software Instance Type Virtual CPU Count Memory (GiB) Network Performance Teradata Data Mover m4.xlarge m4.2xlarge m4.4xlarge High High High 32 Teradata Database on AWS Getting Started Guide

33 Software Teradata DSU Instance Type Virtual CPU Count Memory (GiB) Network Performance m4.10xlarge Very High (10 Gigabit Ethernet) m4.2xlarge m4.4xlarge m4.10xlarge Teradata Ecosystem Manager m4.2xlarge 8 32 High High High Very High (10 Gigabit Ethernet) Teradata REST Services t2.large 2 8 Low to Moderate Teradata Server Management m4.xlarge 4 16 High Teradata Viewpoint m4.2xlarge 8 32 High Chapter 2: Preparing for Teradata Database on AWS Database Templates Database Templates Whether you launch a Teradata Database instance on AWS separately using the CloudFormation option or as part of a Teradata Ecosystem, the instance is based on a template. Templates contain the information and configuration options to create a Teradata Database single-node instance or a Teradata Database MPP instance up to 64 nodes on AWS without the need for additional configuration after launch. Templates determine the storage type (local storage or EBS storage) and the database size per node for EBS storage. You select how much storage per instance in the template. The following table lists the CloudFormation templates available on the AWS Marketplace for launching a Teradata Database instance without other Teradata products. These templates contain similar database configuration options to those in the Teradata Ecosystem CloudFormation templates available through To see a database deployment illustration of the AWS Marketplace templates, see Database Deployment Illustration. AWS CloudFormation Template Name Teradata Database - existing VPC Teradata Database - new VPC Supported Instance Type m4.4xlarge m4.10xlarge m4.16xlarge i2.xlarge i2.2xlarge i2.4xlarge i2.8xlarge d2.xlarge d2.2xlarge d2.4xlarge d2.8xlarge m4.4xlarge m4.10xlarge m4.16xlarge i2.xlarge Teradata Database on AWS Getting Started Guide 33

34 Chapter 2: Preparing for Teradata Database on AWS Database Templates AWS CloudFormation Template Name Supported Instance Type i2.2xlarge i2.4xlarge i2.8xlarge d2.xlarge d2.2xlarge d2.4xlarge d2.8xlarge To launch a Teradata Database instance on AWS, you must subscribe to the applicable Teradata Database product: For a Teradata Ecosystem launch, For a CloudFormation launch, the AWS Marketplace 34 Teradata Database on AWS Getting Started Guide

35 Database Deployment Illustration Chapter 2: Preparing for Teradata Database on AWS Database Templates Local SSD / Local HDD / AWS EBS Teradata Database Data Volumes #1 #2... #n Teradata Database Computation Nodes Other Teradata Apps Database Subnet /16 VPC /16 AWS Virtual Private Cloud VPC peering Apps in other VPC AWS Internet Gateway General Client Teradata Database on AWS Getting Started Guide 35

36 Chapter 2: Preparing for Teradata Database on AWS Database Templates 36 Teradata Database on AWS Getting Started Guide

37 CHAPTER 3 Launching a Teradata Ecosystem Teradata Ecosystem Overview Teradata Ecosystem allows you to launch multiple Teradata software products simultaneously on AWS. You initiate a Teradata Ecosystem launch from where you select from several options of multiple Teradata products. Each Teradata Ecosystem option links to an AWS CloudFormation template hosted on Amazon S3. Note: You cannot launch a Teradata Ecosystem directly from the AWS CloudFormation templates on the AWS Marketplace. The following table indicates the software product links for each Teradata Ecosystem on Teradata Ecosystem Software Product Links Test and Development Teradata Database Enterprise Edition (1-64 Nodes) Teradata Viewpoint (Single Teradata System) Minimum Production Teradata Database Enterprise Edition (1-64 Nodes) Teradata Viewpoint (Single Teradata System) Teradata Server Management Teradata Data Stream Utility Full Production Teradata Database Enterprise Edition (1-64 Nodes) Teradata Viewpoint (Single or Multiple Teradata Systems) Teradata Server Management Teradata Data Stream Utility Teradata Data Mover Teradata Ecosystem Manager Teradata REST Services You cannot add or remove software products from a Teradata Ecosystem. If the Teradata Ecosystem does not include the software products you want, you can launch instances for those products separately, which may require additional configuration after launch. For more information, see Launching Teradata Components Separately. Teradata Database on AWS Getting Started Guide 37

38 Chapter 3: Launching a Teradata Ecosystem Launching a Teradata Ecosystem Launching a Teradata Ecosystem Prerequisite The IAM user must have permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles. Also, check if AWS service limits need to be increased, particularly for EBS, EC2 instances, and VPC elastic IP address limits. For more information, see AWS Service Limits. From you can launch multiple Teradata software products simultaneously, collectively known as a Teradata Ecosystem, with a Teradata Database instance up to 64 nodes. You are given the option to create a placement group in this procedure. 1. From determine the Teradata Ecosystem you want to deploy. For a list of products in each Teradata Ecosystem, see Teradata Ecosystem Overview. 2. For the Teradata Ecosystem you want to deploy, subscribe to each software product by clicking on the corresponding link and following the instructions on the AWS Marketplace. You will receive a welcome for each product. 3. From select one of the following links: Teradata Ecosystem Link Test and Development Launch with Existing VPC Launch with New VPC Minimum Production Launch with Existing VPC Launch with New VPC Full Production Launch with Existing VPC Launch with New VPC After selecting a link, you are redirected to the AWS CloudFormation console. 4. Select a Region from the menu located in the upper right in the console. The Select Template page appears and the template URL is automatically specified under Specify an Amazon S3 template URL. 5. Click Next. 6. Under Specify Details, type a stack name. Note: The stack name must be unique to your region or the launch will fail. 7. Under Parameters, specify the following values: Parameter Category Parameter Name Action Teradata Database System Name Enter a Teradata Database system name. System Nickname DBC Password Enter the system nickname used to monitor Teradata instances in Teradata Viewpoint. Enter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password. 38 Teradata Database on AWS Getting Started Guide

39 Chapter 3: Launching a Teradata Ecosystem Launching a Teradata Ecosystem Parameter Category Parameter Name Action Number of Nodes Enter the number of nodes (1 to 64) you want to launch for this stack. Instance and Storage Type EBS Encryption Japanese Support Elastic IPs Select an instance type for the storage type you want. The storage size is per node. For more information, see Supported Instance Types. Do one of the following: Select Yes to encrypt your EBS volumes. Select No to not encrypt your EBS volumes. This parameter encrypts only the Teradata data disks and not the root drive. For more information on Amazon EBS encryption, see the Amazon User Guide for Linux Instances. Select yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is no. Select if you want to allocate an elastic IP address to each node. These will not be deleted when the stack is removed. Recommended for Minimum Production and Full Production Teradata Ecosystems. See Elastic IP Addresses. Date and Time NTP Servers Enter the NTP servers, separated by commas. System Timezone VPC/Network VPC Do one of the following: [Optional] Enter the operating system time zone of the database system. The default is the timezone of the AWS region. If you selected the template for an existing VPC, search or select a virtual private cloud in which the system will be launched. If you selected the template for a new VPC, enter a CIDR block for the VPC. The template creates a new VPC and a new subnet using this CIDR address. The block must have enough IP address space to support the configuration you choose to launch. Typically, a /16 CIDR is a good choice for this parameter. For example: /16. For more information, see Ecosystem Subnet below. Check to ensure the CIDR address you enter is not being used by existing VPCs by going to the AWS Web Console. Under Networking, select VPC. Under Resources, select VPCs. Check the CIDR column. Teradata Database on AWS Getting Started Guide 39

40 Chapter 3: Launching a Teradata Ecosystem Launching a Teradata Ecosystem Parameter Category Parameter Name Action Availability Zone Ecosystem Subnet Placement Group If you selected the template for a new VPC, search or select an availability zone in which to launch the stack. If you selected the template for an existing VPC, select a subnet to use for the ecosystem. Ensure the subnet you select has a sufficient number of IPs available. The Teradata Database MPP instances require two IPs per node and other Teradata Ecosystem products also need IPs in this subnet. For example, the Full Production Teradata Ecosystem can have up to 9 instances which would mean 9 additional IPs. Also, all AWS subnets have 5 IPs reserved for internal use. For more information, 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. Do one of the following: If you selected the template for an existing VPC, do one of the following: Enter the name of the existing placement group. Leave it blank to not use a placement group. If you selected the template for a new VPC, do one of the following: Select Yes to create a placement group. Select No if you do not want to use a placement group. Security Group Remote Access From Enter an CIDR address (public IP address) of your security group to lock down SSH and enable access to the Teradata Database nodes. For more information, see Security Groups and Ports. Key Pair AWS Key Pair Enter or select the key pair to ssh into for the instances. Teradata Server Management [Minimum and Full Production Teradata Ecosystems] Teradata DSU [Minimum and Full Production Teradata Ecosystems] Admin Password SM REST Password Site Id Instance Type Type the Server Management Administrative password. Type the Server Management REST password. Type the Site ID to be used when connecting to the Teradata Database. If you do not have the Site ID, you can continue without it, and add it later. See Site IDs. Select an instance type. 40 Teradata Database on AWS Getting Started Guide

41 Chapter 3: Launching a Teradata Ecosystem Launching a Teradata Ecosystem Parameter Category Parameter Name Action Teradata Data Mover [Full Production Teradata Ecosystems] Instance Type Additional Agents DATAMOVER Password DBC Password Select an instance type. Enter the the number of additional agents (nodes) you want to launch in this stack from 0 to 3. One node is already included for the master. Enter the password used to access the internal DATAMOVER repository. Enter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password. 8. Click Next. The Options page appears. 9. [Optional] Under Tags, specify up to 10 unique key-value pairs for resources in your stack, allowing you to search at a later time for the resources you launched. 10. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy. You can click Learn more to get more information. Change the Rollback on failure setting to Yes if you need to troubleshoot. 11. Click Next. The Review page appears. 12. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom. 13. Click Create to create the stack. This process can take anywhere between several minutes up to an hour depending on your configuration. Note: Trying to ssh into the instance may cause the creation of the stack to fail. Do not try to ssh into the instance until either CREATE_COMPLETE displays in the Status column or you receive a failure notification. 14. [Optional] To monitor the stack creation progress, do the following: a) From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Status column. b) After the stack is created, ensure CREATE_COMPLETE displays in the Status column. c) From the AWS EC2 Console, click Instances in the left column and ensure your instances are listed under the Name column. The name appears as the stack name followed by the node name. 15. [Optional] To ssh into the system with the public IP/DNS of any of the nodes, type the following command: ssh -i private-key-file ec2-user@instance-dns-name or IP-address After the stack is created, Teradata Database is ready and is started. No additional configuration is required. You do not need to run tdc-init or tdc-start. Teradata Database on AWS Getting Started Guide 41

42 Chapter 3: Launching a Teradata Ecosystem Launching a Teradata Ecosystem 42 Teradata Database on AWS Getting Started Guide

43 CHAPTER 4 Launching Teradata Components Separately Launch Paths Although we recommend launching a Teradata Ecosystem on AWS, you can alternatively use the CloudFormation, Manual Launch, or 1-Click Launch option to deploy Teradata components separately. Launch Option CloudFormation Manual Use Case Allows you to launch a Teradata Database MPP instance (up to 64 nodes), a Teradata Database single-node instance, or a Teradata Data Mover cluster (up to 4 agents) based on templates. Provides a choice of templates for launching a Teradata Database instance. For more information, see Database Templates. Provides a single template for launching a single Teradata Data Mover agent or a cluster of up to 4 agents. Requires no additional configuration after launching a Teradata Database instance and minimal configuration after launching a Teradata Data Mover instance. Gives you full control of all settings before launching Teradata product instances based on AMIs, but is more time-consuming than CloudFormation launch due to post-launch configuration requirements. Note: You cannot launch a Teradata Database instance using Manual. Involves additional configuration steps after instance launch. Allows you to launch 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, but requires you to manually set attached EBS storage volumes for deletion. For more information, see EBS Storage. Provides for launching of instances in placement groups and availability zones other than the default. Certain Teradata Database on AWS software benefits particularly from inclusion in placement groups. For more information, see Placement Groups. Requires some knowledge in setting up an instance. 1-Click Easiest and fastest way to launch a single instance of Teradata products. Requires minimum configuration. Teradata Database on AWS Getting Started Guide 43

44 Chapter 4: Launching Teradata Components Separately Launching Teradata Database Using CloudFormation Launch Option Use Case Note: You cannot launch a Teradata Database instance using 1-Click. Allows you to launch a single AWS instance from one AMI with predefined settings recommended by Teradata. Can use only the predefined Teradata instance types. Presents difficulty modifying some settings after the instance is launched. Cannot modify the predefined storage size and type. Automatically sets EBS storage volumes for deletion on instance termination. Does not provide for launching of instances in Placement Groups and Availability Zones other than the default. Available launch options depend on product. For more information see Launch Options. In all cases, be sure to launch a Teradata Database instance before deploying instances of other Teradata products. For more information on launching an instance, see Subscribing, Launching, and Managing Products at Launch Options Available options for launching Teradata components separately on AWS depend on product. Product Teradata Database Teradata Data Mover Teradata Server Management CloudFormation Launch Manual Launch 1-Click Launch Yes (single-node or MPP up to 64 nodes, single instance) Yes (1- to 4-agent, single instance) No Yes (single-node, single or multiple instances) No Yes (single instance) No Yes Yes (single instance) Other Teradata Products No Yes (single or multiple instances) Yes (single instance) Launching Teradata Database Using CloudFormation Prerequisite Depending on your account settings, check to ensure the IAM user has permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles. Check if AWS service limits need to be increased, particularly for EBS, EC2 instances, and VPC elastic IP address limits. See AWS Service Limits. 44 Teradata Database on AWS Getting Started Guide

45 Complete these steps to launch a Teradata Database system based on CloudFormation templates when deploying Teradata components separately on AWS. You can launch a Teradata Database instance up to 64 nodes. You are given the option to create a placement group in this procedure. 1. From the AWS Marketplace, locate the AMI from which you want to launch the instance: New users: In the Search box, type Teradata. Returning users: Click Your Software, in the upper-right corner. A list of AMIs appears. 2. Select Teradata Database MPP Cloud+ Edition (1-64 Nodes): New users: Click the link. Returning users: Beside the listing, click Launch more software. 3. On the product summary page, click Continue. 4. Click the Custom Launch tab. 5. For new users, click Accept Software Terms. 6. Under Select a Version, select the release version from which to launch the instance. 7. Under Select a Region select a Region. For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations. 8. Under Deployment Options, select one of the following deployment options: Teradata Database - existing VPC Teradata Database - new VPC For more information, see Database Templates. 9. Under Launch, click Launch with CloudFormation Console. The Select Template page appears and the template URL is automatically specified under Specify an Amazon S3 template URL based on your selection at the previous step. 10. Click Next. 11. Under Specify Details, type a stack name. Note: The stack name must be unique to your region or the launch will fail. 12. Under Parameters, specify the following values for the Teradata Database instance: Parameter Category Parameter Name Action Chapter 4: Launching Teradata Components Separately Launching Teradata Database Using CloudFormation Teradata Database System Name Enter a Teradata Database system name. DBC Password Japanese Support NTP Servers Enter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password. Select yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is no. Enter the NTP servers, separated by commas. Teradata Database on AWS Getting Started Guide 45

46 Chapter 4: Launching Teradata Components Separately Launching Teradata Database Using CloudFormation Parameter Category Parameter Name Action System Timezone [Optional] Enter the operating system time zone of the database system. The default is the timezone of the AWS region. Node Configuration Number of Nodes Enter the number of nodes (1 to 64) you want to launch for this stack. Instance and Storage Type EBS Encryption Select an instance type for the storage type you want. The storage size is per node. For more information, see Supported Instance Types. Do one of the following: Select Yes to encrypt your EBS volumes. Select No to not encrypt your EBS volumes. VPC/Network VPC Do one of the following: This parameter encrypts only the Teradata data disks and not the root drive. For more information on Amazon EBS encryption, see the Amazon User Guide for Linux Instances. If you selected the template for an existing VPC, search or select a virtual private cloud in which the system will be launched. If you selected the template for a new VPC, enter a CIDR block for the VPC. The template creates a new VPC and a new subnet using this CIDR address. The block must have enough IP address space to support the configuration you choose to launch. Typically, a /16 CIDR is a good choice for this parameter. For example: /16. For more information, see Database Subnet below. Check to ensure the CIDR address you enter is not being used by existing VPCs by going to the AWS Web Console. Under Networking, select VPC. Under Resources, select VPCs. Check the CIDR column. Availability Zone Database Subnet If you selected the template for a new VPC, search or select an availability zone in which to launch the stack. If you selected the template for an existing VPC, 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. For more information, see VPC and Subnet Sizing in the Amazon Virtual Private Cloud User Guide. 46 Teradata Database on AWS Getting Started Guide

47 Chapter 4: Launching Teradata Components Separately Launching Teradata Database Using CloudFormation Parameter Category Parameter Name Action 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. Placement Group Do one of the following: If you selected the template for an existing VPC, do one of the following: Enter the name of the existing placement group. Leave it blank to not use a placement group. If you selected the template for a new VPC, do one of the following: Select Yes to create a placement group. Select No if you do not want to use a placement group. Security Group Elastic IPs Remote Access From Select if you want to allocate an elastic IP address to each node. These will not be deleted when the stack is removed. Recommended for Minimum Production and Full Production Teradata Ecosystems. See Elastic IP Addresses. Enter an CIDR address (public IP address) of your security group to lock down SSH and enable access to the Teradata Database nodes. When launching a Teradata Database MPP instance, add the private IP addresses of Teradata software instances for any TCP port ranges you are using from For a list of software this applies to, see Security Groups for Teradata Database. Key Pair AWS Key Pair Enter or select the key pair to ssh into for the instances. 13. Click Next. The Options page appears. 14. [Optional] Under Tags, specify up to 10 unique key-value pairs for resources in your stack, allowing you to search at a later time for the resources you launched. 15. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy. You can click Learn more to get more information. 16. Click Next. The Review page appears. 17. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom. 18. Click Create to create the stack. This process can take anywhere between several minutes up to an hour depending on your configuration. Teradata Database on AWS Getting Started Guide 47

48 Chapter 4: Launching Teradata Components Separately Launching Teradata Data Mover Using CloudFormation Note: Trying to ssh into the instance may cause the creation of the stack to fail. Do not try to ssh into the instance until either CREATE_COMPLETE displays in the Status column or you receive a failure notification. 19. [Optional] To monitor the stack creation progress, do the following: a) From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Status column. b) After the stack is created, ensure CREATE_COMPLETE displays in the Status column. c) From the AWS EC2 Console, click Instances in the left column and ensure your instances are listed under the Name column. The name appears as the stack name followed by the node name. 20. [Optional] To ssh into the system with the public IP/DNS of any of the nodes, type the following command: ssh -i private-key-file ec2-user@instance-dns-name or IP-address After the stack is created, Teradata Database is ready and is started. No additional configuration is required. You do not need to run tdc-init or tdc-start. Launching Teradata Data Mover Using CloudFormation Prerequisite Depending on your account settings, check to ensure the IAM user has permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles. Create a VPC, subnets, and a placement group if you are planning to use a placement group. For more information, see Quick Start. Check if AWS service limits need to be increased, particularly for EBS and EC2 instance limits. See AWS Service Limits. If you are deploying Teradata components separately on AWS, you can use a CloudFormation template to launch a single Teradata 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 Teradata Database systems and high Data Mover workload. For information on how to delete an AWS CloudFormation stack, see the AWS CloudFormation Documentation. 1. From the AWS Marketplace, locate the AMI from which you want to launch the instance: New users: In the Search box, type Teradata. Returning users: Click Your Software, in the upper-right corner. A list of AMIs appears. 2. Select Teradata Data Mover. New users: Click the link. Returning users: Beside the listing, click Launch more software. 3. On the product summary page, click Continue. 4. Click the Custom Launch tab. 5. For new users, click Accept Software Terms. 6. Under Select a Version, select the release version from which to launch the instance. 7. Under Select a Region select a Region. 48 Teradata Database on AWS Getting Started Guide

49 For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations. 8. Under Deployment Options, select Teradata Data Mover MPP system with EBS storage. 9. Under Launch, click Launch with CloudFormation Console. The Select Template page appears and the template URL is automatically specified under Specify an Amazon S3 template URL based on you selection at the previous step. 10. Click Next. 11. Under Specify Details, type a stack name. Note: The stack name must be unique to your region or the launch will fail. 12. Under Parameters, specify the following values for the Teradata Data Mover instance: Parameter Category Parameter Name Action Chapter 4: Launching Teradata Components Separately Launching Teradata Data Mover Using CloudFormation VPC Settings VPC Select a virtual private cloud in which the system will be launched. Availability Zone Subnet Remote Access From Placement Group for Data Mover Select an availability zone for the subnet that you select next. Select a subnet. Enter an CIDR address (public IP address) of your security group to lock down SSH and enable access the Data Mover nodes. For more information, see Security Groups and Ports. Check to ensure the CIDR address you enter is not being used by existing subnets in the same VPC by going to the AWS Web Console. Under Networking, select VPC. Under Resources, select Subnets. Check the CIDR column. [Optional] Enter a placement group name for Data Mover. Key Pair AWS Key Pair Enter a key pair to ssh into the instances. Teradata Data Mover Instance Type Additional Agents DBC Password DATAMOVER Password Select an instance type for the storage type you want. For more information, see Supporting Software EBS Storage. Enter the total number of additional agents (nodes) you want to launch in this stack (0 to 3). One agent is already included with the master. Enter a new default Teradata DBC password. For security reasons, we strongly recommend you change the default dbc password to a different password. Enter the new default DATAMOVER password used to access the internal DATAMOVER repository. For security reasons, we strongly recommend you change the default datamover password to a different password. Teradata Database on AWS Getting Started Guide 49

50 Chapter 4: Launching Teradata Components Separately Launching Teradata Data Mover Using CloudFormation Parameter Category Parameter Name Action System Timezone NTP Servers [Optional] Enter the operating system time zone of the database system. The default is the timezone of the AWS region. Enter the NTP servers, separated by commas. This enables the Data Mover cluster clock to be synced. 13. Click Next. The Options page appears. 14. [Optional] Under Tags, specify up to 10 unique key-value pairs for resources in your stack, allowing you to search at a later time for the resources you launched. 15. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy. You can click Learn more to get more information. You can change the Rollback on failure setting to No if you want to troubleshoot a stack failure. The default setting is Yes. 16. Click Next. The Review page appears. 17. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom. 18. Click Create to create the stack. This process can take anywhere between several minutes up to 45 minutes depending on your configuration. Note: Trying to ssh into the instance may cause the creation of the stack to fail. Do not try to ssh into the instance until either CREATE_COMPLETE displays in the Status column or you receive a failure notification. 19. [Optional] To monitor the stack creation progress, do the following: a) From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Status column. b) After the stack is created, ensure CREATE_COMPLETE displays in the Status column. c) From the AWS EC2 Console, click Instances in the left column and ensure your instances are listed under the Name column. The name appears as the stack name followed by the agent name and number. For example, a 4- node Data Mover cluster displays the following: Stackname-DM-Master-Agent1 Stackname-DM-Agent2 Stackname-DM-Agent3 Stackname-DM-Agent4 After the stack is created, Teradata Data Mover is ready and is started. No additional configuration is required. 50 Teradata Database on AWS Getting Started Guide

51 Data Mover Template Illustration Chapter 4: Launching Teradata Components Separately Launching an Instance Using Manual Launch Teradata Data Mover moves data between a data source and a target system. The target system can be a Teradata, Aster, or Hadoop system within AWS or on-premises. When launching Teradata Data Mover using CloudFormation, you can designate additional Data Mover agents (nodes). AWS VPC Viewpoint (Data Mover Portlet) Data Mover Agent Data Source Data Target Data Source/Target: Teradata Aster Hadoop Internet Gateway Data Source/Target (outside of AWS): Teradata Aster Hadoop Launching an Instance Using Manual Launch If you are deploying Teradata components separately on AWS, you can use the Manual Launch option. Before launching instances of other Teradata products, be sure to launch a Teradata Database instance using CloudFormation. You cannot use the Manual Launch option to deploy a Teradata Database instance. 1. From the AWS Marketplace, locate the AMI from which you want to launch the instance: New users: In the Search box, type Teradata. Returning users: Click Your Software, in the upper-right corner. A list of AMIs appears. 2. Select the preferred AMI: New users: In the list of AMIs, click the link for the preferred option. Returning users: Beside the preferred AMI, click Launch more software. A product summary page appears. 3. Review the product configuration options and pricing details, then click Continue. 4. Click Manual. Teradata Database on AWS Getting Started Guide 51

52 Chapter 4: Launching Teradata Components Separately Launching an Instance Using Manual Launch 5. At Select a Version, select the AMI version from which to launch the instance. 6. [Optional] To view cost information for running the instance in a region other than the default, select the region at Pricing Details under For region. For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations. 7. At Pricing Details under Hourly Fees, note the name of the EC2 Instance Type that you want to use. You will need this name to begin configuring the instance later in this procedure. 8. Click Launch with EC2 Console beside the Region in which you want to run the instance. The EC2 Console opens to the Step 2: Choose an Instance Type page. 9. Click beside the row listing the instance type you noted earlier, then click Next: Configure Instance Details. Launching instance types other than those that Teradata supports may result in the instance not launching. For more information, see Supported Instance Types. 52 Teradata Database on AWS Getting Started Guide

53 Chapter 4: Launching Teradata Components Separately Launching an Instance Using Manual Launch 10. On the Step 3: Configure Instance Details page, change the default settings for the following parameters: Parameter Auto-assign Public IP Network Action Select Enable. Select a different setting or click Create new VPC to run the instance in a network other than the default. For more information, see Virtual Private Cloud. 11. [Optional] Change the default settings for other instance parameters as follows: Setting Number of Instances Purchasing option Subnet Placement group Action Enter a value other than 1 to launch multiple instances from the same AMI. Select the check box to Request Spot Instances. Select a different setting or click the link to configure a new subnet to run the instance in an Availability Zone other than the default. For more information, see Region and Time Zone Considerations. Teradata Server Management instances (also known as CMIC instance) require use of the database subnet created by the Teradata Database. Select a setting other than No Placement Group to enable the instance to participate in a low-latency, 10 Gbps network. For more information, see Placement Groups. Note: Placement group appears when you request spot instances. Teradata Database on AWS Getting Started Guide 53

54 Chapter 4: Launching Teradata Components Separately Launching an Instance Using Manual Launch Setting IAM role Shutdown behavior Action Select a different setting or click the link to configure a new IAM role. Select a setting other than Stop. Note: The Shutdown behavior option is not displayed, if you selected Request Spot Instances. Enable termination protection Monitoring Tenancy Select the Protect against accidental termination check box. Select the Enable CloudWatch detailed monitoring check box. Select a setting other than Shared - Run a shared hardware instance. 12. Click Next: Add Storage. 13. [Optional] To set storage volumes to delete on instance termination, select all check boxes in the Delete on Termination column. Unless you set volumes to delete on termination, all data remains and storage-related charges continue to accrue. You can also enable this setting after launching the instance. For more information, see Setting EBS Storage for Deletion on Instance Termination. 14. Click Next: Tag Instance. 15. At Value, type a name for the instance. Naming the instance helps you identify it in the EC2 Management Console. 16. Click Next: Configure Security Group. 17. On the Step 6: Configure Security Group page, do one of the following: Action Configure a new security group Steps a. Select Create a new security group. b. Enter a Security Group Name. c. [Optional] Enter a Description. d. Configure the SSH rule, and click Add Rule to configure additional rules as required. 54 Teradata Database on AWS Getting Started Guide

55 Chapter 4: Launching Teradata Components Separately Launching an Instance Using 1-Click Launch Action Steps For more information, see Security Groups and Ports. Choose an existing security group a. Select Select an existing security group. b. Click beside the row listing the preferred security group. 18. Click Review and Launch. 19. Review the instance configuration summary information for accuracy, and click the applicable Edit link if you want to change settings before launching the instance. 20. Click Launch. The time required for an instance to launch varies because instance types come in various sizes with varying combinations of CPU, memory, storage, and networking capacity. 21. In the Select an existing key pair or create a key pair window, do one of the following, then click Launch Instances. Action Steps Select an existing key pair a. Select Choose an existing key pair. b. At Select a key pair, choose the preferred key pair. c. Click the acknowledgment. Create a key pair a. Select Create a new key pair. b. Enter a Key pair name. c. Enter a Download key pair. d. Save the key pair file to the preferred location. For more information, see Key Pairs. 22. Click to acknowledge that you have access to the private key pair file, then click Launch. 23. View your instances in the EC2 Management Console, and monitor the status of the instance launch. Spot Instances: If you requested spot instances, click View Spot Instances. Instances: Click View Instances. Postrequisite When the Instance State changes to running, complete the applicable procedure under Configuring Teradata Software for AWS. Launching an Instance Using 1-Click Launch If you are deploying Teradata components separately on AWS, you can use the 1-Click Launch option. Before launching instances of other Teradata products, be sure to launch a Teradata Database instance using CloudFormation. You cannot use the 1-Click Launch option to deploy a Teradata Database instance. 1. From the AWS Marketplace, locate the AMI from which you want to launch the instance: New users: In the Search box, type Teradata. Returning users: Click Your Software, in the upper-right corner. Teradata Database on AWS Getting Started Guide 55

56 Chapter 4: Launching Teradata Components Separately Launching an Instance Using 1-Click Launch A list of AMIs appears. 2. Select the preferred AMI: New users: In the list of AMIs, click the link for the preferred option. Returning users: Beside the preferred AMI, click Launch more software. A product summary page appears. 3. Select the type of launch. New users: Review the product configuration options and pricing details, and click Continue. On the Launch on EC2 page, click the 1-Click Launch tab. Returning users: On the Launch on EC2 page, click the 1-Click Launch tab. 4. [Optional] Before launching, review and modify the following settings: a) Expand Version, and select an AMI version. b) Expand Region, and select a region. For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations. c) Expand EC2 Instance Type, select an instance type, and review the displayed pricing and cost information. d) Expand VPC Settings, and select a VPC other than the default because the default VPC is open to the public. e) Expand Security Group, and configure a new or select an existing security group to set your firewall settings. For more information, see Security Groups and Ports. f) Expand Key Pair, and configure a new or select an existing key pair. For more information, see Key Pairs. 5. Launch the AMI. 56 Teradata Database on AWS Getting Started Guide

57 New users: Click Accept Terms & Launch with 1-Click. Returning users: Click Launch with 1-Click. Chapter 4: Launching Teradata Components Separately Launching an Instance Using 1-Click Launch The time required for an instance to launch varies because instance types come in various sizes with varying combinations of CPU, memory, storage, and networking capacity. A Software Installation Details message displays the configuration details for the instance being launched. 6. From the Software Subscriptions page, click Manage in AWS Console. 7. From the AWS console, assign a name to help you identify the instance: a) In the Name column of the instance, click. b) Enter the instance name. c) Click to save the name. Postrequisite When the Instance State changes to running, complete the applicable procedure under Configuring Teradata Software for AWS. Teradata Database on AWS Getting Started Guide 57