WebRTC Ventures Chime Starter Kit HA-Setup (Terraform)

Configure and provision the WebRTC Ventures Chime Starter Kit on a high available infrastructure on AWS cloud using Terraform.

What you should know:

1. Getting the product AMI ID: ObtainAMIID.pdf
2. Module's variables details: VARIABLES.md

Prerequisites

The following are the prerequisites needed for this setup:

1. Install Terraform.
2. Install AWS CLI.
3. Configure Terraform for your AWS account. You may also use the AWS CLI to setup your credentials.

Setup

To provision the application you have two options as documented here with examples:

1. Using an external DNS not hosted on Route53
2. Using AWS Route53 DNS Hostedzone

Additional information

1. If you manage your DNS on AWS Route53, then you can take advantage of the ACM module by setting use_route53_hostedzone variable to true, supplying the route53 hosted zone details under the route53_hosted variable and the hostname under app_domain. Ensure the acm_cert_arn variable is set to null.
2. If you manage your DNS in a different DNS provider, you can create an ACM certificate then copy the certificate ARN from ACM console and put it under acm_cert_arn variable. With this option you must set use_route53_hostedzone variable to false and route53_hosted variable to null for each key within its map.

Provisioning this module successfuly will do the following:

1. Create an EC2 Auto Scaling Group with scaling alarms for CPU usage and optional ones for Network (In and Out) metrics.

2. Create an Application LoadBalancer that will ditribute traffic to your instances.

3. (Optional) If Route53 hosted zone was use, an output of the domain on which you will access your application under application_domain output variable.

4. (Optional) If ACM certificate for TLS was manually created, the output will give you the lb_dns_value with which you will create a CNAME record in your DNS management console as its value:

   For example if my domain is example.com and I want my application to be accessed at meet.example.com; then I will create a CNAME record with meet.example.com as the record name and lb_dns_value output value as its CNAME value.

With your DNS correctly updated you can reach your application on the configured domain.

Conclusions

For any inquiries and questions contact our team at team@webrtc.ventures.