Launching a Teradata Ecosystem

Prerequisite
The IAM user must have permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles. Also, check if AWS service limits need to be increased, particularly for EBS, EC2 instances, and VPC elastic IP address limits. For more information, see AWS Service Limits.
From http://www.teradata.com/aws/getting-started/, you can launch multiple Teradata software products simultaneously, collectively known as a Teradata ecosystem, with a Teradata Database instance up to 64 nodes depending on the database license tier.

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

  1. From http://www.teradata.com/aws/getting-started/, determine the Teradata ecosystem you want to deploy. For a list of products in each Teradata ecosystem, see Teradata Ecosystem Overview.
  2. For the Teradata ecosystem you want to deploy, subscribe to each software product by clicking on the corresponding link and following the instructions on the AWS Marketplace.
    You will receive a welcome email for each product.
  3. From http://www.teradata.com/aws/getting-started/, select one of the following links:
    For a list of Teradata software included in each tier, see Teradata Database License Tiers.
    Teradata EcosystemTierLink Text
    Test and Development
    • Teradata Database Developer
    • Teradata Database Base
    • Teradata Database Advanced
    • Teradata Database Enterprise
    • Launch with Existing VPC
    • Launch with New VPC
    Minimum Production
    • Teradata Database Base
    • Teradata Database Advanced
    • Teradata Database Enterprise
    • Launch with Existing VPC
    • Launch with New VPC
    Full Production
    • Teradata Database Base
    • Teradata Database Advanced
    • Teradata Database Enterprise
    • Launch with Existing VPC
    • Launch with New VPC
    After selecting a link, you are redirected to the AWS CloudFormation console.
  4. Select a Region from the menu located in the upper right in the console.
    The Select Template page appears and the template URL is automatically specified under Specify an Amazon S3 template URL.
  5. Click Next.
  6. Under Specify Details, type a stack name.
    Note:
    The stack name must be unique to your region or the launch will fail.
  7. Under Parameters, specify the following values:
    Parameter CategoryParameter NameAction
    Teradata DatabaseVersionSelect the Teradata Database release version.

    New database versions may not be supported in all Teradata ecosystems.

    System NameEnter a Teradata Database system name.
    System NicknameEnter the system nickname used to monitor Teradata instances in Teradata Viewpoint.
    DBC PasswordEnter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password.
    Number of NodesEnter the number of nodes (1 to 64) you want to launch for this stack.
    Instance and Storage TypeSelect an instance type for the storage type you want. The storage size is per node. For more information, see Supported Instance Types.
    EBS EncryptionDo 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.

    Japanese SupportSelect yes to optimize the hashing algorithm to spread data across all AMPs when using Kanji characters for primary indexes. The default setting is no.
    Elastic IPsSelect 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.

    Enable Secure ZonesSelect yes to change the default setting to enable the Teradata Secure Zones database feature. The default setting is no.
    Enable Row-level SecuritySelect yes to change the default setting to enable the Teradata Row-Level Security database feature. The default setting is no.
    Date and TimeNTP ServersEnter 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.
    VPC/NetworkVPCDo 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 Ecosystem 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 ZoneIf you selected the template for a new VPC, search or select an availability zone in which to launch the stack.
    Ecosystem SubnetIf you selected the template for an existing VPC, select a subnet to use for the ecosystem.

    Ensure the subnet you select has a sufficient number of IPs available. The Teradata Database MPP instances require two IPs per node and other Teradata ecosystem products also need IPs in this subnet. For example, the Full Production Teradata ecosystem can have up to 9 instances which would mean 9 additional IPs. Also, 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 GroupDo 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.
    Security GroupRemote Access FromEnter an CIDR address (public IP address) of your security group to lock down SSH and enable access to the Teradata Database nodes.
    Key PairAWS Key PairEnter or select the key pair to ssh into for the instances.
    Teradata Server Management

    [Base, Advanced, and Enterprise tiers only]

    Number of CMICsSelect the number of CMIC instances to deploy (1 or 2).
    Admin PasswordType the Server Management Administrative password.
    SM REST PasswordType the Server Management REST password.
    Site IdType the Site ID to be used when connecting to the Teradata Database. If you do not have the Site ID, you can continue without it, and add it later. See Site IDs.
    Teradata DSC

    [Minimum and Full Production Teradata ecosystems]

    Select an instance type.
    Teradata Data Mover

    [Full Production Teradata ecosystems]

    Instance TypeSelect an instance type.
    Additional AgentsEnter the the number of additional agents (nodes) you want to launch in this stack from 0 to 3. One node is already included for the master.
    DATAMOVER PasswordEnter the password used to access the internal DATAMOVER repository.
    DBC PasswordEnter a new default Teradata Database password. For security reasons, we strongly recommend you change the default dbc password to a different password.
  8. Click Next.
    The Options page appears.
  9. [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.
  10. [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.
    Change the Rollback on failure setting to Yes if you need to troubleshoot.
  11. Click Next.
    The Review page appears.
  12. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  13. 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.
  14. [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.
  15. [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 ""