Once this certificate authority has been created, it will enter a "Pending" state, and output a Certificate Signing Request. The CSR needs to be self-signed (in the case of acmpca_certificate_authority.type being "ROOT") or signed by a root certificate authority if this is meant to be a "SUBORDINATE".
After signing, you will need to use the AWS PCA CLI to manually associate the signed cert back to the certificate authortiy, which will put it in an "Active" state. See https://awscli.amazonaws.com/v2/documentation/api/latest/reference/acm-pca/index.html for console reference.
If the PCA and certs it issues are in the same account, you can use CreatePermission to configure automatic renewal.
If the PCA and ACM reside in different accounts, share the PCA using a RAM Share to allow ACM in the other account to manage the certificate.
No requirements.
Name | Version |
---|---|
aws | n/a |
Name | Type |
---|
Name | Description | Type | Default | Required |
---|---|---|---|---|
private_certificate_authority | n/a | object({ |
n/a | yes |
Name | Description |
---|---|
certificate_signing_request | n/a |