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 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 7 個月前