Certificate authority meta-resource for automated rotation and renewal

1. A computer-implemented method to automatically rotate a certificate authority (CA) of a public key infrastructure (PKI) hierarchy, comprising:

creating a plurality of CA meta-resources that correspond to a plurality of CAs, wherein:

a first CA meta-resource of the plurality of CA meta-resources corresponds to the CA, includes a first reference to the CA, and is configured to maintain and monitor a plurality of CA information associated with the CA; and

the plurality of CA information includes a first status associated with the first reference to the CA;

determining, using the first CA meta-resource and based at least in part on the plurality of CA information, that the CA is to be rotated with a new CA;

automatically creating the new CA, based at least in part on the plurality of CA information, to replace the CA;

activating the new CA;

creating a second reference in the first CA meta-resource to the new CA;

assigning, in the first CA meta-resource, a second status associated with the second reference to the new CA as active, such that calls to the first CA meta-resource for issuance of a certificate are assigned to the new CA;

modifying the first status associated with the first reference to the CA to deactivated;

notifying, by the first CA meta-resource, a trust store associated with the PKI hierarchy of the new CA;

distributing trust of the new CA to the PKI hierarchy;

identifying an issue with the PKI hierarchy in connection with the new CA; and

based at least in part on the identification of the issue:

modifying the second status associated with the second reference to the new CA to deactivated; and

modifying the first status associated with the first reference to the CA to activated, such that calls to the first CA meta-resource for issuance of certificates are assigned to the CA.

2. The computer-implemented method of claim 1 , wherein the plurality of CA information includes a grace period and the new CA is activated at an expiration of the grace period.

3. The computer-implemented method of claim 1 , wherein creating the new CA includes, at least:

generating a new key pair in connection with the new CA, the new key pair including a public key;

generating a certificate signing request in connection with the new CA, wherein the certificate signing request includes the public key and an identifier of the new CA;

verifying, by a parent CA, the certificate signing request; and

issuing, based at least in part on the verification of the certificate signing request, a new certificate for the new CA, wherein the new certificate includes the public key.

4. The computer-implemented method of claim 1 , wherein the method is performed without manual configuration of the PKI hierarchy.

5. A computing system, comprising:

one or more processors; and

a memory storing program instructions that, when executed by the one or more processors, cause the one or more processors to at least:

create a plurality of certificate authority (CA) meta-resources that correspond to a plurality of CAs, wherein:

a first CA meta-resource of the plurality of CA meta-resources corresponds to a first CA of the plurality of CAs;

the first CA meta-resource is configured to maintain a plurality of CA information and an identifier indicating an active issuing CA; and the identifier indicates that the first CA is the active issuing CA;

determine, using the first CA meta-resource and based at least in part on the plurality of CA information, that the first CA is to be replaced with a new CA;

automatically create, using the first CA meta-resource, the new CA based at least in part on the plurality of CA information;

activate, using the first CA meta-resource, the new CA;

modify the identifier of the first CA meta-resource to indicate that the new CA is the active issuing CA, such that calls to the first CA meta-resource for issuance of a certificate are assigned to the new CA;

identify an issue with the new CA; and

based at least in part on identification of the issue:

deactivate, using the first CA meta-resource, the new CA; and

modify the identifier of the first CA meta-resource to indicate that the first CA is the active issuing CA, such that calls to the first CA meta-resource for issuance of certificates are assigned to the first CA.

6. The computing system of claim 5 , wherein automatic creation of the new CA includes, at least:

generating a new key pair for the new CA;

generating a certificate signing request using the new key pair;

transmitting the certificate signing request to a parent CA;

verifying, by the parent CA, the certificate signing request; and

generating a new CA certificate for the new CA based at least in part on the verification of the certificate signing request.

7. The computing system of claim 5 , wherein the first CA meta-resource maintains a status associated with the new CA and the program instructions, when executed by the one or more processors, further cause the one or more processors to at least:

assign, prior to activation of the new CA, the status associated with the new CA as prepared.

8. The computing system of claim 7 , wherein the first CA meta-resource maintains a second status associated with the first CA and wherein the program instructions, when executed by the one or more processors, further cause the one or more processors to at least:

modify the status of the new CA from prepared to active; and

maintain the second status of the first CA as active, such that the identifier of the first CA meta-resource indicates that the new CA and the first CA are the active issuing CAs, so that calls to the first CA meta-resource for issuance of a certificate are assigned to one of the new CA or the first CA.

9. The computing system of claim 8 , wherein the program instructions, when executed by the one or more processors, further cause the one or more processors to at least:

modify the second status of the first CA from active to deactivated, such that the identifier of the first CA meta-resource indicates that the new CA is the active issuing CA, so that calls to the first CA meta-resource for issuance of a certificate are assigned to the new CA.

10. The computing system of claim 9 , wherein the program instructions, when executed by the one or more processors, further cause the one or more processors to at least:

notify, using the first CA meta-resource, a trust store service to distribute trust of the new CA to a public key infrastructure (PKI) hierarchy.

11. The computing system of claim 5 , wherein the plurality of CA information includes user provided rotation and renewal information associated with the first CA.

12. The computing system of claim 5 , wherein the plurality of CA information includes rotation and renewal information associated with the first CA, and wherein the program instructions, when executed by the one or more processors, further cause the one or more processors to at least:

determine, based at least in part on a configuration of a public key infrastructure (PKI) hierarchy, recommended rotation and renewal information associated with the first CA.

13. The computing system of claim 5 , wherein the first CA meta-resource includes at least one of:

a certificate renewal term;

a certificate renewal grace period;

a certificate rotation term;

a certificate rotation grace period;

a CA identifier, or

a parent CA identifier.

14. A computer-implemented method, comprising:

creating a plurality of certificate authority (CA) meta-resources that correspond to a plurality of certificates and are configured to maintain and monitor a certificate status and certificate renewal and rotation information associated with the plurality of certificates, so as to automatically initiate at least one of automatic rotation or renewal of the plurality of certificates;

determining, using a first CA meta-resource of the plurality of CA meta-resources and based at least in part on the certificate renewal and rotation information of the first CA meta-resource, that a first corresponding certificate of the plurality of certificates is to be replaced;

in response to determining that the first corresponding certificate is to be replaced, automatically generating a new certificate to replace the first corresponding certificate;

creating a reference to the new certificate in the first CA meta-resource;

activating, using the first CA meta-resource, the new certificate and assigning a status associated with the reference to the new certificate as active;

modifying the certificate status associated with the first corresponding certificate to deactivated;

distributing trust of the new certificate;

identifying an issue in connection with the new certificate;

based at least in part on the identification of the issue, modifying the status of the new certificate to deactivated; and

based at least in part on the identification of the issue, modifying the certificate status associated with the first corresponding certificate to active.

15. The computer-implemented method of claim 14 , wherein the new certificate is one of:

a root certificate;

a CA certificate; or

a leaf certificate.

16. The computer-implemented method of claim 14 , wherein the first CA meta-resource includes at least one of:

a certificate renewal term;

a certificate renewal grace period;

a certificate rotation term;

a certificate rotation grace period;

a CA identifier, or

a parent CA identifier.