Use the Planning Worksheet for Teradata Software for AWS to prepare details of the deployment.
Deploy Teradata Database before deploying other Teradata software.
Use this procedure to deploy Teradata Data Mover, Teradata Server Management, and Teradata Unity.
- Data Mover: If you are deploying Teradata components separately on AWS, you can use AWS CloudFormation to deploy a single 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.
- Server Management: Teradata Database supports multiple instances of Teradata Server Management (CMICs) in the public cloud to provide high availability and management of larger database systems. High availability requires at least two CMICs, each of which can manage up to 70 nodes. When you deploy multiple CMICs using AWS CloudFormation, the CMICs are automatically configured to communicate with each other. However, the newly deployed CMICs must be configured manually to manage the existing database and application nodes in the Teradata ecosystem.
- Unity: If you are deploying both of your Teradata Unity regions on AWS, then you must deploy each instance separately.
- If you have not already subscribed to the software you want to deploy, do so now.
- Log in to AWS Marketplace.
- From your account menu in the upper-right corner, select Your Marketplace Software.
- Click Launch More Software under the subscription name of the software you want to deploy.
-
Select an appropriate value under each of the following categories:
Category Action Software Pricing Select your subscription term. Software Version Select the release version from which to deploy the instance. Region Select a region. Deployment Options Select one of the following: - Teradata Data Mover MPP system with EBS storage
- Server Management in VPC for multi-app monitoring
- Teradata Unity MPP system with EBS storage
- Under Launch, click Launch with CloudFormation Console. The template URL is automatically specified under Specify an Amazon S3 template URL.
- Click Next.
- Under Specify Details, verify the stack name is unique to your region.
- Under Parameters, specify the values for the appropriate software and click Next. See Planning Worksheet for Teradata Software for AWS for the values you chose for the software you want to deploy.
- [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 deployed.
- [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy. To troubleshoot a stack failure, change the Rollback on failure setting to No. The default setting is Yes.
- Click Next.
- Review the information and select the I acknowledge check box at the bottom.
-
Click Create to create the stack.
This process can take up to 45 minutes, depending on your configuration.Trying to SSH into the instance may cause the stack creation 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.
-
[Optional] To monitor the stack creation progress, do the following:
- From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Status column.
- After the stack is created, ensure CREATE_COMPLETE displays in the Status column.
- From the AWS EC2 console, click Instances in the left column and ensure your instances are listed under the Name column.