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
When deploying an LB for VPN Gateways, there is no need to deploy the gateways to public subnets, it goes against best practices when using Load Balancers since they should be the only public facing infrastructure and forwarding to internal subnets.
As another option, if using UDP protocol and NLB with Global Accelerator, then the NLB can be in private subnets as well to keep it completely internal on AWS Networks and reduce the attack surface even further.
The text was updated successfully, but these errors were encountered:
Hi @Merlz,
I think this feature request is related to the actual Aviatrix controller product, not the Terraform provider. I've gone ahead and opened a ticket on our internal issue tracker for this request. Thank you!
When deploying an LB for VPN Gateways, there is no need to deploy the gateways to public subnets, it goes against best practices when using Load Balancers since they should be the only public facing infrastructure and forwarding to internal subnets.
As another option, if using UDP protocol and NLB with Global Accelerator, then the NLB can be in private subnets as well to keep it completely internal on AWS Networks and reduce the attack surface even further.
The text was updated successfully, but these errors were encountered: