We have a use case where we want to create a Certificate across multiple hosted zones:
i.e.

{ domainName: "example.com", subjectAlternativeNames: "example.co.uk", hostedZone: xxxx, }

Because we're specifying 1 hosted zone, we (obviously) get the error:
Failed to update resource. [RRSet with DNS name _xxxxx.example.co.uk. is not permitted in zone example.com.]

If we create the certificate in the Console, it automatically places the DNS validation in the correct hosted zone.

Use Case

We want to do this so we can have a single CF instance across both hosted zones, to reduce on cost/complexity to our infrastructure.

Proposed Solution

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

This is a 🚀 Feature Request