Application and Network Load Balancer target groups should use encrypted health check protocols
Flags Elastic Load Balancing target groups, Gateway Load Balancer ones included, whose health check protocol is not HTTPS. Health-check traffic sent over HTTP exposes endpoint paths and response bodies to anyone with network visibility between the load balancer and the target.
- service
- ELB
- severity
- Medium
- scope
- evaluated in every region
How to fix it
In the console
EC2 → Target groups → the target group → Health checks
With the AWS CLI
aws elbv2 modify-target-group --target-group-arn <target-group-arn> --health-check-protocol HTTPS --region <region>With Terraform
resource "aws_lb_target_group" "this" {
health_check {
protocol = "HTTPS"
}
}
See which of your accounts this check is failing on.
Book a demo