Commit 94f73253 authored by Cameron McFarland's avatar Cameron McFarland

Updated notes and updated the sizing and number of collectors based on prod traffic demands.

parent ee9d55e8
......@@ -61,11 +61,7 @@ Testing an event: curl http://34.227.92.217:8000/i\?e\=pv
S3Loader:
"I realize now my folly: the app name needs to be different between the enricher and loader ergo the 2 dynamoDB tables were conflicting. Everything makes so much sense now…"
IAM Policies and Roles:
Need roles/policies to allow proper access to the collectors, enrichers and s3 loaders.
Trim down the firehose role?
Last steps:
Need to get firehose provisioned. It's weird.
Are we using the right SSH key?
Did we clean up everything we made for testing?
......@@ -368,7 +368,7 @@ data "aws_ami" "amazonlinux2" {
resource "aws_launch_configuration" "snowplow_collector_launch_config" {
image_id = "${data.aws_ami.amazonlinux2.id}"
instance_type = "t2.micro"
instance_type = "m5.large"
associate_public_ip_address = "true"
enable_monitoring = "false"
iam_instance_profile = "${aws_iam_role.snowplow_collector_role.id}"
......@@ -438,13 +438,24 @@ resource "aws_lb_target_group" "snowplow_collector_lb_target_group" {
// EC2 Auto Scaling Groups
resource "aws_autoscaling_group" "snowplow_collector_autoscaling_group" {
launch_configuration = "${aws_launch_configuration.snowplow_collector_launch_config.id}"
max_size = "3"
min_size = "3"
max_size = "9"
min_size = "9"
target_group_arns = [
"${aws_lb_target_group.snowplow_collector_lb_target_group.id}",
]
enabled_metrics = [
"GroupStandbyInstances",
"GroupTotalInstances",
"GroupPendingInstances",
"GroupTerminatingInstances",
"GroupDesiredCapacity",
"GroupInServiceInstances",
"GroupMinSize",
"GroupMaxSize",
]
tag {
key = "environment"
value = "SnowPlow"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment