Deploying 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. See AWS Service Limits.

For BYOL, read Bring Your Own License before launching an ecosystem.

From http://www.teradata.com/aws/getting-started/, you can deploy multiple Teradata software products simultaneously, collectively known as a Teradata ecosystem. Each Teradata ecosystem option links to an AWS CloudFormation template hosted on Amazon S3.
Note
You cannot deploy a Teradata ecosystem directly from the AWS Marketplace.

This procedure provides options to encrypt your data volumes and the root disk using a default CMK.

  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 license tier you want to deploy, subscribe to the included software.
    You will receive a welcome email for each product.
  3. From http://www.teradata.com/aws/getting-started/, select one of the following links:
    Teradata EcosystemTierLink Text
    Test and Development
    • Teradata Database Enterprise
    • Teradata Database Advanced
    • Teradata Database Base
    • Launch
    • Launch with IntelliSphere
    • Launch BYOL
    • Launch BYOL with IntelliSphere
    • Teradata Database Developer
    • Launch
    Minimum Production
    • Teradata Database Enterprise
    • Teradata Database Advanced
    • Teradata Database Base
    • Launch
    • Launch with IntelliSphere
    • Launch BYOL
    • Launch BYOL with IntelliSphere
    Full Production
    • Teradata Database Enterprise
    • Teradata Database Advanced
    • Teradata Database Base
    • Launch
    • Launch with IntelliSphere
    • Launch BYOL
    • Launch BYOL with IntelliSphere
    Selecting a link takes you 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 unique stack name.
    Note
    The stack name must be unique to your region or the deployment will fail.
  7. Under Parameters, specify the following values:
    Parameter CategoryParameter NameAction
    Purchase Method [BYOL only]Entitlement IDEnter 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 of LicenseSelect one of the following for the license period:
    • 1 Year
    • 3 Year
    • 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 DatabaseVersionSelect the Teradata Database release version.
    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 to deploy for this stack.

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

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

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

    [Base, Advanced, Enterprise tiers only]

    Do one of the following:

    Note
    If you choose not to unfold during deployment, you can do so after deploying. 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 deploying 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 deploying. See Configuring COP Entries.

    • Select Unfolded-2x to deploy half of the EBS volumes, enabling you to later fold the system after deploying. See Folding a System.
    • Select Unfolded-4x to deploy a quarter of the EBS volumes, enabling you to later fold the system after deploying. See Folding a System.
    Data Storage

    [Base, Advanced, Enterprise tiers only]

    Enter the total node storage size from 5 to 60 TB per node for EBS instance types only.
    EBS Encryption

    [Base, Advanced, Enterprise tiers only]

    Do one of the following:
    • Select Yes to encrypt your EBS data volumes.
    • Select No to not encrypt your EBS data volumes.
    Root Disk Encryption

    [Base, Advanced, Enterprise tiers only]

    Do one of the following:
    • Select Yes to encrypt your root disk.
    • Select No to not encrypt your root disk.
    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 TemporalSelect yes to change the default setting to enable the Temporal database feature. The default setting is no.

    When enabled, temporal data is displayed in UTC time. If you must use a different time zone or enable daylight savings, contact Teradata Professional Services to schedule an appointment to enable the Temporal feature.

    Enable Secure ZonesSelect yes to change the default setting to enable the Secure Zones database feature. The default setting is no.
    Enable Row-Level SecuritySelect yes to change the default setting to enable the Row-Level Security database feature. The default setting is no.
    Enable Teradata Intelligent Memory [Advanced, 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.

    Date and TimeNTP Servers[Optional] Leave blank to use the default Amazon Time Sync Service local IP address. If you must use different NTP servers, enter the IP addresses separated by commas.
    System Timezone[Optional] Default: time zone of the AWS region. Can be changed to the operating system time zone of the database system.
    VPC/NetworkVPCSearch or select an existing virtual private cloud in which the system will be deployed.
    Ecosystem SubnetSelect 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.

    See 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 GroupEnter the name of an existing placement group. See Placement Groups.
    DSC Placement Group[Optional] Enter the name of an existing placement group. This can be the same placement group as the database. See Placement Groups.
    Data Mover Placement Group[Optional] Enter the name of an existing placement group. This can be the same placement group as the database. See Placement Groups.
    Security GroupRemote Access FromEnter a CIDR block to lock down SSH and enable access to the Teradata Database nodes. See Security Groups for Teradata Database.
    Key PairAWS Key PairEnter or select the key pair to SSH into for the instances.
    Teradata Server ManagementNumber of CMICsNumber of Server Management instances to deploy. Minimum for high availability: 2.
    Admin PasswordServer Management administrative password.
    REST PasswordServer Management REST password.
    Site Id [Base, Advanced, Enterprise tiers only]String that identifies this Teradata deployment for Teradata Customer Support (AMZTDB followed by up to 9 numbers). If you do not have a site ID, you can continue without it, and add it later. See Site IDs.
    Teradata DSC

    [Minimum and Full Production ecosystems only]

    Instance TypeSelect an instance type.
    Teradata Data Mover

    [Full Production ecosystems only]

    Instance TypeSelect an instance type.
    Additional AgentsNumber of additional agents (nodes) to deploy in this stack from 0 to 3. One node is already included for the master.
    DATAMOVER PasswordPassword 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 deployed.
  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.
  16. [BYOL only] If you receive licensing errors, see Licensing Issues.
  17. [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).
Postrequisite
[Optional] Some Teradata Database features require manual installation or configuration. See Teradata Database Features. Some Teradata software requires additional configuration. See Configuring Teradata Software for AWS.

results matching ""

    No results matching ""