-
Notifications
You must be signed in to change notification settings - Fork 489
[aws] Add configuration option for TLD for httpjson inputs #8027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…b_findings and securityhub_insights httpjson configs
🌐 Coverage report
|
/test |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed to add this before. Sorry.
Can we add tld
to the system test config [ something other than amazonaws.com as well ] and test this?
Added for the securityhub_findings datastream since that was where the issue was reported |
packages/aws/data_stream/securityhub_findings/_dev/test/system/test-default-config.yml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Package aws - 2.8.0 containing this change is available at https://epr.elastic.co/search?package=aws |
Proposed commit message
[aws] Update
guardduty
,inspector
,securityhub_findings
andsecurityhub_insights
httpjson configs to allow the configuration of the TLD. Default will be set to currently hardcoded value ofamazonaws.com
.Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots
New config option under the Advanced Settings