Deploying Teradata Data Mover Using AWS CloudFormation

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 will use one.

Deploy Teradata Database before deploying Teradata Data Mover.

If you are deploying Teradata components separately on AWS, you can use AWS CloudFormation to deploy 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.
  1. If you have not subscribed to the software, do so now.
  2. From the AWS Marketplace, select Your Marketplace Software from your account menu.
    A list of your software subscriptions appears.
  3. Under the subscription name, click Launch More Software.
  4. Under Software Pricing, select your subscription term.
  5. Under Version, select the release version from which to deploy the instance.
  6. Under Region, select a region.
  7. Under Deployment Options, select Teradata Data Mover MPP system with EBS storage.
  8. 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.
  9. Click Next.
  10. Under Specify Details, type a stack name.
    The stack name must be unique to your region or the deployment will fail.
  11. Under Parameters, specify the following values for the Teradata Data Mover instance:
    Parameter CategoryParameter NameAction
    VPC SettingsVPCSelect a virtual private cloud in which the system is deployed.
    Availability ZoneSelect an availability zone for the subnet that you select next.
    SubnetSelect a subnet.
    Remote Access FromEnter an CIDR address (public IP address) of your security group to lock down SSH and enable access the Data Mover nodes.

    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 PairAWS Key PairEnter a key pair to SSH into the instances.
    Teradata Data MoverInstance TypeSelect an instance type for the storage type you want.
    Additional AgentsEnter the total number of additional agents (nodes) you want to deploy in this stack (0 to 3). One agent is already included with the master.
    DBC PasswordEnter a new default Teradata DBC password. For security reasons, we strongly recommend you change the default dbc password to a different password.
    DATAMOVER PasswordEnter 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 time zone of the AWS region.
    NTP ServersEnter the NTP servers, separated by commas. This enables the Data Mover cluster clock to be synchronized.
  12. Click Next.
  13. [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.
  14. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy.
    You can change the Rollback on failure setting to No if you want to troubleshoot a stack failure. The default setting is Yes.
  15. Click Next.
  16. Review the information and select the I acknowledge check box at the bottom.
  17. 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 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.
  18. [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, refer to Data Movement Using Teradata Data Mover to complete the configuration.

results matching ""

    No results matching ""