AWS systems-manager documentation change
Summary
Clarified hybrid node reregistration requirements regarding activation code reuse limits
Security assessment
Operational clarification about activation codes with no security vulnerability context. Doesn't introduce or modify security controls.
Diff
diff --git a/systems-manager/latest/userguide/fleet-manager-deregister-hybrid-nodes.md b/systems-manager/latest/userguide/fleet-manager-deregister-hybrid-nodes.md index 1256cdcb0..53fe9eb5a 100644 --- a//systems-manager/latest/userguide/fleet-manager-deregister-hybrid-nodes.md +++ b//systems-manager/latest/userguide/fleet-manager-deregister-hybrid-nodes.md @@ -9 +9,3 @@ If you no longer want to manage an on-premises server, edge device, or virtual m -If you want to reregister an on-premises server, edge device, or VM, you must use a different Activation Code and Activation ID than used to register the machine previously. The Activation Code and Activation ID must not have already been used on the maximum number of activations specified when they were created. +###### 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 in the console by choosing **Node tools** , and then choose **Hybrid activations**. If the value of **Registered instances** is less than **Registration limit** , you can reregister a machine using the same activation code and ID. If it's greater, you must use a different activation code and ID.