Static Site will incorrectly create a new Hosted Zone

[rhboyd]

Because the example relies on an ACM Cert already existing, this would imply that the Hosted Zone already exists. The TypeScript static-site example will create a new Hosted Zone and the DNS Resolution will fail because the the new HZ is not the authority for the domain.

aws-cdk-examples/typescript/static-site/static-site.ts

Lines 69 to 71 in 8eae959

	const zone = new route53.HostedZone(this, 'MyHostedZone', {
	zoneName: props.domainName
	});

[jewelsjacobs]

You can replace this with a lookup. I'm not sure the best way to implement this in the example though.

// Import Route53 existing hosted zone
const importedZone = route53.HostedZone.fromLookup(this, 'HostedZoneFromLookup', {
  domainName: props.domain
})

// Output:
new cdk.CfnOutput(this, 'HostedZoneId', { value: importedZone.hostedZoneId, exportName: 'HostedZoneID' });
new cdk.CfnOutput(this, 'ZoneName', { value: importedZone.zoneName, exportName: 'ZoneName' });

// Input props:
const hostedZoneProps = {
  hostedZoneId: cdk.Fn.importValue("HostedZoneID"),
  zoneName: cdk.Fn.importValue("ZoneName")
};

const siteDomain = props.siteSubDomain + '.' + props.domainName;

 // Route53 alias record for the CloudFront distribution
const zone = new route53.HostedZone(this, 'MyHostedZone', hostedZoneProps);
new route53.ARecord(this, 'SiteAliasRecord', {
  recordName: siteDomain,
  target: route53.AddressRecordTarget.fromAlias(new targets.CloudFrontTarget(distribution)),
  zone
});

[rhboyd]

When I added the Python example I ask the user to supply the Hosted Zone's information so we could do the lookup.