Dynamic Route53 records for AWS auto scaling groups with Terraform

Re:Dynamic Route53 records for AWS auto scaling groups with ... by fatninja on Friday February 07, 2020 @11:32PM (#22273892)

Can't this be solved by using IP addresses for hostnames? This can be a part of bootstrap script(which ASG/Launch Configuration already supports via UserData[1])

What I can't understand is -

If your logs are in ELK and metrics in prometheus/grafana - why do you need SSH access? Sounds like thats a good problem to solve

[1] - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-dat...

[ Parent | on HN ]

Re:Dynamic Route53 records for AWS auto scaling groups with ... by jimsheldon on Monday February 10, 2020 @09:20AM (#22289282)

Post author here.

SSH access is a last resort, but it can be necessary in certain cases. For example, if our log forwarding breaks. SSH is also just one example, it can also be helpful to curl endpoints on the host directly without hitting the ELB/ALB.

The post actually provides the user_data script we use.

[ Parent | on HN ]