Cloud concept · Updated

Certificate management - Certificate management is the lifecycle control of digital certificates and their associated private keys to establish trusted identities and secure connections.

In short

It covers certificate issuance, validation, deployment, renewal, revocation, and retirement, together with protection of the keys and trust chains that make certificates useful. In cloud environments, effective certificate management prevents outages from expired certificates and supports authenticated, encrypted communication across public endpoints, internal services, accounts, and Regions.

Cloud Concepts Hub →

6 key aspects of Certificate management

Effective certificate management combines trusted issuance, protected keys, enforced TLS, automated renewal, compromise response, and explicit regional planning.

01
Identity and trust validation

Choose public or private trust according to the clients that must authenticate the endpoint. Validate certificate chains, hostname coverage, validity periods, and intended key usage rather than treating any installed certificate as trustworthy.

02
Private-key protection

Restrict access to certificate private keys and prefer managed custody where supported. When keys must be distributed, use encrypted storage, tightly scoped permissions, and deployment paths that avoid logs, source repositories, and container images.

03
TLS enforcement across connection segments

Configure listeners, TLS security policies, and service-specific deny controls to prevent unencrypted access. Evaluate frontend and backend connections independently, including whether each endpoint validates its peer.

04
Automated lifecycle operations

Automate issuance, renewal, deployment, and retirement, with monitoring that detects failed renewals before expiration. Verify that applications actually serve the replacement certificate after deployment.

05
Revocation and compromise response

Prepare to replace compromised keys, issue replacement certificates, and revoke affected certificates. Revocation only helps when the relevant clients perform and enforce revocation checks.

06
Regional and cryptographic boundaries

Inventory certificates, authorities, and deployment dependencies by account and Region. Keep certificate renewal separate from encryption-key rotation, and do not assume multi-Region encryption keys replicate certificates.

Cloud services for Certificate management

ACM supplies certificates to supported endpoints such as Elastic Load Balancing and CloudFront, while AWS Private CA supplies private trust for internal identities. Endpoint configuration must then enforce approved TLS settings and protect each connection segment independently. Regional load balancers use certificates in their own Regions, whereas CloudFront requires ACM viewer certificates in US East (N. Virginia). KMS addresses a separate layer: cryptographic key operations and access controls, not certificate issuance or renewal. Together, these services support secure connections only when ownership, trust distribution, regional placement, renewal monitoring, and compromise response are explicitly designed.

AWS Private Certificate AuthorityAWS Private Certificate Authority

Provides private certificate authorities for internal identities and private PKI hierarchies. Engineers must manage issuance permissions, client trust distribution, CA lifecycle, and appropriate revocation mechanisms.

Amazon CloudFrontAmazon CloudFront

Uses certificates to secure viewer connections for custom domain names; ACM viewer certificates must be in US East (N. Virginia). Viewer protocol policy and origin protocol policy independently control the viewer and origin connection segments.

Certificate management exam questions

Real practice exam questions on Certificate management, with the correct answer and its explanation. Answer them with every option in the exam simulator.

DVA-C02

A company hosts an application at portal.example.com behind an Application Load Balancer (ALB) in eu-west-1. The ALB has an HTTPS listener on port 443 that uses an AWS Certificate Manager (ACM) certificate for portal.example.com. The company must also serve accounts.example.net through the same listener without disrupting the existing domain. Company policy requires a separate certificate for each domain, and all clients support Server Name Indication (SNI). Which solution meets these requirements with the least operational overhead?

Show answerCORRECT ANSWER

Request and validate an ACM certificate for accounts.example.net in eu-west-1. Add it to the existing HTTPS listener's certificate list while retaining the existing certificate.

An ALB HTTPS listener supports multiple certificates through SNI. Adding the new certificate to the listener's certificate list allows the ALB to select the appropriate certificate for each client's requested hostname. Both certificates remain independently managed in ACM, and neither a new listener nor a new load balancer is required.

SCS-C03

A company operates several public Application Load Balancers (ALBs) in one AWS Region. Their HTTPS listeners reference the same imported certificate ARN in AWS Certificate Manager (ACM). Company policy requires certificates from an approved external public certificate authority (CA), which the clients already trust.

The certificate will expire in 14 days. The external CA has supplied a replacement certificate for the same DNS names, a newly generated matching private key, and the intermediate certificate chain. The replacement uses the same key algorithm and key size as the existing certificate. A certificate-management automation role can import certificates into ACM but cannot modify ALB listeners.

Which action should the security engineer automate to deploy the replacement certificate to all the ALBs without changing listener configurations?

