[Feature Request]: Support DNS outside of Route53

[jpivac]

Describe your idea/feature/enhancement

We have our DNS with Cloudflare, and would like to use copilot to deploy services to AWS without copilot trying (and erroring) when it attempts to configure DNS.

Proposal

Support the option of skipping any DNS configuration by copilot.

Additional Details

I have used copilot to build and deploy some services to ECS successfully.

I manually added a wildcard certificate in ACM and used that via $ copilot env init --import-cert-arns arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012 successfully.

I then pointed a CNAME record at the publi-abcdef-12345.ap-southeast-2.elb.amazonaws.com host which all worked well.

However when attempting to add the following under http:

   additional_rules:
     - path: 'rest'
       target_port: 4500       # Traffic on "/rest" is forwarded to the main container, on port 4500.  

Copilot returns the error: X execute deployment 1 of 1 in group 1: deploy service api to environment staging: validate ALB runtime configuration for "http.additional_rule[0]": cannot deploy service api without "alias" to environment staging with certificate imported

Speaking to AWS support I have been informed copilot is delegating responsibility for the subdomain to Route53.

"From the look of it you will need to point the NS record at the subdomain, and the subdomain will need to be managed by Route53 for this to work with Copilot at present"

We would like to keep all DNS with Cloudflare if possible.

[sandorvasas]

+1 I know it's business for AWS, but really frustrating.