You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The aws_acm module should support requesting certificates from AWS certificate manager. Currently the module only supports imported certificates.
Private certificates are easier to support and automate because they do not require validation.
I am trying to support custom domain endpoints for the new opensearch module PR #859. This requires setting up a certificate which is issued by a trusted authority; having a self-signed imported cert would not work. It would be sufficient to support private certificates.
Issue Type
Feature Idea
Component Name
aws_acm
Additional Information
The request-certificate operation would require new attributes:
domain-name
validation-method (email, dns)
List of subject-alternative-names
idempotency-token
domain-validation-options (for email validation)
options
certificate-authority-arn
It should be easier to support and automate cert validation using DNS, assuming DNS is managed by Route53.
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Summary
The
aws_acm
module should support requesting certificates from AWS certificate manager. Currently the module only supports imported certificates.Private certificates are easier to support and automate because they do not require validation.
I am trying to support custom domain endpoints for the new
opensearch
module PR #859. This requires setting up a certificate which is issued by a trusted authority; having a self-signed imported cert would not work. It would be sufficient to support private certificates.Issue Type
Feature Idea
Component Name
aws_acm
Additional Information
The request-certificate operation would require new attributes:
It should be easier to support and automate cert validation using DNS, assuming DNS is managed by Route53.
Code of Conduct
The text was updated successfully, but these errors were encountered: