(@aws-cdk/aws-route53): ARecord with ApiGatewayv2DomainProperties to subdomain not working

[janschloss]

What is the problem?

Hello,

when trying to create an ARecord with an HTTP API alias on a subdomain, the record is created with the general domain instead.

Reproduction Steps

    const apiSubDomain = `api.${this.domain}`;

    const hostedZone = HostedZone.fromLookup(this, "HostedZone", {
      domainName: this.domain,
    });

    const certificate = new Certificate(this, "Certificate", {
      domainName: this.domain,
      subjectAlternativeNames: [apiSubDomain],
      validation: CertificateValidation.fromDns(hostedZone),
    });

    const domainName = new DomainName(this, "DomainName", {
// > Note that this is using the subdomain
      domainName: apiSubDomain,
      certificate: certificate,
    });

    const httpApi = new HttpApi(this, "HttpApi", {
      disableExecuteApiEndpoint: false,
      defaultDomainMapping: {
// > Note that this is using the subdomain
        domainName,
      },
    });

    new ARecord(this, "HttpApiAliasRecord", {
      zone: hostedZone,
      target: RecordTarget.fromAlias(
        new ApiGatewayv2DomainProperties(
          domainName.regionalDomainName,
          domainName.regionalHostedZoneId
        )
      ),
    });

What did you expect to happen?

I expected an A Record like this in Route53:
api.example.com | A | Simple | - | alias.....

What actually happened?

An A Record to the general domain was created:
example.com | A | Simple | - | alias.....

CDK CLI Version

1.130.0 (build 9c094ae)

Framework Version

No response

Node.js Version

v14.18.0

OS

Windows

Language

Typescript

Language Version

No response

Other information

No response

[lukewiwa]

Yes I think this is where the critical bug is

aws-cdk/packages/@aws-cdk/aws-cloudfront/lib/distribution.ts

Line 308 in beaa5b2

this.domainName = distribution.attrDomainName;

Seems that by default it takes the top level domain rather than one from the "domains" attribute

Solution

I figured out if you put the record name as the subdomain you wish to connect to it should work out ok.

    new route53.ARecord(this, "AliasRecord", {
      zone: hostedZone,
      recordName: "sub.domain.com",
      target: route53.RecordTarget.fromAlias(
        new alias.CloudFrontTarget(distribution)
      )
    });
  }

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[janschloss]

Don't think this is fixed yet

[simonloach]

This is not fixed and very misleading.