Skip to main content
Compliance · Critical severity

ACM Certificate Expiring Soon

Once it expires every client sees a TLS error, and browsers and API clients refuse the connection outright.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

AWSprovider
Criticalseverity
Compliancewhere it shows up
Manualfix, steps written out

AWS

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Renew the ACM certificate in the 30 days before it expires.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
ACM Certificates on AWS
The fix, by hand
  1. ACM → Certificates → the resource → check expiration date + validation method.
  2. DNS-validated certs auto-renew if the validation CNAME is still in the hosted zone. Verify the CNAME exists with the value ACM lists in Domain validation.
  3. Email-validated certs require manual approval. Check the renewal email sent to the domain's WHOIS / abuse contact.
  4. If auto-renewal failed, the Renewal status field shows the error: re-add missing CNAMEs, or re-issue a fresh cert.
  5. Cut listeners (ALB / NLB / CloudFront) over to the new cert ARN before the old one expires.
  6. CloudWatch → ACM → DaysToExpiry alarm prevents future surprises. Set at 30 days.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-198
Full reference

ACM Certificate Expiring Soon

Related checks

AKS Cluster RBAC Not EnabledAzureAzure NSG Open to InternetAzureGCP Cloud SQL Instance Has Public IP EnabledGoogle CloudGCP Firewall Rule Allows All PortsGoogle CloudGCP Firewall Rule Allows Internet Access to Sensitive PortGoogle CloudGCS Bucket Does Not Enforce Public Access PreventionGoogle Cloud

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·