Launching Teradata Database 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. Check if AWS service limits need to be increased, particularly for EBS, EC2 instances, and VPC elastic IP address limits. See AWS Service Limits.
Complete these steps to launch a Teradata Database system based on CloudFormation templates to deploy Teradata components separately on AWS. You can launch a Teradata Database instance up to 64 nodes for Teradata Database Base, Advanced, or Enterprise, and up to 2 nodes for Developer.

You are given the option to create a placement group in this procedure.

  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 Teradata Database 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 one of the following deployment options:
    • Teradata Database local/EBS storage - new VPC
    • Teradata Database local/EBS storage - existing VPC
    For more information, see Database Templates.
  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 your 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 Database instance:
    Parameter Category Parameter Name Action
    Teradata Database System Name Enter a Teradata Database system name.
    DBC Password Enter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password.
    Japanese Support Select yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is no.
    NTP Servers Enter the NTP servers, separated by commas.
    System Timezone [Optional] Enter the operating system time zone of the database system. The default is the timezone of the AWS region.
    Enable Secure Zones Select yes to change the default setting to enable the Teradata Secure Zones database feature. The default setting is no.
    Enable Row-level Security Select yes to change the default setting to enable the Teradata Row-Level Security database feature. The default setting is no.
    Node Configuration Number of Nodes Enter the number of nodes (1 to 64) you want to launch for this stack.

    Instance and Storage Type Select an instance type for the storage type you want. The storage size is per node. For more information, see Supported Instance Types.
    EBS Encryption Do one of the following:
    • Select Yes to encrypt your EBS volumes.
    • Select No to not encrypt your EBS volumes.
    Note:

    This parameter only applies to the Advanced and Enterprise tiers.

    This parameter encrypts only the Teradata data disks and not the root drive. For more information on Amazon EBS encryption, see the Amazon User Guide for Linux Instances.

    VPC/Network VPC Do one of the following:
    • If you selected the template for an existing VPC, search or select a virtual private cloud in which the system will be launched.
    • If you selected the template for a new VPC, enter a CIDR block for the VPC. The template creates a new VPC and a new subnet using this CIDR address. The block must have enough IP address space to support the configuration you choose to launch. Typically, a /16 CIDR is a good choice for this parameter. For example: 172.31.0.0/16. For more information, see Database Subnet below.

      Check to ensure the CIDR address you enter is not being used by existing VPCs by going to the AWS Web Console. Under Networking, select VPC. Under Resources, select VPCs. Check the CIDR column.

    Availability Zone If you selected the template for a new VPC, search or select an availability zone in which to launch the stack.
    Database Subnet If you selected the template for an existing VPC, select a subnet to use for the database.

    Ensure the subnet you select has a sufficient number of IPs available. The Teradata Database MPP instances require two IPs per node and all AWS subnets have 5 IPs reserved for internal use.

    For more information, see VPC and Subnet Sizing in the Amazon Virtual Private Cloud User Guide.

    Check that the subnet you choose has enough available IPs. From the AWS Web Console, under Networking, select VPC. Under Resources, select Subnets. Check the Available IPs column for that specific subnet.

    Placement Group Do one of the following:
    • If you selected the template for an existing VPC, do one of the following:
      • Enter the name of the existing placement group.
      • Leave it blank to not use a placement group.
    • If you selected the template for a new VPC, do one of the following:
      • Select Yes to create a placement group.
      • Select No if you do not want to use a placement group.
    Elastic IPs Select if you want to allocate an elastic IP address to each node.

    These will not be deleted when the stack is removed.

    Recommended for Minimum Production and Full Production Teradata ecosystems. See Elastic IP Addresses.

    Security Group Remote Access From Enter an CIDR address (public IP address) of your security group to lock down SSH and enable access to the Teradata Database nodes.

    When launching a Teradata Database MPP instance, add the private IP addresses of Teradata software instances for any TCP port ranges you are using from 0 - 65535. For a list of software this applies to, see Security Groups for Teradata Database.

    Key Pair AWS Key Pair Enter or select the key pair to ssh into for the instances.
  11. Click Next.
    The Options page appears.
  12. [Optional] Under Tags, specify up to 50 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 Permissions, select an IAM role.
    You can click Learn more to get more information.
  14. [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.
  15. Click Next.
    The Review page appears.
  16. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  17. Click Create to create the stack.
    This process can take anywhere between several minutes up to an hour 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.
  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 node name.
  19. [Optional] To ssh into the system with the public IP/DNS of any of the nodes, type the following command:
    ssh -i private-key-file ec2-user@instance-DNS-name or IP-address
    After the stack is created, Teradata Database is ready and is started. No additional configuration is required. You do not need to run tdc-init or tdc-start.

results matching ""

    No results matching ""