Werk #22442: AWS: Changed rule settings were ignored until the cache expired
| Component | Checks & agents | ||||||
| Title | AWS: Changed rule settings were ignored until the cache expired | ||||||
| Date | Oct 8, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Previously, when you changed the rule Amazon Web Services (AWS), the AWS special agent did not always notice. For example, you might add a region, change a tag filter, or limit a service to certain names. Until its cache expired, the agent kept showing the data of the old settings: for about 5 minutes for most sections, and until midnight for Costs and usage.
This has been fixed. The agent now notices every changed setting and fetches fresh data on its next run.
After the update, the agent fetches all data from AWS once, because it sees the configuration as changed. You don't need to do anything.
Technical background
The agent stores a hash of its command line to detect configuration changes. The hash covered only the names of the options, not their values. So it changed only when an option was added or removed, not when a value changed.