AWS systems-manager documentation change
Summary
Clarified installation instructions for SSM Agent on non-EC2 Linux nodes and added requirement for new Activation Code/ID when reregistering.
Security assessment
Emphasizes security best practice (using fresh credentials for reregistration) but does not address a specific disclosed vulnerability.
Diff
diff --git a/systems-manager/latest/userguide/hybrid-multicloud-ssm-agent-install-linux.md index 996a10c0f..d026b5290 100644 --- a/systems-manager/latest/userguide/hybrid-multicloud-ssm-agent-install-linux.md +++ b/systems-manager/latest/userguide/hybrid-multicloud-ssm-agent-install-linux.md @@ -9 +9 @@ Setting up private key auto rotationDeregister and reregister a managed node (Li -This topic describes how to install AWS Systems Manager SSM Agent on non EC2 (Amazon Elastic Compute Cloud) Linux machines in a [hybrid and multicloud](./operating-systems-and-machine-types.html#supported-machine-types) environment. If you plan to use Windows Server machines in a hybrid and multicloud environment, see the next step, [Install SSM Agent on hybrid Windows Server nodes](./hybrid-multicloud-ssm-agent-install-windows.html). +This topic describes how to install AWS Systems Manager SSM Agent on non-EC2 (Amazon Elastic Compute Cloud) Linux machines in a [hybrid and multicloud](./operating-systems-and-machine-types.html#supported-machine-types) environment. For information about installing SSM Agent on EC2 instances for Linux, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](./manually-install-ssm-agent-linux.html). @@ -11,5 +11 @@ This topic describes how to install AWS Systems Manager SSM Agent on non EC2 (Am -###### Important - -This procedure is for machine types other than EC2 instances for a hybrid and multicloud environment. To download and install SSM Agent on an EC2 instance for Linux, see [Manually installing and uninstalling SSM Agent on EC2 instances for Linux](./manually-install-ssm-agent-linux.html). - -Before you begin, locate the Activation Code and Activation ID that were sent to you after you completed the hybrid activation earlier in [Create a hybrid activation to register nodes with Systems Manager](./hybrid-activation-managed-nodes.html). You specify the Code and ID in the following procedure. +Before you begin, locate the Activation Code and Activation ID that were generated during the hybrid activation process, as described in [Create a hybrid activation to register nodes with Systems Manager](./hybrid-activation-managed-nodes.html). You specify the Code and ID in the following procedure. @@ -33 +29 @@ For an HTTPS proxy server, enter the following commands at the command line: - 3. Copy and paste one of the following command blocks into SSH. Replace the placeholder values with the Activation Code and Activation ID generated when you create a managed-node activation, and with the identifier of the AWS Region you want to download SSM Agent from, then press `Enter`. + 3. Copy and paste one of the following command blocks into SSH. Replace the placeholder values with the Activation Code and Activation ID generated during the hybrid activation process and with the identifier of the AWS Region you want to download SSM Agent from, then press `Enter`. @@ -172,2 +167,0 @@ On all other Linux installations: -You can reregister a machine after you deregister it. Use the following procedure to reregister a machine. After you complete the procedure, your managed node is displayed again in the list of managed nodes. - @@ -175,0 +170,2 @@ You can reregister a machine after you deregister it. Use the following procedur +You can reregister a machine after you deregister it. However, you must use a different Activation Code and Activation ID than were used previously to register the machine. +