- Newest
- Most votes
- Most comments
Hello, and thank you for reaching out!
I have reviewed the case you opened with AWS Support and the resulting investigation from the internal ELB team regarding this known issue with Classic Load Balancers.
This does appear to be a unique situation wherein the recommended workaround of migrating to ALB / NLB is explicitly unsupported by the AWS OpsWorks Stacks service utilizing ELB. I do see that there some environments wherein an Application Load Balancer can be used with some OpsWorks Stacks, but I do understand if this workaround does not fit your environment.
I wanted to let you know that I have engaged internal teams further to determine if there is more information or a workaround that can be found for this issue. I encourage you to follow up on this via the original support case or via your account manager.
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi Justin, I met this issue recently. Our application is basing on EKS, the service is exposed by LoadBalancer with k8s service. Any suggestion for the ELB configuration for that ?