Deploy an Instance Using Manual Launch | Teradata Vantage on AWS (DIY) - 2.2 - Deploying an Instance Using Manual Launch - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.2
Release Date
May 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2800-041K
Language
English (United States)
Some Teradata software can be deployed using Manual Launch if you are deploying the software separately from Vantage on AWS.
  1. If you have not already subscribed to the software you want to deploy, do so now.
  2. Log in to AWS Marketplace.
  3. From your account menu in the upper-right corner, select Your Marketplace Software.
  4. Select Launch More Software under the subscription name of the software you want to deploy.
  5. Review the configuration options and pricing details, then select Continue.
  6. Select Manual.
  7. At Select a Version, select the AMI version from which to deploy the instance.
  8. [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.
  9. 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.
  10. Select 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.
  11. Select "" beside the row listing the instance type you noted earlier, then select Next: Configure Instance Details.
    Deploying instance types other than those that Teradata supports may result in the instance not deploying.
  12. On the Step 3: Configure Instance Details page, change the default settings for the following parameters:
    Parameter Action
    Auto-assign Public IP Select Enable.
    Network Select a different setting or select Create new VPC to run the instance in a network other than the default.
  13. [Optional] Change the default settings for other instance parameters as follows:
    Settings Action
    Number of Instances Enter a value other than 1 to deploy multiple instances from the same AMI.
    Purchasing option Select the check box to Request Spot Instances.
    Subnet Select a different setting or select the link to configure a new subnet to run the instance in an Availability Zone other than the default.
    Placement group Select a setting other than No Placement Group to enable the instance to participate in a low-latency, 10 Gbps network.
    Placement group appears when you request spot instances.
    IAM role Select a different setting or select the link to configure a new IAM role.
    Shutdown behavior Select a setting other than Stop.
    The Shutdown behavior option is not displayed, if you selected Request Spot Instances.
    Enable termination protection Select the Protect against accidental termination check box.
    Monitoring Select the Enable CloudWatch detailed monitoring check box.
    Tenancy Select a setting other than Shared - Run a shared hardware instance.
  14. Select Next: Add Storage.
  15. [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 deploying the instance. See Setting EBS Storage for Deletion on Instance Termination.
  16. Select Next: Tag Instance.
  17. At Value, enter a name for the instance.
    Name the instance to help you identify it in the EC2 Management Console.
  18. Select Next: Configure Security Group.
  19. On the Step 6: Configure Security Group page, do one of the following:
    Action Steps
    Configure a new security group
    1. Select Create a new security group.
    2. Enter a Security Group Name and, if desired, a description.
    3. Configure the SSH rule, and select Add Rule to configure additional rules as required.
    Choose an existing security group
    1. Select Select an existing security group.
    2. Select "" beside the row listing the preferred security group.
  20. Select Review and Launch.
  21. Review the instance configuration summary information for accuracy, then select the applicable Edit link if you want to change settings before deploying the instance.
  22. Select Launch.
    The time required for an instance to deploy varies because instance types come in various sizes with varying combinations of CPU, memory, storage, and networking capacity.
  23. In the Select an existing key pair or create a key pair window, select one of the following, then select Launch Instances.
    • Choose an existing key pair
    • Create a new key pair
  24. Select "" to acknowledge that you have access to the private key pair file, then select Launch.
  25. View your instances in the EC2 Management Console, and monitor the status of the deploying instance.
    • Spot instances: If you requested spot instances, select View Spot Instances.
    • Instances: Select View Instances.
Postrequisite When the Instance State changes to running, complete the applicable procedure under Configuring Teradata Software on AWS .