AWS systems-manager documentation change
Summary
Added note about activation code reuse limits and updated command instructions for clarity.
Security assessment
The changes clarify activation code reuse conditions and command syntax but do not address a security vulnerability or introduce security features. The note about registration limits is operational guidance.
Diff
diff --git a/systems-manager/latest/userguide/hybrid-multicloud-ssm-agent-install-linux.md b/systems-manager/latest/userguide/hybrid-multicloud-ssm-agent-install-linux.md index d026b5290..2351bfaa6 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 @@ -168 +168,3 @@ On all other Linux installations: -###### To reregister a managed node on a non-EC2 Linux machine +###### Note + +You can reregister an on-premises server, edge device, or VM using the same activation code and ID as long as you haven't reached the instance limit for the designated activation code and ID. You can verify the instance limit for an activation code and ID by calling the [describe-activations](https://docs.aws.amazon.com/cli/latest/reference/ssm/describe-activations.html) API using the AWS CLI. After you run the command, verify that the value of `RegistrationCount` doesn't exceed `RegistrationLimit`. If it does, you must use a different activation code and ID. @@ -170 +172 @@ On all other Linux installations: -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. +###### To reregister a managed node on a non-EC2 Linux machine @@ -174 +176 @@ You can reregister a machine after you deregister it. However, you must use a di - 2. Run the following command. Be sure to 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 Region you want to download the SSM Agent from. + 2. Run the following command. Be sure to replace the placeholder values with the Activation Code and Activation ID generated when you created a managed-node activation, and with the identifier of the Region you want to download the SSM Agent from.