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. If you have not subscribed to the software, do so now.
  2. If you previously subscribed to the software, do the following:
    1. From the AWS Marketplace, select Your Marketplace Software from your account menu in the upper-right corner.
      A list of your software subscriptions appears.
    2. Click Launch More Software under the subscription name.
  3. Under Software Pricing, select your subscription term.
  4. Under Version, select the release version from which to launch the instance.
  5. Under Region select a Region.
    For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations.
  6. Under Deployment Options, select Teradata Data Mover MPP system with EBS storage.
  7. 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.
  8. Click Next.
  9. Under Specify Details, type a stack name.
    Note:
    The stack name must be unique to your region or the launch will fail.
  10. Under Parameters, specify the following values for the Teradata Data Mover instance:
    Parameter Category Parameter Name Action
    VPC Settings VPC Select a virtual private cloud in which the system will be launched.
    Availability Zone Select an availability zone for the subnet that you select next.
    Subnet Select a subnet.
    Remote Access From 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.

    Placement Group for Data Mover [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 Select an instance type for the storage type you want. For more information, see Supporting Software EBS Storage.
    Additional Agents 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.
    DBC Password Enter a new default Teradata DBC password. For security reasons, we strongly recommend you change the default dbc password to a different password.
    DATAMOVER 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.
    System Timezone [Optional] Enter the operating system time zone of the database system. The default is the timezone of the AWS region.
    NTP Servers Enter the NTP servers, separated by commas. This enables the Data Mover cluster clock to be synced.
  11. Click Next.
    The Options page appears.
  12. [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.
  13. [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.
  14. Click Next.
    The Review page appears.
  15. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  16. 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.
  17. [Optional] To monitor the stack creation progress, do the following:
    1. From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Status column.
    2. After the stack is created, ensure CREATE_COMPLETE displays in the Status column.
    3. 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.

results matching ""

    No results matching ""