aws: restore stable endInclusive bound to findings filter for inspector data stream - #19144
Merged
Conversation
efd6
force-pushed
the
s7155-aws-inspector2
branch
from
May 21, 2026 20:41
66880dd to
b177f3c
Compare
Contributor
Author
|
/test |
efd6
force-pushed
the
s7155-aws-inspector2
branch
from
May 24, 2026 21:12
b177f3c to
1ff20a7
Compare
Contributor
🚀 Benchmarks reportTo see the full report comment with |
efd6
marked this pull request as ready for review
May 24, 2026 23:29
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
approved these changes
Jun 4, 2026
…or data stream The previous fix (cd8d67e) removed endInclusive entirely from the Inspector lastObservedAt filter to prevent nextToken invalidation caused by (now) re-evaluation during pagination. However, Inspector may enforce the same oneOf schema constraint as Security Hub, which rejects filters missing the upper bound. Use a static far-future epoch value (2032-01-01T00:00:00Z) instead. Inspector validates that dates fall within [1970-01-01, 2033-01-01), likely due to a 32-bit epoch representation, so the value must stay below that ceiling. The static value never changes between pagination pages, avoiding the original nextToken invalidation.
efd6
force-pushed
the
s7155-aws-inspector2
branch
from
June 4, 2026 20:46
1ff20a7 to
55fa3ab
Compare
Contributor
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
cc @efd6 |
Contributor
|
Package aws - 6.19.2 containing this change is available at https://epr.elastic.co/package/aws/6.19.2/ |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots