fix(vm-workload-scanning): Fixing CFT for Managament Account for Workload Scanning [SSPROD-52797] #142
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
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.
https://sysdigcloud.slack.com/archives/CMCPMSQ8Y/p1738853886784009
Hi team, Covantis POV here. We onboarded AWS org via CFT CSPM+CDR/CIEM+WorkloadScanning
I think the CFT template we use for WorkloadScanning does not create the required role sysdig-vm-workload-scanning-xxxxx in the management account (1st screenshot). I was able to replicate that in our lab aws org, I don't see the role in the list of resources created by the stack (2nd screenshot), just the stackset that will be used for sub-accounts.
Can you please check? [cc
@Stefan Trimborn
] (edited)