|Sign up for an AWS account.||See Sign Up for AWS under Setting Up in the Amazon User Guide for Linux Instances.|
|Learn about and create users and groups for identity and access management (IAM).||See Create an IAM User under Setting Up in the Amazon User Guide for Linux Instances.|
|Learn about and create one or more key pairs.||See Key Pairs.
To create a key pair, see Create a Key Pair under Setting Up in the Amazon User Guide for Linux Instances.
|Learn about and create a new VPC.||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.
|Learn about and create one or more security groups and learn which ports should be opened.||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.
|Learn about and create one or more subnets, if needed.||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.
Subnets must be set to auto-assign public IP addresses. See Enabling Auto-Assignment of Public IP Addresses for Subnets.
|Learn about elastic IP addresses if needed.||See Elastic IP Addresses if you plan to launch a Minimum Production or Full Production Teradata ecosystem.|
|Learn about placement groups, if needed.||See Placement Groups, especially if you want to launch Teradata Database MPP, Teradata Data Mover, and Teradata DSC instances. If you launch a Teradata ecosystem, you can create a placement group automatically.
To create a placement group, see Placement Groups under Network and Security in the Amazon User Guide for Linux Instances.
|Learn about time zones and availability zones.||See AWS Regions.
To learn more, see Regions and Availability Zones under What is Amazon EC2 in the Amazon User Guide for Linux Instances.
|Learn about when to use public IP/DNS addresses versus private IP/DNS addresses.||See Connection Considerations.
To learn more, see Instance IP Addressing under Network and Security in the Amazon User Guide for Linux Instances.
|Decide if you want temporary or persistent storage for your data.||See Storage Considerations, including the sub-topics in this section.
To learn more, see Storage in the Amazon User Guide for Linux Instances.
|Learn about available Teradata products.||See Supported Software for Teradata Database on AWS.|
|Learn about software purchase options.||You can purchase most Teradata software solutions by choosing either a Teradata IntelliSphere software bundle or individual software components.
You can purchase software from Teradata and bring that license to AWS or purchase from AWS on an hourly basis. In either case, you must subscribe to the software on AWS before you can deploy it. See:
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.
|Learn about BYOL.||You can purchase software directly from Teradata, then bring that license to AWS. See Bring Your Own License.|
|Learn about options for Teradata Database MPP instances.||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. See Node Failure Recovery.
|Decide how you want to deploy the Teradata software.||To learn about the recommended method of launching Teradata Database and multiple other Teradata software products simultaneously, see Teradata Ecosystem Overview. This method does not require additional configuration after launch.
To learn about launching Teradata products one at a time, see Methods for Launching Software Solutions Separately.
|Learn about AWS service limits and increase them in advance of the time that you need them.||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 administrative tasks||Learn about important topics to avoid incurring charges, including Stopping or Terminating Teradata Database Instances.|
|Register for Teradata Support.||When you subscribe to Teradata Database on AWS or Teradata IntelliSphere for the Teradata Base, Advanced, or Enterprise license tier, you receive a welcome email that enables you to register for support. After you complete the support registration, an email is sent within two business days containing your Master Customer Record, site ID, user ID, and password. See Site IDs.
Teradata support is available for all license tiers except Teradata Database Developer. Use the Teradata Community forum for community-driven customer support.
|Learn about Teradata Community forums.||The Teradata Community forum for Teradata Database on AWS offers community-driven support. See Links: Teradata on AWS.|
|Learn about using Teradata Database and its associated software.||See http://www.info.teradata.com for Teradata customer documentation. For example, see the Teradata Viewpoint User Guide to learn how to monitor Teradata Database.|