Deploying an Instance Using Manual Launch
PrerequisiteDeploy Teradata Database. See Deploying a Teradata Ecosystem Using AWS CloudFormation and Deploying Teradata Database Using AWS CloudFormation
If you are deploying Teradata components separately on AWS, some products can be deployed using Manual Launch.
- If you have not subscribed to the Teradata software, do so now.
- From the AWS Marketplace, select Your Marketplace Software from your account menu in the upper-right corner.A list of AMIs appears.
- Beside the preferred AMI, click Launch more software.A product summary page appears.
- Review the configuration options and pricing details, then click Continue.
- Click Manual.
- At Select a Version, select the AMI version from which to deploy the instance.
- [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.
- 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.
- 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.
- Click beside the row listing the instance type you noted earlier, then click Next: Configure Instance Details.Deploying instance types other than those that Teradata supports may result in the instance not deploying.
- 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 click Create new VPC to run the instance in a network other than the default.
- [Optional] Change the default settings for other instance parameters as follows:
Setting 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 click 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.NotePlacement group appears when you request spot instances. IAM role Select a different setting or click the link to configure a new IAM role. Shutdown behavior Select a setting other than Stop.NoteThe 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.
- Click Next: Add Storage.
- [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.
- Click Next: Tag Instance.
- At Value, type a name for the instance.Naming the instance helps you identify it in the EC2 Management Console.
- Click Next: Configure Security Group.
- On the Step 6: Configure Security Group page, do one of the following:
Action Steps Configure a new security group
- Select Create a new security group.
- Enter a Security Group Name and, if desired, a description.
- Configure the SSH rule, and click Add Rule to configure additional rules as required.
Choose an existing security group
- Select Select an existing security group.
- Click beside the row listing the preferred security group.
- Click Review and Launch.
- Review the instance configuration summary information for accuracy, and click the applicable Edit link if you want to change settings before deploying the instance.
- Click 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.
- In the Select an existing key pair or create a key pair window, select one of the following, then click Launch Instances.
- Choose an existing key pair
- Create a new key pair
- Click to acknowledge that you have access to the private key pair file, then click Launch.
- View your instances in the EC2 Management Console, and monitor the status of the instance deploy.
- Spot instances: If you requested spot instances, click View Spot Instances.
- Instances: Click View Instances.
PostrequisiteWhen the Instance State changes to running, complete the applicable procedure under Configuring Teradata Software for AWS