Creating Amplify App with domain in private zone

We don't differentiate public zone and private zone. But if you want, you can manually move the record from public zone to private zone.

Thanks for the response Gary,

I'm noticing that this doesn't seem to be an issue of public vs private but rather the Amplify Console is not setting up my domain in the correct zone at all.

I've setup a new scenario similar to the following:

Public Zone 1: example.com

Public Zone 2: test.example.com

When I set up the "Root Domain" for my application I choose the "test.example.com" zone but whenever I setup new domains via the "Domain Management" screen Amplify Console creates them in the example.com zone.

This seems like a bug to me and your it being private vs public doesn't seem relevant.

Can you confirm whether this is expected behaviour or if it's a bug that can be addressed?

Thanks

Edited by: nlaffey on Feb 25, 2019 2:28 PM

Edited by: nlaffey on Feb 26, 2019 6:34 AM

Hi nlaffey,

Thanks for the question.
Currently, this is expected behaviour, you can always manual move the DNS records that displayed in the Amplify Console to the desired hostedzone. But I agree with you, this is inconvenient, the team will take look into this issue and find a solution for it.

Best,
Shufanaws

Got it, thanks for the follow up.