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 ??

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年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン