IAM compliance automation: enforce MFA and clean up access keys in AWS
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on a schedule (every day). Along the way it connects AWS IAM and Slack.
How it runs
Trigger: On a schedule (every day).
- Get many users (AWS IAM): uses AWS IAM
- Get IAM User MFA Devices (HTTP Request): calls an HTTP API
- Filter: keeps only the items that match a condition
- Send warning message(s) (Slack): uses Slack
- Get User Access Key(s) (HTTP Request): calls an HTTP API
- Parse the list of user access key(s) (Code): runs custom JavaScript code
- Filter: keeps only the items that match a condition
- Send message and wait for response (Slack): send and wait for a reply
- Deactivate Access Key(s) (HTTP Request): calls an HTTP API
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- AWS IAM
n8n-nodes-base.awsIam - HTTP Request
n8n-nodes-base.httpRequest - Filter
n8n-nodes-base.filter - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Slack
n8n-nodes-base.slack - Code
n8n-nodes-base.code
From the author
Automated AWS IAM Compliance Workflow for MFA Enforcement and Access Key Deactivation > This workflow leverages AWS IAM APIs and n8n automation to ensure strict security compliance by continuously monitoring IAM users for MFA (Multi-Factor Authentication)…