921164 - Set up and test production EC2 telemetry-server instances and Load Balancer

Status: RESOLVED FIXED

(Webtools Graveyard :: Telemetry Server, defect)

Description

[Mark Reid [:mreid]]

Set up production EC2 telemetry-server instances and Load Balancer, including:
-ELB for incoming.telemetry.mozilla.org
  - Instance name: telemetry-server-lb
  - DNS Info: 
    - telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (A Record)
    - ipv6.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (AAAA Record)
    - dualstack.telemetry-server-lb-2038738656.us-west-2.elb.amazonaws.com (A or AAAA Record)
  - Servers: two (or maybe more) small/micro instances

Test servers and LB
Clean up S3 buckets / SQS queues after.

Comment 1

[Mark Reid [:mreid]]

Set up and tested two micro instances.  If we need to spin up more instances, it's easy using the 'launch_telemetry_server.py' script in the telemetry-server project:
https://github.com/mreid-moz/telemetry-server

Machine details:
Name:     telemetry-server-v1-primary-1
AWS ID:   i-3804150c
Hostname: ec2-54-202-53-173.us-west-2.compute.amazonaws.com

Name:     telemetry-server-v1-secondary-1
AWS ID:   i-be3d998a
Hostname: ec2-54-202-13-6.us-west-2.compute.amazonaws.com

Production config details are available in the above github repo:
aws_provisioning/aws_telemetry_server_config.prod.json
aws_provisioning/aws_telemetry_server_config.prod_secondary.json

S3 Configuration:
Incoming S3 bucket: telemetry-incoming-v1
Publish S3 bucket:  telemetry-published-v1