AWS systems-manager documentation change
Summary
Removed details about standard/advanced instance tiers and added deprecation notice for advanced tier. Updated navigation links.
Security assessment
The changes document business model updates (tier removal and pricing changes) without addressing vulnerabilities or security controls. No security weaknesses or mitigations are mentioned.
Diff
diff --git a/systems-manager/latest/userguide/fleet-manager-managed-nodes.md b/systems-manager/latest/userguide/fleet-manager-managed-nodes.md index db1464aa6..bf672f2e3 100644 --- a//systems-manager/latest/userguide/fleet-manager-managed-nodes.md +++ b//systems-manager/latest/userguide/fleet-manager-managed-nodes.md @@ -30,12 +30 @@ The only supported feature for macOS instances is viewing the file system. -###### About Systems Manager instances tiers - -AWS Systems Manager offers a standard-instances tier and an advanced-instances tier. Both support managed nodes in your [hybrid and multicloud](./operating-systems-and-machine-types.html#supported-machine-types) environment. The standard-instances tier allows you to register a maximum of 1,000 machines per AWS account per AWS Region. If you need to register more than 1,000 machines in a single account and Region, then use the advanced-instances tier. You can create as many managed nodes as you like in the advanced-instances tier. All managed nodes configured for Systems Manager are priced on a pay-per-use basis. For more information about enabling the advanced instances tier, see [Turning on the advanced-instances tier](./fleet-manager-enable-advanced-instances-tier.html). For more information about pricing, see [AWS Systems Manager Pricing](https://aws.amazon.com/systems-manager/pricing/). - -Note the following additional information about the standard-instances tier and advanced-instances tier: - - * Advanced instances also allow you to connect to your non-EC2 nodes in a [hybrid and multicloud](./operating-systems-and-machine-types.html#supported-machine-types) environment by using AWS Systems Manager Session Manager. Session Manager provides interactive shell access to your instances. For more information, see [AWS Systems Manager Session Manager](./session-manager.html). - - * The standard-instances quota also applies to EC2 instances that use a Systems Manager on-premises activation (which isn't a common scenario). - - * To patch applications released by Microsoft on virtual machines (VMs) on-premises instances, activate the advanced-instances tier. There is a charge to use the advanced-instances tier. There is no additional charge to patch applications released by Microsoft on Amazon Elastic Compute Cloud (Amazon EC2) instances. For more information, see [Patching applications released by Microsoft on Windows Server](./patch-manager-patching-windows-applications.html). - +###### Note @@ -42,0 +32 @@ Note the following additional information about the standard-instances tier and +**Important:** Effective June 30, 2026, the advanced-instances tier has been removed. There is no longer a 1,000-instance limit for hybrid managed nodes, and you no longer need to enable a paid tier to use Session Manager on non-EC2 machines. Instead, starting September 30, 2026, Session Manager and Run Command use pay-as-you-go pricing when used on hybrid managed nodes. @@ -43,0 +34 @@ Note the following additional information about the standard-instances tier and +For more information about pricing, see [AWS Systems Manager Pricing](https://aws.amazon.com/systems-manager/pricing/). @@ -85,2 +75,0 @@ You can deregister managed nodes at any time. For example, if you're managing mu - * [Configuring instance tiers](./fleet-manager-configure-instance-tiers.html) - @@ -114 +103 @@ Controlling access to Fleet Manager -Configuring instance tiers +Resetting passwords on managed nodes