Why do I need to prepare VPC Endpoint Service and NLB for connecting to HULFT Square?

Question

1. Why do I need to prepare AWS VPC Endpoint Service and NLB for connecting HULFT Square in closed network?
2. Is there any way to connect HULFT Square in closed connection other than using PrivateLink?

Background
Currently, I use PrivateLink for connecting HULFT Square in closed network.
There is a limitation of listeners per NLB, so the number of connecting host is up to 50. However, Our connection destination is estimated to be more than 50, so using NLB is not the best choice in terms of scalability as adding new NLB costs extra fee.
Considering those, I would like to ask the necessity of using VPC Endpoint Service and NLB.

Answer

1. HULFT Square only supports PrivateLink as connecting method in closed network. 
   Therefore, users need to create VPC Endpoint Service and route traffic by NLB in their AWS environment, the connection destination of HULFT Square. Users also need to create VPC Endpoint in HULFT Square to connect the routed traffic path.
   
   For the details of PrivateLink, please also refer to the following online help.
   ◇PrivateLink
   
   
2. As answered in answer 1 above, HULFT Square only supports PrivateLink as connecting method in closed network.