Is your feature request related to a problem? Please describe.
One of our apps requires a secure cookie be set on our domain name. The previews are built and available at a URL like this one:
pr-xxxx.yyyyyyyyyyy.amplifyapp.com
Describe the solution you'd like
I would like to be able to replace amplifyapp.com (in that pattern above) with a custom domain, that's managed in route53, automatically.
Additional context
N/A
We have this same issue - our auth token is stored in a secure cookie scoped to our domain, so we are unable to authenticate from our SPA deployed to the preview URL in amplify.
A wrinkle on our end is that our DNS is configured in Cloudflare, not Route53, so I'm not sure how the DNS update would work.
One idea would be some sort of trigger from Amplify which could let us run a lambda to configure or delete DNS records when preview apps are generated or destroyed.
@mwarkentin @adamaltman this is supported: https://aws.amazon.com/blogs/mobile/automatically-create-and-delete-custom-sub-domains-for-your-branch-deployments-with-amplify-console/
FYI, looks like this option isn't available if you deploy your root domain _is_ a subdomain. You can manually create sub-subdomainds, but not automatically.
E.g. If the root domain for app is demo.myapp.com, you can manually create pr-27.demo.myapp.com, but the option to creatae it automatically isn't there.

Most helpful comment
We have this same issue - our auth token is stored in a secure cookie scoped to our domain, so we are unable to authenticate from our SPA deployed to the preview URL in amplify.
A wrinkle on our end is that our DNS is configured in Cloudflare, not Route53, so I'm not sure how the DNS update would work.
One idea would be some sort of trigger from Amplify which could let us run a lambda to configure or delete DNS records when preview apps are generated or destroyed.