- Newest
- Most votes
- Most comments
Here are some steps you can take to investigate and potentially resolve the issue:
- Check the AWS Management Console: The first step is to check the AWS Management Console to ensure that the listener is indeed being deleted. You can do this by navigating to the EC2 section, selecting 'Load Balancers', and then checking the 'Listeners' tab for your specific load balancer.
- Review Access Logs: AWS provides access logs that capture detailed information about requests sent to your load balancer. These logs can be used to analyze traffic patterns and troubleshoot issues. If access logging is enabled for your load balancer, you can check these logs in the Amazon S3 bucket specified during the enabling of access logs. The logs contain information such as the time the request was received, the client's IP address, latencies, request paths, and server responses.
- Check for Manual Deletion: Ensure that the listener is not being manually deleted by someone with access to your AWS account. This could be a team member or a third-party service with access to your AWS resources. Check Cloudtrail. If you suspect this might be the case, you may want to review your IAM policies and access controls.
- Finally, you can always contact AWS Support
Please try out these
Check AWS CloudTrail Logs Review the AWS CloudTrail logs to find events related to changes in your Load Balancer configuration, especially the deletion of the 443 listener.
Examine Load Balancer Access: Evaluate and restrict who has access to modify Load Balancer settings, using IAM roles to limit permissions.
Evaluate Load Balancer Access Logs Review access logs for the Load Balancer to identify suspicious activity that may lead to the deletion of the listener.
Enable AWS Config Enable AWS Config to track changes to your AWS resources, providing a historical record of Load Balancer changes.
Seek AWS Support: If the root cause remains elusive, consider reaching out to AWS Support for professional assistance in investigating and resolving the issue.
Relevant content
- asked 9 months ago
- Accepted Answerasked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 9 months ago
You might be able to find the cause by looking in CloudTrail (provided that it has been configured in your account).
To do this navigate to the CloudTrail Service -> Event History and in Look-up attributes look for: Event name = "DeleteListener"
If you see any event listed, this might give a clue to what/who is deleting the Load Balancer Listeners