AWS Node Termination Handler
AWS Node Termination Handler is a Helm chart that deploys a Kubernetes component to gracefully drain and cordon Amazon EC2 nodes before maintenance, Spot…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
50/100 Fair
- Maintained
- 79last commit 8 days ago
- Popular
- 651,764 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 07 serious findings, 6 minor, CI, tests, OpenSSF Scorecard 4.1/10
Based on 4 of 5 factors.
Security check: 7 serious findings
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.45.0, which has a known critical vulnerability (Go)
Automated checks on commit be7b2ed, 24 Oct 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 1,764
- Open issues
- 13
- Last commit
- 2026-11-12
- Latest release
- v1.25.6
- License
- Apache-2.0
- Activity
- rising
Checked today - source: GitHub (aws/aws-node-termination-handler)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install it in kube-system with Helm Run the Helm install in the kube-system namespace and set a real chart version. This is the default place the app expects for its cluster-level permissions, and missing either can leave the release unable to manage nodes or hard to update. source
- Use a secret for webhook alerts If you want Slack or other alerts, create a Kubernetes secret (a stored password-like value) with your webhook URL and point the chart to it with webhookURLSecretName. That keeps the URL out of command history and makes sure termination notices actually go to your alert destination. source
- Pick the AWS warnings to watch Set the on/off feature flags to match the AWS warnings you care about, such as enableSpotInterruptionDraining and enableRebalanceMonitoring. If a flag is off, that warning is ignored and pods may not drain before the node is taken away. source
- Watch supported termination events Configure the handler to watch Amazon EC2 events that affect your nodes, including scheduled maintenance, Spot interruptions, Auto Scaling Group (ASG) scale-in, Availability Zone (AZ) rebalance, and termination through the API or Console. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does aws-node-termination-handler need a pod on each node for Spot and EC2 event handling?
The IMDS Monitor runs a small pod on each host to monitor IMDS paths like /spot and /events. It reacts by draining and/or cordoning the corresponding node.
Can aws-node-termination-handler use an SQS queue for interruption events?
The Queue Processor monitors an SQS queue of events from Amazon EventBridge. It handles ASG lifecycle events, EC2 status change events, Spot Interruption Termination Notice events, and Spot Rebalance Recommendation events.
How can I track how often nodes are terminated by the handler?
The built-in metrics endpoint may be unavailable after the node goes down. This can make tracking termination frequency over time difficult because the pod may stop reporting after the node is gone.
Can it be deployed to self-managed Amazon EKS worker nodes?
AWS guidance describes deploying Node Termination Handler in a self-managed worker node in an Amazon EKS cluster. It can be automated through a CI/CD pipeline.
Answers sourced from docs.aws.amazon.com, github.com, github.com, www.reddit.com
Community
- AWS Node Termination Handler : r/devopspro - Reddit (reddit)
- Is there a way to monitor "node-termination-handler ... - Reddit (reddit)
Collected 48 days ago - public community threads