# Public Key Infrastructure

Public Key Infrastructure is the system of certificates, trusted authorities, policies, and processes used to bind identities to public keys and manage that trust over time.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/public-key-infrastructure

> Public Key Infrastructure (PKI) allows systems to verify that a public key belongs to the expected server, user, device, or organization. In cloud environments, it supports authenticated TLS connections, mutual TLS, and digital signatures while requiring careful protection of private keys and management of certificate lifecycles.

Practice exams covering Public Key Infrastructure: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Public Key Infrastructure

PKI combines verifiable identity, protected private keys, explicit trust relationships, and dependable certificate lifecycle operations.

1. **Identity binding and certificate validation**: Certificates bind public keys to identities under an issuer's policy. Clients must validate the chain, expected identity, validity period, and permitted usage rather than merely checking that a certificate is signed.
2. **Trust anchors and CA hierarchy**: Trust begins with root certificates explicitly accepted by clients. Use subordinate CAs to separate environments or workloads and limit routine exposure of root signing keys.
3. **Private-key protection**: Protect private keys with restrictive access controls and hardware-backed storage where appropriate, especially for CA signing keys. Certificate distribution can be broad, but private-key distribution should be minimized and carefully controlled.
4. **Automated certificate lifecycle**: Automate issuance, deployment, renewal, and expiration monitoring as one workflow. Confirm that renewed certificates are actually loaded by endpoints and that imported or custom-managed certificates have an explicit renewal owner.
5. **Revocation and compromise response**: Plan how clients obtain and enforce revocation information, including behavior when status services are unavailable. Replacing a compromised key requires issuing and deploying a certificate for a new key, not merely renewing a certificate that reuses the compromised key.
6. **Regional resilience and consistent trust**: Design regional issuance and certificate deployment independently from cryptographic key replication. Distribute appropriate trust anchors and intermediate certificates, and test authentication during regional failover.

## Cloud services for Public Key Infrastructure

AWS Private CA establishes private certificate trust, while ACM manages certificate workflows and deployment to supported endpoints. AWS KMS addresses cryptographic key management rather than certificate issuance; its permissions, rotation, and multi-Region capabilities must not be confused with PKI lifecycle controls. AWS CloudHSM is an option for protecting signing keys used by self-managed CA software. CloudTrail provides an audit trail for supported administrative and lifecycle actions. Together, these services support separate responsibilities for trust, certificate delivery, key protection, and auditing, but engineers must still design client trust stores, authorization, revocation enforcement, and regional recovery.

- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: Provides managed root and subordinate private CAs for issuing certificates to internal workloads, users, and devices. It supports certificate revocation mechanisms, but clients must trust the appropriate hierarchy and enforce certificate validation.
- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: Provides dedicated hardware security modules that can protect private keys for compatible, self-managed CA software. The organization remains responsible for CA software, issuance policy, certificate lifecycle management, and resilient HSM architecture.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Records supported API activity for services involved in certificate and key management. Use these records to investigate CA configuration changes, issuance activity, and key administration, while separately monitoring endpoint certificate validity and deployment.

## Public Key Infrastructure exam questions

Real practice exam questions on Public Key Infrastructure, with the correct answer and its explanation.

### Question 1 (DVA-C02)

**Question:**

A development team creates temporary test workloads that authenticate to an internal API by using mutual TLS. Each workload needs a certificate that is valid for 24 hours. The API must validate all workload certificates against a shared private CA trust chain without adding individual workload certificates to its trust store. Security policy requires an AWS-managed issuing CA whose operating mode prevents issuance of certificates valid for more than 7 days, even if the certificate-requesting code is misconfigured. Which solution meets these requirements?

**Correct answer:** Create an AWS Private CA in short-lived certificate mode. Generate a key pair and certificate signing request for each workload, and use the AWS Private CA IssueCertificate API to request a certificate with a validity period of 1 day.

**Explanation:** Short-lived certificate mode limits issued certificates to a maximum validity of 7 days. Direct issuance through the AWS Private CA API supports requesting 24-hour certificates. Configuring the API to trust the issuing CA's chain allows it to validate new workload certificates without trusting each certificate individually.

### Question 2 (SAP-C03)

**Question:**

