Prisma Cloud: How to stop Elastic Load Balancers from violating 'AWS Elastic Load Balancer with listener TLS/SSL is not configured' policy
7554
Created On 12/22/21 01:40 AM - Last Modified 01/27/23 21:55 PM
Objective
How to configure Elastic Load Balancers in the AWS console to be compliant with the 'AWS Elastic Load Balancer with listener TLS/SSL is not configured' policy which is creating alerts in Prisma Cloud.
Environment
- Prisma Cloud
- AWS
- Elastic Load Balancers
Procedure
1. Login to AWS console
2. Search for EC2
3. Select Load Balancers
4. Select the desired load balancer and click the listeners tab
5. Select TLS, change the port number to what you need, and select an ACM cert to use
Additional Information
Alerts are generated in Prisma Cloud for 'AWS Elastic Load Balancer with listener TLS/SSL is not configured' policy because in the AWS console, if the user goes to edit any of the non SSL protocols/ports, it shows N/A in the space to configure the cert ID which puts ELBs in violation of this policy.