Regional domains show `s3` instead of `s3-website` resulting in misconfiguration about terraform-aws-cloudfront-s3-cdn HOT 3 CLOSED

That's odd. Perhaps it would be better to use website_endpoint or website_domain instead.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket#website_endpoint

Could you check if the outputs of either use the correct s3-website endpoint ?

Certainly, I did some digging and found the following:

• website_domain: s3-website-eu-west-1.amazonaws.com
• website_endpoint: REDACTED.s3-website-eu-west-1.amazonaws.com

Using website_endpoint would probably be best here as the bucket_ attributes do not contain the -website suffix:

• bucket_domain_name: REDACTED.s3.amazonaws.com
• bucket_regional_domain_name: REDACTED.s3.eu-west-1.amazonaws.com

from terraform-aws-cloudfront-s3-cdn.

@nitrocode Looks good!

One minor thing I noticed is that it wants to replace the existing
REDACTED.s3-website.eu-west-1.amazonaws.com into
REDACTED.s3-website-eu-west-1.amazonaws.com (a dash instead of a dot between s3-website and the region) but this is due to the way things were generated prior to v0.55.

Since both the dash and dot-variants are working the same this is an acceptable change IMHO.

from terraform-aws-cloudfront-s3-cdn.

Thanks @syphernl . I put in an initial PR with branch website_endpoint to use that when var.website_enabled is true.

Could you use point your module to my feature branch to see if it works as expected for you ?

module "cdn" {
  source = "[email protected]:cloudposse/terraform-aws-cloudfront-s3-cdn.git?ref=website_endpoint"

  website_enabled = true
  # ...
}

from terraform-aws-cloudfront-s3-cdn.