A company operates 20,000 telemetry agents in its data centers and in another cloud provider. The agents use IAM Roles Anywhere to obtain temporary credentials for uploading data to Amazon S3. The company wants to replace its self-managed certificate issuer with a managed private CA.

Security policy requires the issuing CA itself to reject requests for end-entity certificates with validity periods longer than 7 days, even if an authorized enrollment service requests a longer period. Agents must normally receive certificates valid for 48 hours and renew them every 24 hours without interruption. The CA must remain usable for several years without replacement.

Each agent generates and protects its own private key. An existing authenticated enrollment service can submit certificate signing requests, retrieve issued certificates, and distribute certificates to agents. The company can extend this service with scheduled renewal logic. The IAM Roles Anywhere trust anchor, profile, and role permissions will be configured correctly for the selected CA.

Which certificate issuance and renewal design meets these requirements?

**Correct answer:** Create an AWS Private CA in short-lived certificate mode with a CA certificate valid for several years. Have the enrollment service use IssueCertificate to request 48-hour certificates from agent-generated CSRs, retrieve the certificates, and replace them on agents every 24 hours.

**Explanation:** Short-lived certificate mode enforces a maximum end-entity certificate validity period of 7 days without requiring the CA certificate itself to expire within 7 days. Direct issuance supports agent-generated CSRs and locally protected private keys. The enrollment service provides the required renewal and distribution because certificates issued directly through the Private CA API are not automatically renewed by ACM.

### Question 3 (SCS-C03)

**Question:**

A company uses AWS Private CA to issue certificates for internal TLS services. All clients trust only the company's current private root CA. The company must replace this root CA with a new root CA that has a different key pair. Neither CA is compromised.

Client trust-store updates and service certificate deployments occur asynchronously over several weeks. Existing certificates will remain valid throughout the migration. The company prohibits cross-signing between the two CA hierarchies and requires uninterrupted TLS connectivity with certificate validation enabled throughout the migration.

Which migration plan meets these requirements?

**Correct answer:** Add the new root certificate to client trust stores while retaining the old root certificate. Confirm that all clients trust both roots before deploying service certificates from the new hierarchy. Remove the old trust anchor only after all services have migrated and no required certificate chains depend on it.

**Explanation:** An overlapping trust period allows clients to validate certificates from either hierarchy during asynchronous service deployments. Distributing the new trust anchor first prevents failures when services begin presenting new certificates. Retaining the old trust anchor until its dependencies are gone preserves connectivity to services that have not yet migrated.

### Question 4 (DOP-C02)

**Question:**

A company uses AWS Private Certificate Authority to issue server certificates for internal services. Deployment pipelines generate private keys and certificate signing requests (CSRs), then call IssueCertificate directly. All internal clients trust the issuing hierarchy and validate the server's DNS subject alternative name (SAN).

A security test shows that a compromised service's pipeline can obtain a valid certificate containing another service's DNS name. The pipelines use the same issuing CA, and each pipeline must continue to request certificates automatically. A security-owned registry maps each pipeline's IAM role to its permitted DNS names. Pipeline owners cannot modify this registry or security-managed IAM permissions, but they can submit arbitrary CSRs.

A DevOps engineer must prevent a pipeline from obtaining certificates for another service's identity while preserving automated issuance. Which solution meets these requirements?

**Correct answer:** Remove direct IssueCertificate access from pipeline roles. Provide an IAM-authenticated issuance broker that obtains the caller's role from the authenticated request context, checks every requested DNS SAN against that role's registry entry, and rejects unauthorized names. Allow only the broker's role to issue certificates, using a fixed server-certificate template.

**Explanation:** A CA signature makes the asserted identity trusted, so issuance must verify that the requester is authorized to claim that identity. The broker binds every requested DNS SAN to an independently authenticated IAM role and a security-controlled authorization mapping. Removing direct issuance access prevents pipelines from bypassing these checks, while the broker preserves automated issuance.

## Practice Public Key Infrastructure in a full exam

Questions on Public Key Infrastructure in each practice exam, with every answer option and an explanation for each:

- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 4 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 4 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 4 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 3 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Public Key Infrastructure

