Ok guys, I had a similar problem, what is the best thing you can do at this point,
there is an api gateway that completes SSL - make a call from Api Gateway to your alb, elb or nlb (it is better if it matches your architecture) - have alb protected by WAF with two sets of rules 1. a white list of all api ip gateways 2. have a header http accepted only by api gateway
in this way you keep your infrared to the limit.
if you have nlb, then you can have a direct link to NLB directly, keep in mind that NLB does not support route-based routing and application fault tolerance in the cross-zone
I asked AWS to raise a feature request for the same
raaone7
source share