Page tree
Skip to end of metadata
Go to start of metadata

Analytics Director automates the upgrade of Ribbon Analytics. 

The Analytics Director instance is installed with the Network Interface on the internal subnet of the Ribbon Analytics cluster, or another subnet that is accessible by the internal subnet.

Use the following steps to launch Analytics Director in AWS. This procedure is required only once for a VPC.

Prerequisites

  • Analytics Director requires a dedicated role with the following privileges:
    • EC2 – Full Access
    • CloudFormation – ReadOnly Access

  • Analytics Director requires VPC Endpoints for the following services:
    • EC2
    • CloudFormation

Procedure Steps

  1. Log into the AWS Console.
  2. Create and verify VPC Endpoints.
    1. Select ServicesVPC (found under the Networking & Content Delivery heading).
    2. In the navigation tree on the left, select Endpoints.
    3. Verify or create the "cloudformation" service.

      1. If an endpoint exists for the "cloudformation" service in the desired region, select and verify its settings.
        OR

      2. If the "cloudformation" service does not exist, click Create Endpoint to add the subnet and update the security group for the service.

        Note

        These are global resources for the VPC, so changes may impact other instances in the VPC. Consult with the VPC Administrator to determine the potential impact of changes.

    4. Verify or create the "EC2" service.
      1. If an endpoint exists for the "EC2" service in the desired region, select and verify its settings.
        OR

      2. If the "EC2" service does not exist, click Create Endpoint to add the subnet and update the security group for the service.

        Note

        These are global resources for the VPC, so changes may impact other instances in the VPC. Consult with the VPC Administrator to determine the potential impact of changes.

  3. Create the Analytics Director role. If the role already exists and has the required privileges, skip this step.
    1. In the AWS Console, select Services IAM (under the Security, Identity, & Compliance heading).
    2. Select Roles
    3. Click Create Role.
    4. Select AWS Service and the EC2 Use Case, then click Next: Permissions.
    5. Use the search field to search for and enable the AmazonEC2FullAccess policy.
    6. Use the search field to search for and enable the AWSCloudFormationReadOnlyAccess policy.
    7. Click Next: Tags.
    8. Click Next: Review.
    9. Enter a Role name and optional Description.
    10. Click Create role.
  4. Launch the Analytics Director instance.
    1. In the AWS Console, select ServicesEC2 (under the Compute heading).
    2. Click Launch Instance.
    3. Click Shared by  Me to view a list of Private AMI IDs.
    4. Select the "director" AMI. Verify it is the proper AMI ID for the region by referring to the IDs published in the Release Notes, or obtain it from the Ribbon Support team.
    5. Enable t2.micro and click Next: Configure Instance Details.
    6. Specify the Network and Subnet.
    7. Set the IAM Role to the Analytics Director role.
    8. Click Next: Add Storage.
    9. Select Add Tags and click Next: Configure Security Group.
    10. Select or create the Internal security group and click Review and Launch.
    11. Click Launch.
    12. Select the SSH Key or create a new one, then click Launch Instance.