Public Key Infrastructure establishes trust in public keys through digitally signed certificates, usually using the X.509 standard. A certificate associates a public key with an identity and includes information such as its issuer, validity period, and permitted uses. The corresponding private key remains confidential. A certificate is not a secret, and possessing a copy does not enable an attacker to impersonate its owner without the private key.

A certificate authority (CA) signs certificates after the required identity checks and authorization steps. Clients validate a certificate chain from the presented certificate through any intermediate CAs to a root they already trust. Root trust comes from a configured trust store, not simply from a root certificate being self-signed. Production hierarchies often keep the root CA offline and use subordinate CAs for routine issuance, reducing exposure of the most consequential signing key.

During a TLS connection, the client checks the certificate chain, validity dates, intended usage, and expected identity, such as a DNS name in the subject alternative name extension. The server proves possession of the corresponding private key through the TLS protocol. TLS then uses symmetric session keys to protect application traffic; certificates do not directly encrypt all transmitted data. With mutual TLS, both peers authenticate using certificates, but applications still need authorization rules to decide what an authenticated peer may do.

Publicly trusted certificates are appropriate for endpoints accessed by ordinary browsers and other clients using public trust stores. Private certificates support internal services, enterprise devices, and workloads whose clients can be configured to trust an organizational CA. For example, an internal payment API can require client certificates issued by a dedicated subordinate CA. Issuance policy and application authorization should prevent a certificate intended for one workload from granting unrestricted access to unrelated services.

Certificate management includes secure key generation, certificate signing requests, controlled issuance, deployment, renewal, revocation, and eventual retirement. A signing request contains a public key and requested identity information, not the private key. Automating renewal reduces expiration outages, but issuing a replacement certificate is insufficient unless it reaches every endpoint and the service reloads it. Revocation through certificate revocation lists or the Online Certificate Status Protocol also depends on client support and configuration; publishing revocation information does not guarantee that every client checks it. Short-lived certificates reduce the remaining lifetime of compromised credentials but increase reliance on dependable issuance automation.

In AWS, Private Certificate Authority provides managed private CAs, while Certificate Manager handles certificate provisioning and supported deployment and renewal workflows. AWS KMS manages cryptographic keys but is not a CA and does not provide an X.509 certificate issuance lifecycle. KMS asymmetric signing can support custom signing applications, but it does not replace identity validation, certificate policy, or revocation infrastructure. Protect CA signing keys with tightly controlled access and hardware-backed cryptography, and separate certificate-request permissions from CA administration.

Multi-Region design requires separate planning for key availability, certificate deployment, and trust. One approach uses regional subordinate CAs beneath a common organizational root, allowing clients to trust a shared hierarchy while issuance remains regionally distributed. AWS Private CA resources are regional, and creating another CA does not replicate an existing CA's signing key. Likewise, related KMS multi-Region keys share key material but do not replicate certificates, trust stores, or a PKI. Certificates for regional AWS endpoints generally need deployment in the endpoint's Region; CloudFront requires ACM certificates in US East (N. Virginia). Test regional failover, renewal, and revocation access before an outage.

The main trade-off is operational control versus operational responsibility. A private hierarchy gives an organization control over identities and issuance policy, but requires trust-store distribution, monitoring, incident response, and recovery planning. A compromised leaf key usually affects its certificate identity; a compromised CA signing key can undermine every identity within that CA's scope. Minimize that scope through subordinate hierarchies, issuance restrictions, least-privilege administration, and auditable lifecycle operations.

## Learn Public Key Infrastructure in lessons

4 short lessons on Public Key Infrastructure in 3 certification courses.

- SAP-C03: Public Key Infrastructure: certificate trust for hybrid workloads (Premium), https://app.blowstack.com/lessons/public-key-infrastructure-certificate-trust-for-hybrid-workloads-sap-c03
- SCS-C03: Public Key Infrastructure: multi-Region CA hierarchies (Premium), https://app.blowstack.com/lessons/public-key-infrastructure-multi-region-ca-hierarchies-scs-c03
- DOP-C02: Public Key Infrastructure: CA trust boundaries (Premium), https://app.blowstack.com/lessons/public-key-infrastructure-ca-trust-boundaries-dop-c02
- DOP-C02: Public Key Infrastructure: automated certificate lifecycles (Premium), https://app.blowstack.com/lessons/public-key-infrastructure-automated-certificate-lifecycles-dop-c02
