Launching Teradata Server Management 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. For more information, see Quick Start. Check if AWS service limits need to be increased, particularly for EBS and EC2 instance limits. See AWS Service Limits.
If you are launching Teradata components separately on AWS, you can use CloudFormation to launch a single or multiple Server Management (CMIC) instances.

For information about how to delete an AWS CloudFormation stack, see the AWS CloudFormation Documentation.

  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 release version from which to launch the instance.
  5. Under Region, select a region in which to launch the instance.
    For information on the implications of the region setting with Teradata software, see Region and Time Zone Considerations.
  6. Under Deployment Options, select Server Management in VPC for multi-app monitoring.
  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.
    The stack name must be unique to your region or the launch will fail.
  10. Under Parameters, specify the following values for the Teradata Server Management instance:
    Parameter Category Parameter Name Action
    VPC Settings VPC Select a virtual private cloud in which the system will be launched.
    Availability Zone Select an availability zone for the subnet that you select next.
    Subnet Select a public subnet created by the Teradata Database.
    Allow SM Services Access From (CIDR block) Make sure this is the CIDR block of the existing subnet.
    Allow Remote Access From Enter a CIDR address (public IP address) of your security group to lock down SSH and enable access to Server Management. For more information, see Security Groups and Ports.

    Make sure the CIDR address you enter is not being used by existing subnets in the same VPC by going to the AWS Web Console. Under Networking, select VPC. Under Resources, select Subnets. Check the CIDR column.

    Key Pair AWS Key Pair Enter a key pair to SSH into the instances.
    Teradata Server Management Number of CMICs Number of Server Management instances to launch. Two is the minimum required number for high availability.
    Server Management Site ID [Base, Advance, and Enterprise tier users only] Teradata site ID to be used when connecting to the Teradata Database (AMZ followed by 12 numbers). If you do not have the site ID, you can continue without it, and add it later. See Site IDs.
    Server Management Admin Password Enter the Server Management Administrative password, using 6 to 32 alphanumeric characters.
    Server Management REST Password Enter the Server Management REST password, using 6 to 32 alphanumeric characters.
  11. Click Next.
    The Options page appears.
  12. [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.
  13. [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.
    You can change the Rollback on failure setting to No if you want to troubleshoot a stack failure. The default setting is Yes.
  14. Click Next.
    The Review page appears.
  15. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  16. Click Create to create the stack.
    This process can take anywhere from several minutes to 45 minutes, 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.
  17. [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.
    After the stack is created, Teradata Server Management is ready and is started. The CMICs you launched are automatically configured to communicate with each other.

results matching ""

    No results matching ""