(enhancement): Frequency for updated findings for GuardDuty #1057
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
Brian969
changed the title
Brian969
changed the title
dliggat
approved these changes
Oct 3, 2022
Contributor
dliggat
left a comment
dliggat
left a comment
There was a problem hiding this comment.
LGTM @rjjaegeraws. Tested adding and removing guardduty-frequency - setting updated as expected.
Brian969
added a commit
that referenced
this pull request
Oct 4, 2022
* add frequency for GuardDuty * update sample config files with new config option * add guardduty eks support * fix for issue with ALB forwarder when no HOSTS defined (#1019) * Decreasing max concurrency limit to 10 (#1062) * (Fix): SM jitter (#1050) * exponential backoff fix * exponential backoff fix * Fixed backoff for lambdas * added backoff in other location * fixed lambda timeouts and added timeout aspect * fixed typo * tweak default max jitter delay to 2s from 5s Co-authored-by: hickeydh-aws <hickeydh@amazon.com> Co-authored-by: Brian969 <56414362+Brian969@users.noreply.github.com> * (docs): Eb faq doc update (#1055) * added Elastic Beanstalk entry to FAQ * Update index.md Co-authored-by: Jahnke <ejahnke@909c4acec9cf.ant.amazon.com> * (addon): OpenSearch SIEM added CW Alarms (#1056) * added CW Alarms * fix typo Co-authored-by: Brian969 <56414362+Brian969@users.noreply.github.com> * (enhancement): Frequency for updated findings for GuardDuty (#1057) * add frequency for GuardDuty * update sample config files with new config option * add guardduty eks support Co-authored-by: rycerrat <42330513+rycerrat@users.noreply.github.com> Co-authored-by: hickeydh-aws <88673813+hickeydh-aws@users.noreply.github.com> Co-authored-by: hickeydh-aws <hickeydh@amazon.com> Co-authored-by: Brian969 <56414362+Brian969@users.noreply.github.com> Co-authored-by: Elden Jahnke <94935251+ejahnke@users.noreply.github.com> Co-authored-by: Jahnke <ejahnke@909c4acec9cf.ant.amazon.com>
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.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
This pull requests implements a new configuration value
"guardduty-frequency"with the following possible values:FIFTEEN_MINUTES, ONE_HOUR, SIX_HOURSBy default, the Frequency for updated findings for GuardDuty is set at the default, SIX_HOURS.
Here's an example of the result with the following config: