AWS eks documentation change

Service: eks · 2026-03-19 · Documentation low

File: eks/latest/userguide/auto-get-logs.md

Summary

Added documentation for NodeDiagnostic node destination and kubectl plugin for log collection

Security assessment

The change adds documentation for a new log collection method that stores logs temporarily on nodes and provides a kubectl plugin for collection. This enhances security observability and troubleshooting capabilities but doesn't address a specific security vulnerability.

Diff

diff --git a/eks/latest/userguide/auto-get-logs.md b/eks/latest/userguide/auto-get-logs.md
index e2eceab0c..2e7a92481 100644
--- a//eks/latest/userguide/auto-get-logs.md
+++ b//eks/latest/userguide/auto-get-logs.md
@@ -5 +5 @@
-PrerequisitesStep 1: Create S3 bucket destination (optional)Step 2: Create pre-signed S3 URL for HTTP PutStep 3: Create NodeDiagnostic resourceStep 4: Download logs from S3Step 5: Clean up NodeDiagnostic resource
+PrerequisitesStep 1: Create S3 bucket destination (optional)Step 2: Create pre-signed S3 URL for HTTP PutStep 3: Create NodeDiagnostic resourceStep 4: Download logs from S3Step 5: Clean up NodeDiagnostic resourceNodeDiagnostic node DestinationExample Usage
@@ -124,0 +125,16 @@ Wait approximately one minute before attempting to download the logs. Then, use
+## NodeDiagnostic `node` Destination
+
+Starting with version `v1.6.0` of the Node Monitoring Agent, there is an option to set the log collection destination to `node`. Using this destination will lead to the collection and temporary persistence of logs on the node for later collection. In addition to this functionality, within the Node Monitoring Agent’s GitHub repository is a `kubectl` plugin you can install for easy interaction and log collection. For more information, see the [documentation for the `kubectl ekslogs` plugin](https://github.com/aws/eks-node-monitoring-agent/blob/main/tools/kubectl-ekslogs/README.md).
+
+## Example Usage
+    
+    
+    # Collect NodeDiagnostic logs from a single node
+    kubectl ekslogs <node-name>
+    
+    # Collect NodeDiagnostic logs from multiple nodes
+    kubectl ekslogs <node-name-1> <node-name-2> <node-name-3>
+    
+    # Collect NodeDiagnostic logs from all nodes with a specific label
+    kubectl ekslogs -l <key>=<value>
+