Support AWS Shield advanced on NLBs not part of ingress controller #3752
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
|
Hello @uk-rj, Thanks for your feature request to add AWS Shield Advanced support for NLBs on AWS load balancer controller. We will discuss this with our internal team and see if we can add it to our roadmap. Thanks |
shraddhabang
added
kind/feature
|
@shethyogita83 @shethyogita83 If this is open for contribution, I would like to pick this issue. |
|
Hey @csauoss, Thanks for reaching out and offering to pick up the issue! Yes, this issue is open for contribution and you can pick it up. We will be waiting for your PR. Thanks! |
6 tasks
|
@shethyogita83 I have the pr #3869 out for this. Took me longer than expected as I was occupied with some things. Can you please suggest me a simple way to test this manually and also review the pr when you get a chance? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the ALB controller supports an annotation to enable AWS Shield Advanced for ALB / Ingress resource.
alb.ingress.kubernetes.io/shield-advanced-protection
AWS Shield Advanced is also available for NLBs, it would be great if you could provide and annotation and support for enabling of shield-advanced-protection on NLBs created using the service resource. I guess it would also need to provision an elastic IP, linked to the NLB, for advanced shield to work.
The text was updated successfully, but these errors were encountered: