Clean Up Expired AWS ACM Certificates with Slack Approval

Automates detection and cleanup of expired AWS ACM certificates via daily scans, Slack approvals, and secure deletions to maintain a tidy AWS environment.

n8n
Clean Up Expired AWS ACM Certificates with Slack Approval

This n8n workflow automates the management of AWS ACM certificates by running on a daily schedule. It fetches all certificates using AWS ACM's listCertificates API, then loops through each to describe details and filter for expired ones based on status and expiration dates. For each expired certificate, it sends a rich Slack message with details like ARN, domain, and expiration date, awaiting admin approval via reactions (✅ to proceed).

Upon approval, the workflow securely deletes the certificate using AWS ACM's deleteCertificate API and posts a confirmation notification back to Slack. If no approval or rejection occurs, it handles gracefully without action. This ensures human oversight in critical security operations, preventing accidental deletions while proactively cleaning up unused resources.

Ideal for AWS administrators, DevOps teams, and IT ops managing SSL/TLS lifecycles. Benefits include reduced manual auditing time, enhanced security by removing expired certs that could pose risks, cost savings on unused resources, and seamless Slack integration for team collaboration. Use cases span cloud governance, compliance audits, and automated infrastructure maintenance in production environments.

$12.99
Last updated October 17, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Business Operations & ERPs workflows

More from Nikolai Vos

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.