aws: fix handling of last response body in guardduty data stream #14525
Conversation
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
efd6
added
Integration:aws
efd6
force-pushed
the
14491-aws
branch
2 times, most recently
from
11fe4a5 to
d3967f7
Compare
6 tasks
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
This was referenced Jul 15, 2025
chemamartinez
approved these changes
Jul 16, 2025
The previous code would access .last_response.body.findings and assess its size. However, is the findings field is not present, which is expected in the first part of the chain, the template fails with a map look-up error. Instead, use the index helper to allow us to more gently probe for the presence of the field, only preceeding if it is non-zero. This does not fix the issue, but does allow us to handle it by logic changes in the input.
💚 Build Succeeded
History
cc @efd6 |
|
|
Package aws - 3.13.1 containing this change is available at https://epr.elastic.co/package/aws/3.13.1/ |
5 tasks
kcreddy
added a commit
that referenced
this pull request
Aug 19, 2025
…m for CDR workflows (#14809) Add support for CDR Cloud Native Vulnerability Management (CNVM)[1] workflow by adding necessary mappings and latest transform. Also fixes agent degradation from httpjson's empty cursor happening in log data stream using "ignore_empty_value". Similar to [2]. [1] https://www.elastic.co/guide/en/security/current/vuln-management-overview.html [2] #14525
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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