AWS Security ChangesHomeSearch

AWS systems-manager documentation change

Service: systems-manager · 2026-07-04 · Documentation low

File: systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.md

Summary

Removed note about advanced-instances tier requirement for Session Manager on non-EC2 nodes.

Security assessment

Change removes a feature availability note unrelated to security mechanisms. SSH connection documentation remains unchanged with no security implications.

Diff

diff --git a/systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.md b/systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.md
index ec6a9c3ba..7f4811e95 100644
--- a//systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.md
+++ b//systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.md
@@ -54,4 +53,0 @@ For information about installing or updating SSM Agent on a managed node, see th
-###### Note
-
-To use Session Manager with on-premises servers, edge devices, and virtual machines (VMs) that you activated as managed nodes, you must use the advanced-instances tier. For more information about advanced instances, see [Configuring instance tiers](./fleet-manager-configure-instance-tiers.html).
-