Amazon Q Web Experience URL Alias Redirect to custom Domain

Question

As an AWS Architect aiming to direct users to a new Amazon Q web experience via a custom domain name managed by Route 53, I've encountered challenges despite creating public hosted zones in both us-east-2 and us-west-1 regions, where the service is active. Despite trying various alias and record types, Amazon Q does not appear in the service list for alias targets. Resorting to a standard CNAME record introduces certificate issues and results in a 'host not found' error. Given these circumstances, what are the recommended steps or configurations to successfully map a custom domain to the Amazon Q web experience, ensuring secure and error-free redirection?"

I have already investigated the following article. https://repost.aws/knowledge-center/route-53-no-targets, but unfortunately this didn't help.

Accepted Answer

Hi THere

You can use CloudFront in front of your Amazon Q for Business URL.

1. Create an SSL Certificate for your custom domain name in AWS Certificate Manager.  Complete all validation steps
2. Create a CloudFront Distribution and point it to the Amazon Q for Business hostname
3. Point the CloudFront distribution to your ACM certificate, and add your custom domian name as an Alternate Domain Name
4. Once your CloudFront distribution is deployed, create an Alias record in Route53 pointing to your CloudFront distribution

I just tested this and it works fine.  Once you are logged into Q, the Amazon Q URL is displayed in the broser, but the redirection from your custom domain to your iDp and back to Q works ( I tested with Azure AD)

Answer

Many thanks. I followed the above solution with success.

Amazon Q Web Experience URL Alias Redirect to custom Domain

Relevant content