Show answerCORRECT ANSWER

Import the replacement certificate, its matching new private key, and its intermediate certificate chain into ACM, specifying the existing certificate ARN.

Reimporting an externally issued certificate into its existing ACM ARN preserves its associations with integrated AWS services. ACM deploys the replacement to the associated ALBs without listener configuration changes. The replacement certificate must be supplied with its matching private key and appropriate certificate chain.

SAA-C03

A company uses an ACM-issued public certificate on an Application Load Balancer (ALB). The certificate was validated through DNS and previously renewed automatically. The company recently moved its authoritative public DNS to a different provider, copying only records used to route application traffic. The application is still accessible over HTTPS, but ACM now reports that the certificate's managed renewal is pending validation. The certificate expires in 20 days.

A solutions architect must restore automatic renewal without replacing the certificate or changing the ALB listener. Which action should the solutions architect take?

Show answerCORRECT ANSWER

Retrieve the certificate's DNS validation CNAME records from ACM, add them at the new authoritative public DNS provider, and retain them for subsequent renewals.

ACM requires the DNS validation CNAME records to remain publicly resolvable for automatic renewal of a DNS-validated certificate. Restoring those records allows ACM to validate domain ownership again. Because the certificate remains attached to the ALB, ACM can renew and deploy it without replacing the certificate or changing the listener.

Practice Certificate management in a full exam

Questions on Certificate management in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Certificate management

3 min read

Certificate management connects identity, trust, and cryptography. An X.509 certificate binds a public key to an identity, such as a DNS name, through a certificate authority's signature. During a typical TLS connection, the client validates the certificate chain, checks the requested hostname against the certificate's subject alternative names, checks validity dates, and verifies that the server controls the corresponding private key. The certificate is not secret; its private key must remain protected. A valid certificate alone does not require encryption or determine which TLS versions a server accepts.

The lifecycle starts with identifying endpoints, owners, trust requirements, and supported algorithms. Public-facing applications generally need certificates chaining to a publicly trusted authority. Internal applications can use a private certificate authority, but their clients must receive and trust the appropriate root certificates. Issuance controls should verify domain ownership or workload identity and restrict who can request certificates for sensitive names. Mutual TLS adds client certificate authentication, requiring management of both server and client identities.

Deployment must be paired with transport enforcement. For example, an AWS Application Load Balancer can use an HTTPS listener with an AWS Certificate Manager certificate and a security policy that permits approved TLS protocol versions and cipher suites. An HTTP-to-HTTPS redirect helps normal users, but the initial HTTP request remains unencrypted. Where cleartext connections are prohibited, do not expose an HTTP listener. For services such as object storage, use supported resource-policy conditions to deny requests that do not use secure transport.

Consider every network segment separately. TLS termination at a load balancer protects the client-to-load-balancer connection, not automatically the connection to application targets. Configure HTTPS targets when that segment also requires encryption. Encryption and authenticated peer identity are separate requirements: Application Load Balancers do not validate target certificates, so HTTPS targets alone do not establish validated backend identity. Applications with stricter identity requirements need an architecture that performs the required certificate validation.

Renewal must include successful deployment, not merely issuance of a replacement. Managed services can renew eligible certificates and update supported integrations, but imported certificates require a separate renewal process. Certificates deployed to application hosts need automation to distribute replacements and reload processes safely. Track expiration, renewal failures, certificate attachments, and ownership. For compromised keys, replace the key and certificate, revoke the old certificate where supported, and consider whether clients actually check certificate revocation lists or Online Certificate Status Protocol responses.

Regional scope also matters. AWS Certificate Manager certificates are regional resources; regional load balancers need certificates in their own Regions, while CloudFront viewer certificates managed by ACM must be in US East (N. Virginia). Plan issuance or supported import workflows for each required Region rather than assuming certificates replicate automatically. Private certificate authorities also require explicit regional availability and recovery planning.

Certificate keys and data-encryption keys serve different purposes. AWS KMS customer managed keys provide cryptographic operations and access controls, but they do not replace a certificate authority or issue TLS certificates. KMS multi-Region keys are related keys with shared key material, not a mechanism for replicating certificates or private CA resources. Automatic rotation of a symmetric KMS key does not renew a TLS certificate. Managed key custody reduces exposure and operational work, while portable key material increases deployment flexibility but also increases the burden of secure distribution, access control, auditing, and compromise response.

Learn Certificate management in lessons

4 short lessons on Certificate management in 3 certification courses.

Open the lessons