fix(aws.config): handle empty DescribeConfigRules responses#14958
Merged
andrewkroh merged 5 commits intoelastic:mainfrom Aug 19, 2025
Merged
fix(aws.config): handle empty DescribeConfigRules responses#14958andrewkroh merged 5 commits intoelastic:mainfrom
andrewkroh merged 5 commits intoelastic:mainfrom
Conversation
Handle responses from DescribeConfigRules that contain an empty list (e.g. `ConfigRules: []`).
The comments help me navigate the program more effectively.
The error.message values indicated a request URL path that is different than the actual requested URL. So modify the format of the error message to be accurate while also indicating what API call was being performed.
[git-generate] elastic-package -C packages/aws changelog add --description "Fixed issue where empty DescribeConfigRules responses caused 'index out of bounds' errors in AWS Config integration." --type bugfix --next patch --link "elastic#14958"
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
andrewkroh
commented
Aug 19, 2025
efd6
approved these changes
Aug 19, 2025
|
💚 Build Succeeded
History
|
|
Package aws - 3.14.1 containing this change is available at https://epr.elastic.co/package/aws/3.14.1/ |
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
…14958) This change addresses issues discovered during testing of the AWS Config integration CEL program. The program was failing to handle empty ConfigRules responses properly, which could occur when AWS Config has no rules configured in a region. The failures resulted in 'index out of bounds: 0' errors. The fix ensures that empty ConfigRules lists are handled gracefully without causing program failures. The error.message values now accurately reflect the URL path and include the specific AWS Config API call being made (DescribeConfigRules vs GetComplianceDetailsByConfigRule). State management has been improved to consistently preserve the URL value across all execution paths, preventing debug warnings about missing state values. Comments have been added to explain the different stages of the CEL program. Closes elastic#14955
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
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.Related issues