Amplify Custom Domain Activation Issue with Google Domains

Hello AWS Community,

I'm experiencing a peculiar issue with AWS Amplify and a custom domain registered through Google Domains. The setup works flawlessly with the default Amplify-generated URL and a secondary domain managed by Route 53. However, the problem arises when I attempt to use a custom domain from Google Domains.

After a successful app build in Amplify, I proceed to add the custom domain and configure the DNS records in Google Domains as instructed (three CNAME records: one for domain verification, one for the www subdomain, and one for the root domain).

Initially, the SSL creation and configuration steps complete successfully, and my React application becomes accessible via the custom domain, it opens correctly for 2 minutes approx. but unfortunately, this is short-lived. The domain activation step fails, leading to a 403 error indicating a bad request or potential configuration issue, as per CloudFront's error message. Subsequently, the site becomes entirely unreachable, displaying a DNS_PROBE_FINISHED_NXDOMAIN error.

1. First it renders ok when the domain ownership is verified
2. After a few minutes on the 3rd step it shows this

403 ERROR
The request could not be satisfied.
Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: CCNnEj21lt8TYY6ITvjVR2lL87

3. After more minutes it shows

This site can’t be reachedCheck if there is a typo in www.recovery.portal.tryrook.io.
If spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN

It's worth noting that this setup previously functioned correctly before I had to recreate the Amplify app due to VCS changes. Despite ensuring complete resource deletion and DNS record propagation, the issue persists, presenting as a brief period of accessibility before failing.

Has anyone encountered a similar issue or can offer insights into resolving this domain activation failure with Amplify and Google Domains?

Additionally, to mitigate the impact of this issue, I've temporarily migrated my application to Vercel Cloud, where the custom domain setup with Google Domains functions without any problems. This workaround suggests that the issue might be specific to the integration between AWS Amplify and Google Domains. Any insights or solutions to rectify this on AWS would be greatly appreciated.

Thank you in advance for your assistance.