Launching Teradata Database Using CloudFormation

Depending on your accountsettings, check to ensure the IAM user has permissions for AWS CloudFormation, IAMroles, IAM profiles, and instance profiles. Check if AWS service limits need to beincreased, particularly for EBS, EC2 instances, and VPC elastic IP address limits. SeeAWS Service Limits.
Complete these steps to launch aTeradata Database system based on CloudFormation templates to deploy Teradata componentsseparately on AWS. You can launch a Teradata Database instance up to 64 nodes forTeradata Database Base, Advanced, or Enterprise, and up to 2 nodes for Developer.

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

  1. If you have not subscribed to the software, do so now.
  2. If you previously subscribed to the software, do thefollowing:
    1. From the AWS Marketplace, select Your Marketplace Software from youraccount menu in the upper-right corner.
      A list of your software subscriptionsappears.
    2. Click Launch MoreSoftware under the subscription name.
  3. Under Software Pricing,select your subscription term.
  4. Under Version, select theTeradata Database release version from which to launch the instance.
  5. Under Region select aregion.
    For information on the implications of the region settingwith Teradata software, see Region and Time Zone Considerations.
  6. Under Deployment Options, select Teradata Database local/EBS storage - existing VPC.
    For more information, see Database Templates.
  7. Under Launch, clickLaunch with CloudFormationConsole.
    The Select Templatepage appears and the template URL is automatically specified under Specify an Amazon S3 template URL based on yourselection at the previous step.
  8. Click Next.
  9. Under Specify Details,type a stack name.
    The stack name must be unique to your region orthe launch will fail.
  10. Under Parameters,specify the following values for the Teradata Database instance:
    Parameter CategoryParameter NameAction
    Teradata DatabaseSystem NameEnter a Teradata Databasesystem name.
    DBC PasswordEnter a new defaultTeradata Database password. For security reasons, westrongly recommend you change the default dbc password to a differentpassword.
    Japanese SupportSelect yes to optimize the hashingalgorithm to spread data across all AMPs when using Kanjicharacters for primary indexes. The default setting isno.
    NTP ServersEnter the NTP servers,separated by commas.
    System Timezone[Optional] Enter theoperating system time zone of the database system. Thedefault is the timezone of the AWS region.
    Enable Secure ZonesSelect yes to change the defaultsetting to enable the Teradata Secure Zones databasefeature. The default setting is no.
    Enable Row-Level SecuritySelect yes to change the defaultsetting to enable the Teradata Row-Level Security databasefeature. The default setting is no.
    Enable Teradata Intelligent Memory Do one of the following:
    • To disable Teradata Intelligent Memory, leave the default cache percent as 0.
    • To enable Teradata Intelligent Memory, type a cache percent from 1 to 80 to specify the size of the hot cylinder cache as a percentage of FSG cache.

      For information, see the ctl utility in Utilities and the Teradata Intelligent Memory Orange Book.

    This parameter applies only to the Advanced and Enterprise tiers.
    Node ConfigurationNumber of NodesEnter the number of nodes(1 to 64) you want to launch for this stack.

    Instance and StorageTypeSelect an instance typefor the storage type you want. The storage size is per node.For more information, see Supported Instance Types.
    EBS EncryptionDo one of thefollowing:
    • Select Yes to encrypt your EBS volumes.
    • Select No to not encrypt your EBSvolumes.

    Thisparameter only applies to the Advanced andEnterprise tiers.

    Thisparameter encrypts only the Teradata data disks and notthe root drive. For more information on Amazon EBSencryption, see the Amazon User Guide for Linux Instances.

    VPC/NetworkVPCSearch or select an existing virtual private cloud in which the system will be launched.
    Database SubnetSelect 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.

    Database Placement GroupDo one of the following:
    • Enter the name of the existing placement group.
    • Leave it blank to not use a placement group.
    Elastic IPsSelect if you want toallocate an elastic IP address to each node.

    These will not be deleted when thestack is removed.

    Recommended forMinimum Production and Full Production Teradataecosystems. See Elastic IP Addresses.

    SecurityGroupRemote Access FromEnter a CIDR block to lock down SSH and enable access to the Teradata Database nodes. For more information, see Security Groups for Teradata Database.
    KeyPairAWS Key PairEnter or select the keypair to SSH into for the instances.
  11. Click Next.
    The Options pageappears.
  12. [Optional] Under Tags,specify up to 50 unique key-value pairs for resources in your stack, allowingyou to search at a later time for the resources you launched.
  13. [Optional] Under Permissions, select an IAM role.
    You can click Learnmore to get more information.
  14. [Optional] Under Advanced, set additional options for your stack, such asnotifications and a stack policy.
    You can click Learnmore to get more information.
  15. Click Next.
    The Review pageappears.
  16. Review the information carefully to ensure it is correct, andselect the standard AWS I acknowledgecheck box at the bottom.
  17. Click Create tocreate the stack.
    This process can take anywhere between several minutes up toan hour depending on your configuration.
    Trying to SSH into the instance may cause the creation of thestack to fail. Do not try to SSH into the instance until eitherCREATE_COMPLETE displaysin the Status column or you receive afailure notification.
  18. [Optional] To monitor the stack creation progress, do thefollowing:
    1. From the AWS CloudFormation console, ensureCREATE_IN_PROGRESSdisplays in the Statuscolumn.
    2. After the stack is created, ensure CREATE_COMPLETE displays in theStatus column.
    3. From the AWS EC2 Console, click Instances in the left column and ensureyour instances are listed under the Name column.
      The name appears as the stack name followed by thenode name.
  19. [Optional] To SSH into the system with the public IP/DNS ofany 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 readyand is started. No additional configuration is required. You do not need to runtdc-init or tdc-start.

results matching ""

    No results matching ""