You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally would be for both ALB and NLB, like Internet <-> AWS NLB with elastic IP <-> AWS ALB <-> AWS EKS.
Minimum for NLB, like Internet <-> AWS NLB with elastic IP <-> AWS EKS.
Would be nice keep user's IP info...
P.S. AWS ALB does not support static IP even customers request it since many years ago. You could suggest any reasonable work around.
A solution to your problem is to set up an out of band NLB, have the LBC manage an ALB, and manually register the ALB into your NLB. This should be reasonably straight forward as you shouldn't need to manage the out of band NLB, while the LBC will do the heavy lifting of ensuring the ALB targets are correctly updated.
Is your feature request related to a problem?
We need static external IP for AWS load-balancer.
Describe the solution you'd like
Would be nice if we could assign reserved AWS elastic IPs to the load-balancer.
The text was updated successfully, but these errors were encountered: