Cloudformation-coverage-roadmap: AWS::EC2::VPCEndpointService-PrivateDnsName
Title
AWS::EC2::VPCEndpointService-PrivateDnsName
Scope of request
Add support for the PrivateDnsName attribute to the AWS::EC2::VPCEndpointService CloudFormation resource.
The PrivateDnsName is supported by the CreateVpcEndpointServicConfiguration API call but not exposed via CloudFormation
Expected behaviour
- In Create, the Endpoint Service should be created with the specified PrivateDnsName
- In Update, the Endpoint Service's PrivateDnsName should be added, changed or removed as per the behaviour of the ModifyVpcEndpointServiceConfiguration API call
Helpful Links to speed up research and evaluation
API docs at:
Category
Networking & Content (VPC, Route53, API GW,...)
networking & content deliv
trav-c
👍18
>All comments
It would be nice if you can specify a Route53 HostedZoneId too, so if you own the zone and it's hosted in Route53 then it can create the required records in the zone and complete the DNS verification process automatically.
Currently we have to do this manually on every VPCEndpointService we create. We don't have enough to write a Lambda for it but we have more than convenient for the manual process.
akunszt
on 19 Aug 2020
👍8
Was this page helpful?
0 / 5 - 0 ratings
Related issues
san-san
路
3Comments
grauj-aws
路
3Comments
kdgregory
路
3Comments
baxang
路
3Comments
mildebrandt
路
3Comments
Most helpful comment
It would be nice if you can specify a Route53 HostedZoneId too, so if you own the zone and it's hosted in Route53 then it can create the required records in the zone and complete the DNS verification process automatically.
Currently we have to do this manually on every VPCEndpointService we create. We don't have enough to write a Lambda for it but we have more than convenient for the manual process.