feat(route53): Vpc endpoint service private dns

[flemjame-at-amazon]

https://aws.amazon.com/premiumsupport/knowledge-center/vpc-private-dns-name-endpoint-service/
https://docs.aws.amazon.com/vpc/latest/userguide/verify-domains.html

AWS added the ability to specify a custom DNS name for an endpoint service earlier this year. It makes it so your clients don't have to create aliases for an InterfaceVpcEndpoint when they connect to your service. This reduces undifferentiated lifting done by clients. This PR creates a construct that will set up the custom DNS.

stack = new Stack();
vpc = new Vpc(stack, 'VPC');
nlb = new NetworkLoadBalancer(stack, 'NLB', {
  vpc,
});
vpces = new VpcEndpointService(stack, 'VPCES', {
  vpcEndpointServiceLoadBalancers: [nlb],
});
// You must use a public hosted zone so domain ownership can be verified
zone = new PublicHostedZone(stack, 'PHZ', {
  zoneName: 'aws-cdk.dev',
});
new VpcEndpointServiceDomainName(stack, 'EndpointDomain', {
  endpointService: vpces,
  domainName: 'my-stuff.aws-cdk.dev',
  publicZone: zone,
});

Original design ticket: #10580

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[flemjame-at-amazon]

rix0rrr opined this should be in the route53 module - #10580

[flemjame-at-amazon]

Any update on this @rix0rrr @shivlaks ?

[gitpod-io]

[shivlaks]

@flemjame-at-amazon took a first pass, take a look at the suggestions/feedback and let me know what you think!

• what's the added newFile.ts in aws-route53-patterns - can that be removed?
• an integration test needs to be added for VpcEndpointServiceDomainName

[flemjame-at-amazon]

@shivlaks

* what's the added `newFile.ts` in `aws-route53-patterns` - can that be removed?

I'm not sure how that got in, must have misclicked - yes it will be removed.

* an integration test needs to be added for `VpcEndpointServiceDomainName`

Can you elaborate on what an integration test is? Do you mean an integ.vpc-endpoint-service-domain-name.test.ts coupled with an integ.expected.json ?

Pull request has been modified.

[shivlaks]

@flemjame-at-amazon

Can you elaborate on what an integration test is? Do you mean an integ.vpc-endpoint-service-domain-name.test.ts coupled with an integ.expected.json ?

Yes, running the integ test by yarn integ or npm run integ would deploy all the integration tests in a module.

yarn integ.test-name.js would deploy a specific test. A successful deployment will automatically create the .generated file. You should not need to add this manually.

[flemjame-at-amazon]

@shivlaks @rix0rrr any update on this?

[shivlaks]

@flemjame-at-amazon looks good to me! added the do-not-merge so @rix0rrr can also have one final look.

Pull request has been modified.

[flemjame-at-amazon]

@shivlaks do you know what's happening with this?

[shivlaks]

@shivlaks do you know what's happening with this?

checking on it, hoping to get it merged ahead of the next release

[shivlaks]

dropping the do-not-merge as I verified with @rix0rrr that we can move forward with this change

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: b56d705
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[ravitejasomisetty]

Would be even better if we can import a hosted zone from different account by providing IAM access. DNS delegation may have been set up in a central account.