diff --git a/latest/ug/automode/automode.adoc b/latest/ug/automode/automode.adoc
index 4d6dda389..e97a66089 100644
--- a/latest/ug/automode/automode.adoc
+++ b/latest/ug/automode/automode.adoc
@@ -50,6 +50,7 @@ The following is a list of data plane components that are automated:
 *** Locks down access to files on the AMI using SELinux enforcing mode and a read-only root file system.
 *** Prevents direct access to the nodes by disallowing SSH or SSM access.
 *** Includes GPU support, with separate kernel drivers and plugins for NVIDIA and Neuron GPUs, enabling high-performance workloads. 
+*** Automatically handles link:AWSEC2/latest/UserGuide/spot-instance-termination-notices.html[EC2 Spot Instance interruption notices,type="documentation"] and EC2 Instance health events
 ** *Auto scaling*: Relying on https://karpenter.sh/docs/[Karpenter] auto scaling, EKS Auto Mode monitors for unschedulable Pods and makes it possible for new nodes to be deployed to run those pods. As workloads are terminated, EKS Auto Mode dynamically disrupts and terminates nodes when they are no longer needed, optimizing resource usage.
 ** *Upgrades*: Taking control of your nodes streamlines EKS Auto Mode's ability to provide security patches and operating system and component upgrades as needed. Those upgrades are designed to provide minimal disruption of your workloads. EKS Auto Mode enforces a 21-day maximum node lifetime to ensure up-to-date software and APIs.
 * *Load balancing*: EKS Auto Mode streamlines load balancing by integrating with Amazon's Elastic Load Balancing service, automating the provisioning and configuration of load balancers for Kubernetes Services and Ingress resources. It supports advanced features for both Application and Network Load Balancers, manages their lifecycle, and scales them to match cluster demands. This integration provides a production-ready load balancing solution adhering to {aws} best practices, allowing you to focus on applications rather than infrastructure management.