<![CDATA[How to resolve CloudFront conflict with custom domain on FusionAuth Cloud?]]>We are using FusionAuth Cloud with a custom domain, and we've set up our own CloudFront distribution for that domain. However, we received notification that FusionAuth is implementing CloudFront as part of their cloud infrastructure.

The issue is that AWS only allows one CloudFront distribution per hostname. Our custom domain is registered in our CloudFront distribution, but the DNS record points to the FusionAuth instance.

What changes do we need to make to resolve this conflict and allow FusionAuth to enable CloudFront on their side for our instance?

]]>https://fusionauth.io/community/forum/topic/3158/how-to-resolve-cloudfront-conflict-with-custom-domain-on-fusionauth-cloudRSS for NodeTue, 29 Sep 2026 01:01:29 GMTMon, 28 Sep 2026 16:13:35 GMT60<![CDATA[Reply to How to resolve CloudFront conflict with custom domain on FusionAuth Cloud? on Mon, 28 Sep 2026 16:13:47 GMT]]>To resolve this CloudFront conflict, you need to disassociate your custom domain from your CloudFront distribution.

Since AWS only allows one CloudFront distribution per hostname, and FusionAuth Cloud is implementing CloudFront on their infrastructure, you have two options:

  1. Remove the custom domain from your CloudFront distribution — This allows FusionAuth to add the domain to their CloudFront distribution
  2. Set up your CloudFront as a proxy — Configure your distribution to proxy requests to FusionAuth's infrastructure

The recommended approach is to remove your custom domain from your CloudFront distribution entirely, as FusionAuth will handle CloudFront configuration as part of their cloud service.

How FusionAuth Custom Domains Work

When you configure a custom domain with FusionAuth Cloud, you create a CNAME record pointing from your custom domain to your deployment's durable URL (something like <random-string>.durable.fusionauth.dev). FusionAuth manages the CloudFront distribution and SSL certificates on their infrastructure, so you don't need to maintain your own CloudFront distribution for the custom domain.

The proper DNS setup should be:

  • Custom domain → CNAME → FusionAuth durable URL

This allows FusionAuth to provision and manage the entire CloudFront infrastructure, including SSL certificate validation and renewal, as part of their cloud service.

Migration Timeline

This change is important but not urgent. A timeline of 1-2 weeks for investigation and implementation is reasonable. FusionAuth support can assist you through the migration process if you have any questions during implementation.

Related Documentation

Note: If you're on a High Availability plan and want to use the Unlimited Custom Domains feature, or if you need assistance with the migration, open a support ticket.

]]>https://fusionauth.io/community/forum/post/8654https://fusionauth.io/community/forum/post/8654Mon, 28 Sep 2026 16:13:47 GMT