Can we implement EKS-AMI hardening?

As per Our Infosec team, Every server should be using Hardened AMI according to there policies.
While we do the same for EKS AMI worker nodes are terminated before starting. Any suggestions?

The issue does not name any files, tests, or entry points. Start by reviewing the EKS AMI worker-node startup and termination behavior alongside the Infosec hardening policy. Done would require a maintainer-defined approach that applies the hardened AMI without terminating workers before they start; the unanswered discussion needs clarification first.

Written by the indexing model from the issue text.