클래식로드밸런서 리스너 초기상태로 변경 막기(Prevent Classic Load Balancer Listener from reverting to initial state)

안녕하세요.

일반적으로 ELB 설정 이후 리스너나 대상 인스턴스 등은 AWS SDK/CLI 또는 인프라 배포 관련 설정을 따로 하시는 게 아니라면 변경될 이유는 없습니다. 혹시 EKS 등의 서비스 노출 용도로 ELB Controller 등을 통해 배포하고 있지는 않은지요? Controller 의 설정은 기존에 설정해 두신 것과 달리 되어있지는 않은지요?

어느 부분에서 변경이 되는 건지 파악이 잘 안되신다면 CloudTrail 등에서 해당 리소스의 변경 요청 작업을 누가 시도한 건지 확인해 볼 수 있을 것 같습니다.

I apologize, but I don't have specific information about preventing Classic Load Balancer listeners from reverting to their initial state or changing protocols unexpectedly. Classic Load Balancers are an older generation of load balancers, and AWS recommends using Application Load Balancers or Network Load Balancers for newer deployments.

However, for modern Application Load Balancers (ALBs), there are some practices that can help maintain consistent configurations:

1. Use deletion protection: Enable deletion protection on your load balancer to prevent accidental changes or deletions.

2. Implement proper access controls: Ensure that only authorized personnel have permissions to modify load balancer settings.

3. Use Infrastructure as Code (IaC): Manage your load balancer configuration using tools like AWS CloudFormation or Terraform to maintain a consistent state.

4. Regular audits: Periodically review your load balancer configurations to ensure they haven't changed unexpectedly.

5. Monitor for changes: Set up AWS CloudTrail to log API calls and monitor for unexpected modifications to your load balancer settings.

If you're experiencing unexpected changes to your Classic Load Balancer, it's recommended to contact AWS Support for assistance, as this behavior is not typical and may indicate an underlying issue.
Sources
Edit attributes for your Application Load Balancer - Elastic Load Balancing