NLB Privatelink Exposure

Question

Hello, I have a workload behind AWS Network Load Balancer. The workload is in regular use and the traffic flows through the Network Load Balancer. A requirement has come up where I have to expose the workload as service to a different AWS account using AWS Privatelink. I plan to use Privatelink Endpoint Service in the account with workload but I don't want to disrupt the traffic to Network Load Balancer for existing teams. Will exposing the NLB with Privatelink affect the traffic in any way for existing teams? I don't have a solid answer so I am asking this question.

Accepted Answer

Setting Privatelink does not disconnect communication to the NLB.  
Unlike ALB, NLB is a load balancer that can handle millions of requests per second without warming up.  
So even if a large number of requests come in after setting PrivateLink, it is designed to withstand the load.  
https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html#network-load-balancer-benefits
> Ability to handle volatile workloads and scale to millions of requests per second.

NLB Privatelink Exposure

Contenus pertinents