[Docs update] Add support for fs-check parameter to AWS Backup integration lambda #90
Conversation
This file contains 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
Veetaha
changed the title
volatilecat
approved these changes
Jul 12, 2024
anelson
approved these changes
Jul 15, 2024
|
Merging since 0.31 was released |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates our public documentation for AWS Backup integration lambda. It should be merged once we release support for fs-checks in scan-only and in AWS Backup integration lambda in 0.31
The new option is a boolean that is adjacent to iscan. The request needs to look like this:
{ "fs_check": true, "iscan": { "malware": true, "ransomware": true, "event_bridge_bus": "MyBusName" } }