Launching Teradata Database Using CloudFormation

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.

For BYOL, read Bring Your Own License before launching Teradata Database.

Complete these steps to launch a Teradata Database system based on CloudFormation templates to deploy Teradata components separately on AWS.

This procedure provides an option to create a placement group.

This procedure provides an option to encrypt your data volumes. To encrypt the root drive, see Encryption.

  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 in the upper-right corner.
    A list of your software subscriptions appears.
  3. Click Launch MoreSoftware under the subscription name.
  4. Under Software Pricing,select your subscription term.
  5. Under Version, select the Teradata Database release version from which to launch the instance.
  6. Under Region, select aregion.
  7. Under Deployment Options, select Teradata Database local/EBS storage -existing VPC.
  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 based on your selection at the previous step.
  9. Click Next.
  10. Under Specify Details, type a stack name.
    The stack name must be unique to your region or the launch will fail.
  11. Under Parameters, specify the following values for the Teradata Database instance:
    Parameter Category Parameter Name Action
    Licensing [BYOL only] EID Enter the entitlement ID which is a unique string of characters that enable you to use the licensed software. Obtain the EID from the email you received when you purchased the license.
    Term Select one of the following for the license period:
    • 1Year
    • 3Year
    • POC: Short-term license (30, 60 or 90 days) used for a proof-of-concept

    Obtain the term from the email you received when you purchased the license.

    The term is visible as a suffix to the name in the Product column after you log in to the Teradata EMS server.

    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 time zone 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.
    Enable Teradata Intelligent Memory

    [Advanced and Enterprise tiers only]

    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.

      See the ctl utility in Utilities and the Teradata Intelligent Memory Orange Book.

    Node Configuration Number of NodesEnter the number of nodes to launch for this stack.

    The number of supported nodes depends on the license tier. See Teradata Database License Tiers.

    If you are launching into an unfolded state, your node count must be a multiple of 2 (2x) or a multiple of 4 (4x).

    Instance and Storage Type Select an instance type for the storage type you want. The storage size is per node. See Supported Instance Types.
    Fold / Unfold

    [Advanced and Enterprise tiers only]

    Do one of the following:
    If you choose not to unfold during launch, you can do so after launching. See Unfolding a System.
    • Select None to disable this feature (default).
    • Select Unfold-Ready to automatically allocate extra IP addresses from the subnet. This ensures the IP addresses used to connect to the Teradata Database for client connectivity do not change when the system is unfolded.

      The initial state for a system has 4 secondary IP addresses per node.

      The following examples are for launching a 4-node system:
      • When the system unfolds to 2x, then 8 nodes and 2 secondary IP addresses are assigned to each node.
      • When the system unfolds to 4x, then 16 nodes and 1 secondary IP address is assigned to each node.

      Clients will still use the same 16 IPs to connect to the Teradata Database system in both of the examples.

      If you do not select this option now, you can allocate IP addresses after launching. See Configuring COP Entries.

    • Select Unfolded-2x to launch half of the EBS volumes, enabling you to later fold the system after launching. See Folding a System.
    • Select Unfolded-4x to launch a quarter of the EBS volumes, enabling you to later fold the system after launching. See Folding a System.
    Data Storage [Advanced and Enterprise tiers only] Enter the total node storage size from 5 to 60 TB per node for EBS instance types only.
    EBS Encryption

    [Advanced and Enterprise tiers only]

    Do one of thefollowing:
    • Select Yes to encrypt your EBS data volumes.
    • Select No to not encrypt your EBS data volumes.
    VPC/Network VPC Search or select an existing virtual private cloud in which the system will be launched.
    Database Subnet 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.

    See VPC and Subnet Sizing inthe Amazon Virtual Private Cloud User Guide.

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

    Database Placement Group Do one of the following:
    • Enter the name of the existing placement group.
    • Leave it blank to not 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 a CIDR block to lock down SSH and enable access to the Teradata Database nodes. See Security Groups for Teradata Database.
    KeyPair AWS Key Pair Enter or select the keypair to SSH into for the instances.
  12. Click Next.
    The Options page appears.
  13. [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.
  14. [Optional] Under Permissions, select an IAM role.
    You can click Learn more to get more information.
  15. [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.
  16. Click Next.
    The Review page appears.
  17. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  18. Click Create to create the stack.
    This process can take anywhere between several minutes up to an hour 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.
  19. [Optional] To monitor the stack creation progress, do the following:
    1. From the AWS CloudFormation console, ensure CREATE_IN_PROGRESS displays in the Statuscolumn.
    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.
  20. [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.
  21. [BYOL only] If you receive licensing errors, see Licensing Issues.
  22. [BYOL only] Continuously monitor the AWS CloudWatch logs for errors, warnings, and alerts until you stop or terminate your instance.
    See Accessing AWS CloudWatch Logs (look for log group Teradata/DBS/stack-name and log stream telm_stack-name).
[Optional] Some Teradata Database features require manual installation or configuration. See Teradata Database Features.

results matching ""

    No results matching ""