Uploader has insufficient jitter for large deployments.
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
While jitter was added to the uploader in 2.3.136.0, the jitter window is only 30 seconds. We are seeing spikes of errors every 30 minutes as our deployment exhausts the PutInventory API quota. If increasing the jitter would increase a window of inaccessibility for the agent, perhaps a random time offset could be applied to the initial scheduling, so that the inventory upload events are not scheduled for x:00 and X:30.
https://github.com/aws/amazon-ssm-agent/blob/3dee01c80ab7a3d06abc4dbe4648283162bf7516/agent/plugins/inventory/datauploader/uploader.go#L134-L147

Contributor guide
Research direction
Start in agent/plugins/inventory/datauploader/uploader.go at lines 134-147 and inspect how the inventory upload schedule and its 30-second jitter are calculated. Reproduce or reason about deployments that exhaust the PutInventory API quota at x:00 and x:30, then verify that scheduling spreads uploads without creating an unacceptable access window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100