2回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
With both the instance and ALB in the same subnet and VPC privatelink is not required. Within the same subnet you can use the security group of the ALB to control who is allowed to connect (ie use the security group of the EC2 instance within the ALB inbound rule)
PrivateLink can be used to expose your NLB (not ALB) to other AWS accounts or unlinked VPCs
0
I don't understand your question but a privatelink is to access to a service outside your VPC... If the target ALB is in the same VPC, you "just" need good configurations on NACL, Security Groups and routes.
回答済み 2年前
関連するコンテンツ
- 質問済み 2ヶ月前