route53 A record is setting incorrect alias target for s3 website

[harmohan-a]

🐛 Bug Report

What is the problem?

I created a cdk stack with s3, route53 and A record on an existing zone. when deployed the alias target in route53 is encoded string

http\072\057\057harmohan.<website>.com.s3-website-ap-southeast-2.amazonaws.com.

Reproduction Steps

 const bucketProps: BucketProps = {
      bucketName: DOMAIN_NAME,
      websiteIndexDocument: 'index.html',
      publicReadAccess: true,
      removalPolicy: cdn ? RemovalPolicy.RETAIN : RemovalPolicy.DESTROY,
      websiteErrorDocument: cdn ? undefined : 'index.html'
    }

    const bucket = new Bucket(this, 'S3Bucket', bucketProps);

    const zone = HostedZone.fromLookup(this, 'HostedZone', {
      domainName: <domain name>
    });

    new ARecord(this, 'ARecord', {
      recordName: DOMAIN_NAME,
      zone: zone,
      target: {
        aliasTarget: new BucketWebsiteTarget(bucket)
      }
    });

Verbose Log

Environment

• CDK CLI Version: 1.6.0
• Module Version: 1.6.0
• OS:
• Language: TypeScript

Other information

[jokyjang]

I have seen the same issue with Java.

[nmussy]

Definitely my fault, I've used the bucketWebsiteUrl property as a record value, which is prefixed with the http:// protocol:

aws-cdk/packages/@aws-cdk/aws-route53-targets/lib/bucket-website-target.ts

Line 32 in c8bb50e

dnsName: this.bucket.bucketWebsiteUrl,

Sorry about that, I'll get a PR ready

[harmohan-a]

thanks @nmussy

[jokyjang]

This is still not working correctly. Based on my experience, the alias target for S3 bucket should be set to the regionalized base domain name such as s3-website-us-west-2.amazonaws.com if the bucket is in us-west-2 instead of the full endpoint name.

It seems Route53 could figure out the full endpoint name since bucket name must exactly match the record name.

[nmussy]

Hey @jokyjang. Please tell me if I understand correctly, but the DnsName shouldn't be the actual bucket website, but the fixed endpoint depending on the region. So instead of setting <bucket_name>.s3-website-us-west-2.amazonaws.com like we have now, we should use s3-website-us-west-2.amazonaws.com. Your last paragraph (also mentioned in the documentation) got me a little puzzled though:

Route 53 figures out which bucket to route traffic to based on the name of the record.

We might have to add a CNAME to allow the user to transparently have different domain name, unless I'm missing something.

I'll look into it tomorrow morning, it's getting late here. Thanks, and sorry again for the issues everyone.

[nmussy]

#4250 was just merged to fix the issue raised by @jokyjang.

I'm also looking into making another PR to make sure that the bucketName matches the full domain name.