Add entropy scan support and remove requirement for elastio:resource tag on aws-backup-restored resource
#83
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
…` tag on aws-backup-restored resource
volatilecat
approved these changes
Apr 26, 2024
anelson
approved these changes
Apr 26, 2024
mvovchuk
approved these changes
Apr 26, 2024
Veetaha
deleted the
feat/entropy-support-in-aws-backup-integration-and-iim-update
branch
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.
Exposed entropy detection in AWS Backup integration API.
@Silverhorn27 implemented IAM roles for Elastio Connector such that our BG job can directly tag the restored EC2 instance and volumes with
elastio:resourceif that EC2/EBS hasawsbackup-restore-testtag on it (which we consider a temporary resource that we can mutate).