Common variables referenced in naming standards

• ALB

• ASG

If you followed the naming conventions listed in terraform-aws-vpc you will find it useful to use this terraform-aws-discovery module. The idea of using a discovery module is to centralize datasource usage in a central place and keep the source code DRY.

Here is an example usage:

module "discovery" {
  source              = "github.com/Lowess/terraform-aws-discovery"
  aws_region          = "${var.aws_region}"
  vpc_name            = "${var.vpc_name∑}"
  ec2_ami_names       = [...]
  ec2_security_groups = [...]
}

☝️ If you do not what to use this module you are free to redefine the datasources you need but keep in mind that you will be rebuilding the wheel 🎡

Let's create an ALB and the related resources needed (security groups, listeners and target groups).

• aws_lb
• aws_lb_target_group
• aws_lb_listener
• aws_security_group
• aws_security_group_rule

☝️ AWS Educate does not allow access to Autoscaling and Launch configuration services, In this example we will simulate autoscaling features by running multiple EC2 instances

• aws_security_group
• aws_security_group_rule
• aws_instance
• aws_lb_target_group_attachment

💪 It's now on you to figure out a logic to implement scale up / scale down actions on your autoscaling group

☝️ Here is a way to retrieve Netdata CPU average using the Netdata API:

curl -s "http://<instance-ip>:19999/api/v1/data?chart=system.cpu&after=-10&format=json&options=nonzero" \
  | jq "[ .data[] | nth(2)] | add / length";

Based on standard module structure guidelines