AWS systems-manager medium security documentation change
Summary
Added security warning about improper installation methods for non-EC2 systems and emphasized hybrid CLI tool usage
Security assessment
Explicitly warns that using EC2 installation methods on non-EC2 systems could lead to security vulnerabilities, indicating a security-conscious documentation update to prevent misconfigurations.
Diff
diff --git a/systems-manager/latest/userguide/manually-install-ssm-agent-windows.md b/systems-manager/latest/userguide/manually-install-ssm-agent-windows.md index 0b0c3153b..2f0f95f69 100644 --- a//systems-manager/latest/userguide/manually-install-ssm-agent-windows.md +++ b//systems-manager/latest/userguide/manually-install-ssm-agent-windows.md @@ -24 +24,3 @@ SSM Agent requires Windows PowerShell 3.0 or later to run certain AWS Systems Ma -###### Note +###### Installation on other machine types + +This procedure in this topic applies specifically to installing or reinstalling SSM Agent on an EC2 instance for Windows Server. For on-premises servers, virtual machines, or other non-EC2 environments, use the `ssm-setup-cli` tool as described in [Install SSM Agent on hybrid Windows Server nodes](./hybrid-multicloud-ssm-agent-install-windows.html). @@ -26 +28 @@ SSM Agent requires Windows PowerShell 3.0 or later to run certain AWS Systems Ma -This procedure applies to installing or reinstalling SSM Agent on an EC2 instance for Windows Server. If you need to install the agent on an on-premises server or a virtual machine (VM) so it can be used with Systems Manager, see [How to install the SSM Agent on hybrid Windows nodes](./hybrid-multicloud-ssm-agent-install-windows.html). +Using EC2 installation procedures on non-EC2 systems can potentially result in security vulnerabilities. The `ssm-setup-cli` tool provides additional security protections for non-EC2 machines.