DNS validation of Certificates

[richardkeit]

Is your feature request related to a problem? Please describe.
I'm frustrated when LZA can create a certificate for me with DNS validation, but even with a suitable hosted zone within the account (where the certificate is created), I still need to validate the certificate myself.

In a multi-account architecture, this is not ideal.

The console provides a "do it for me" button.

Describe the feature you'd like
Automatically provide DNS validation of certificates within the same account
Bonus - validation in a different account

Additional context
This may be applicable in design of feature:

• Hability to create Private Hosted Zones in workload accounts from shared VPC #92

[bo1984]

Hi @richardkeit! What's likely occurring here, and as you pointed out, the "do it for me" functionality in console is adding the CNAME record to the hosted zone in Route53 as documented. This is a pattern that I think would be useful for large extensive environments especially. We're aiming for extending Route 53 Public and Private Hosted Zones in the early part of next year, and can probably get this added around the same timeline. I will keep this issue open in the meantime should you have any other related questions or concerns.