Menu
Real-Time Web Analytics with Kinesis Data Analytics
Real-Time Web Analytics with Kinesis Data Analytics

Appendix C: Existing VPC Template

The Real-Time Web Analytics with Kinesis Data Analytics solution includes an AWS CloudFormation template that allows you to deploy the solution in an existing virtual private cloud (VPC).

Prerequisites

Before you start, the existing Amazon VPC must have the following:

  • Two public subnets in different Availability Zones for the solution's Application Load Balancer (ALB).

  • Two subnets that can receive traffic from the solution's ALBs and connect to Amazon Kinesis Data Firehose API endpoints for the solution's beacon web servers.

Launch the Stack

  1. Sign in to the AWS Management Console and click the button below to launch the real-time-web-analytics-with-kinesis-existing-vpc AWS CloudFormation template.

    
              Real-Time Web Analytics with Kinesis Data Analytics launch button

    You can also download the template as a starting point for your own implementation.

  2. The template is launched in the US East (N. Virginia) Region by default. To launch this solution in a different AWS Region, use the region selector in the console navigation bar.

    Note

    This solution uses the Amazon Kinesis Data Firehose and Amazon Kinesis Data Analytics services, which are currently available in specific AWS Regions only. Therefore, you must launch this solution an AWS Region where these services are available. For the most current service availability by region, see AWS service offerings by region.

  3. On the Select Template page, verify that you selected the correct template and choose Next.

  4. On the Specify Details page, assign a name to your solution stack.

  5. Under Parameters, review the parameters for the template, and modify them as necessary.This solution uses the following default values.

    Parameter Default Description
    User Name <Requires input>

    User name to access the real-time dashboard

    User Email Address <Requires input>

    Email address of dashboard user. After launch, an email will be sent to this address with dashboard login instructions.

    CloudWatch Dashboard Yes

    Choose whether to deploy the Amazon CloudWatch metrics dashboard

    CORS Origin *

    Specify a name for the new Amazon S3 bucket where the real-time dashboard will be stored. Do not specify an existing bucket.

    Node Requests/Min 50K

    The number of requests per minute that each beacon node will support. Choose 50K or 100K.

    Min Beacon Servers 2

    The minimum number of beacon web servers. For high availability, specify at least 2.

    Max Beacon Servers 6

    The maximum number of beacon servers

    SSH Key Pair <Requires input>

    Public and private key pair, which allows you to connect securely to the beacon web servers. When you created an AWS account, this is the key pair you created in your preferred AWS Region.

    Enable SSH? false

    Choose whether to allow SSH access to beacon servers. If you select true for this parameter, you must specify an SSH Key Pair and a CIDR block in the Enable SSH From parameter.

    Note

    This solution's beacon web servers are configured to be managed by AWS Systems Manager. As a result, you can use Run Command to connect to the beacon server instead of SSH.

    Enable SSH From <Optional input>

    This IP address CIDR block will have access to the beacon web servers

    Existing VPC <Requires input>

    The VPC ID of the existing VPC for the beacon severs

    ALB Subnet 1 <Requires input>

    The subnet ID of a public subnet in your existing VPC for the first ALB

    ALB Subnet 2 <Requires input>

    The subnet ID of a public subnet in your existing VPC for the second ALB. Note that this subnet must be in a different AZ than the subnet for the first ALB.

    Beacon Server Subnet 1 <Requires input>

    The subnet ID of a subnet in your existing VPC for the first beacon web server

    Beacon Server Subnet 2 <Requires input>

    The subnet ID of a subnet in your existing VPC for the second beacon web server. Note that this subnet must be in a different AZ than the subnet for the first beacon web server.

  6. Choose Next.

  7. On the Options page, choose Next.

  8. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  9. Choose Create to deploy the stack.

    You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of CREATE_COMPLETE in roughly 10 minutes.

    The solution sends an email invitation to join the real-time dashboard.

  10. In the email, follow the instructions to sign in to the dashboard.