Deploying Teradata Server Management Using AWS CloudFormation

Prerequisite
Depending on your account settings, check to ensure the IAM user has permissions for AWS CloudFormation, IAM roles, IAM profiles, and instance profiles. See Quick Start. Check if AWS service limits need to be increased, particularly for EBS and EC2 instance limits. See AWS Service Limits.

Deploy Teradata Database before deploying Server Management.

  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 More Software under the subscription name.
  4. Under Software Pricing, select your subscription term.
  5. Under Version, select the release version from which to deploy the instance.
  6. Under Region, select a region in which to deploy the instance.
  7. Under Deployment Options, select Server Management in VPC for multi-app monitoring.
  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.
  9. Click Next.
  10. Under Specify Details, type a stack name.
    The stack name must be unique to the deployment region.
  11. Under Parameters, specify the following values for the Teradata Server Management instance:
    Parameter CategoryParameter NameAction
    VPC SettingsVPCSelect a virtual private cloud in which the system is deployed.
    Availability ZoneSelect an availability zone for the subnet that you select next.
    SubnetSelect 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 FromEnter a CIDR address (public IP address) of your security group to lock down SSH and enable access to Server Management.
    Key PairAWS Key PairEnter a key pair to SSH into the instances.
    Teradata Server ManagementNumber of CMICsNumber of Server Management instances to deploy. Minimum for high availability: 2.
    Server Management Site ID[Enterprise, Advanced, Base tier users only] String that identifies this Teradata deployment for Teradata Customer Support (AMZTDB followed by up to 9 numbers). If you do not have the site ID, you can continue without it, and add it later. See Site IDs.
    Server Management Admin PasswordEnter 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.
  12. Click Next.
    The Options page appears.
  13. [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.
  14. [Optional] Under Advanced, set additional options for your stack, such as notifications and a stack policy.
    Setting the Rollback on failure value to No enables troubleshooting after a stack failure.
  15. Click Next.
    The Review page appears.
  16. Review the information carefully to ensure it is correct, and select the standard AWS I acknowledge check box at the bottom.
  17. Click Create to create the stack.
    This process can take anywhere from several minutes to 45 minutes, 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.
  18. [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 deployed are automatically configured to communicate with each other.
Postrequisite
The CMICs must be configured, interactively or in batch mode, to manage the Teradata Database and other applications in the ecosystem. See Teradata Server Management Configuration.

results matching ""

    No results matching ""