Load balancer listener must use HTTPS protocol
High
AWS
General
aws-elasticloadbalancingv2-listener-load-balancer-2
Applies to
AWS::ElasticLoadBalancingV2::Listener
What CGPulse checks
A resource passes this rule when protocol must equal HTTPS. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure the listener to use HTTPS with a valid TLS certificate to encrypt traffic. In AWS Console: EC2 > Load Balancers > Listeners > Add HTTPS listener. See: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html
Terraform
resource "aws_lb_listener" "{name}" {
protocol = "HTTPS"
ssl_policy = "ELBSecurityPolicy-TLS13-1-2-2021-06"
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled