VPC Interface Endpoint Limitation on one subnet per Availability Zone for "Enable Private DNS Name"

0

Per this, only one subnet per AZ can be used with "Enable Private DNS Name" option.

This is a show stopper for customer implementation as there are multiple subnets in a AZ customer want to use the endpoint. Specially, when customers have a solid use case for using SSM but don’t want to use internet for this.

Wondering, what is the suggested workaround and tentative plan to remove this limitation ?? As a workaround, may be creating a internal R53 entry , associating with the VPC and creating the service specific Cnames to resolve to the vpc endpoints ??? Would that work ??

AWS
已提問 6 年前檢視次數 1065 次
1 個回答
0
已接受的答案

Private DNS Name options applies to the entire VPC, any Instance in the VPC can resolve private DNS Name of interface endpoint via Amazon Provided DNS.

已回答 6 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南