Copilot-cli: Copilot Creates a Public Hosted Zone, even if a Private Hosted Zone already existed

[asantos-fuze]

There is a Private HZ xpto.internal.domain.com in the account.
An app is created with the following parameters:
copilot app init app --domain xpto.internal.domain.com

Copilot is creating a Public Hosted Zone app.xpto.internal.domain.com

Expected behavior:
Since a Private Hosted Zone already existed, records should be added under the existing zone.

[iamhopaul123]

Hello @asantos-fuze. Thank you for the feedback! Making this "expected behavior" work is easy. However, I'm not sure if it solves all your use cases, since actually by default we'll use the domain name as ${service name}.${env name}.${app name}.${domain name} for your deployed service (we are also working on customized domain name https://github.com/aws/copilot-cli/issues/1188). Could you elaborate more about your use cases? For example, do you want to just have a private domain work in your VPC and place your tasks in the private subnets as well?

[asantos-fuze]

Hi @iamhopaul123

I've imported a vpc and subnets into the environment.
The objective was to deploy the app with an internal ALB for private subnets and add the new app to an already existent Privat Hosted Zone

[iamhopaul123]

Gotcha. It makes sense to me. We'll work on this feature that allowing users to use a private hosted zone in Copilot (could coexist with public domain) and make sure all the sub hosted zone are private and connected to all the environment VPCs that are under the app as well. Does that sound good to you?

[asantos-fuze]

Hi @iamhopaul123 , yes that sounds good

[asantos-fuze]

Also, ALB should support the Schema Internal, instead of internet-facing