AWS systems-manager documentation change
Summary
Added troubleshooting entry for 'Encounter service side error when uploading the inventory' and updated a date
Security assessment
The change documents a race condition error in patching operations but does not indicate any security vulnerability or security feature enhancement. The date change is purely cosmetic.
Diff
diff --git a/systems-manager/latest/userguide/patch-manager-troubleshooting.md b/systems-manager/latest/userguide/patch-manager-troubleshooting.md index 8e14fd6a9..a32ef2e46 100644 --- a//systems-manager/latest/userguide/patch-manager-troubleshooting.md +++ b//systems-manager/latest/userguide/patch-manager-troubleshooting.md @@ -136,0 +137,2 @@ When a `Scan` operation runs, it overwrites the compliance details from the most + * Issue: Patching fails with 'Encounter service side error when uploading the inventory' + @@ -275 +277 @@ When a `Scan` operation runs, it overwrites the compliance details from the most - 05/01/2023 17:04:30 root [ERROR]: Error code returned from curl is 23 + 05/01/2025 17:04:30 root [ERROR]: Error code returned from curl is 23 @@ -299,0 +302,11 @@ A common example occurs with the `urllib3` package, which is found in `pip`, `yu +### Issue: Patching fails with 'Encounter service side error when uploading the inventory' + +**Problem** : When running the `AWS-RunPatchBaseline` document, you receive the following error message: + + + Encounter service side error when uploading the inventory + +**Cause** : Two commands to run `AWS-RunPatchBaseline` were running at the same time on the same managed node. This creates a race condition when initializing boto3 client during patching operations. + +**Solution** : Ensure that no State Manager association, maintenance window tasks, or other configurations that run `AWS-RunPatchBaseline` on a schedule are targeting the same managed node around the same time. +