AWS guardduty documentation change
Summary
Updated CloudWatch Events references to EventBridge in documentation history
Security assessment
Routine update reflecting service name change from CloudWatch Events to Amazon EventBridge, no security implications
Diff
diff --git a/guardduty/latest/ug/doc-history.md b/guardduty/latest/ug/doc-history.md index 110b15470..f8dedd85a 100644 --- a/guardduty/latest/ug/doc-history.md +++ b/guardduty/latest/ug/doc-history.md @@ -418 +418 @@ For more information about protection plan availability in the Israel (Tel Aviv) -[Added support for updating the frequency of notifications sent to CloudWatch Events](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_findings_cloudwatch.html)| You can now update the frequency of notifications sent to CloudWatch Events for the subsequent occurrences of existing findings. Possible values are 15 minutes, 1 hour, or the default 6 hours. [Learn more](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_findings_cloudwatch.html)| October 9, 2018 +[Added support for updating the frequency of notifications sent to CloudWatch Events](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_findings_eventbridge.html)| You can now update the frequency of notifications sent to CloudWatch Events for the subsequent occurrences of existing findings. Possible values are 15 minutes, 1 hour, or the default 6 hours. [Learn more](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_findings_eventbridge.html)| October 9, 2018