Deploying and Starting Teradata AppCenter Using AWS 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.

Deploy Teradata Database before deploying Teradata AppCenter.

  1. If you have not subscribed to the software, do so now.
    Teradata AppCenter is available only as part of the IntelliSphere bundle. You must subscribe to both Teradata Database and Teradata AppCenter. See Subscribing to Teradata Software.
  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 Teradata Database release version from which to deploy the instance.
  6. Under Region select a region.
    For information about setting a region with Teradata software, see AWS Regions.
  7. Under Deployment Options, select Teradata AppCenter.
  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 deployment will fail.
  11. Under Parameters, specify the following values for the Teradata AppCenter instance:
    Parameter CategoryParameter NameAction
    Network ConfigurationVPCSearch VPC for AppCenter AWS resources. See Virtual Private Cloud
    SubnetSearch for a subnet to use for AppCenter resources.
    Which IP address' should be allowed to SSH AppCenter Instances?Enter CIDR block to allow SSH to AppCenter instances.
    Which IP address' should be allowed to connect AppCenter over HTTPS?Enter the CIDR block to allow HTTPS access to AppCenter.
    Amazon EC2 ConfigurationAWS Key PairSearch for existing AWS key pair name of customer. See Key Pairs
    AppCenter ConfigurationRoute53 Hosted Zone for AppCenterSearch for hosted zone to access AppCenter using DNS.
    Fully qualified base name for AppCenter. Base name must match with selected Route53 hosted zone.Enter fully qualified base domain name for AppCenter based on your hosted zone. Base domain is used to access various AppCenter services.
    Ingress Certificate (Optional)Enter Base64 encoded ingress certificate. This needs to go with ingress key.
    Ingress Key (Optional)Enter Base64 encoded ingress key. This needs to go with ingress certificate.
    AppCenter root passwordEnter root password. Password length must be between 5 and 32 alpha numeric characters.
    AppCenter grafana admin's passwordEnter root password. Password length must be between 5 and 32 alpha numeric characters.
    AppCenter kibana admin's passwordEnter root password. Password length must be between 5 and 32 alpha numeric characters.
    Custom App Certificate (Optional)Enter Base64 encoded certificate. This needs to be a wild card certificate of the form *.appcenter..
    Custom App Key (Optional)Enter Base64 encoded key that goes with the above certificate.
  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 deployed.
  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 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.
  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
  21. To open Teradata AppCenter, go to https://appcenter.base-domain, where base-domain is your domain. See AppCenter Configuration in Parameters table.
    The URL is shown in the output section of the AWS CloudFormation page.

results matching ""

    No results matching ""