Repository navigation
fix(Onboarding): Change lambda function for workload scanning modules SSPROD-69028 - #111
Merged
Merged
Conversation
ndsistsys
approved these changes
Jun 15, 2026
ivanbesinovic-sysdig
approved these changes
Jun 24, 2026
Contributor
|
Hi @raghavanandan LGTM. Just Ankit to approve testing |
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
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.
Jira
https://sysdig.atlassian.net/browse/SSPROD-69028
Summary
Replaces the
lambda:ListTagsForResourceIAM action withlambda:ListTagsin the vm-workload-scanning module.Changes
modules/vm-workload-scanning/main.tf— updated the functions IAM policy document (single-account install / management account in org installs).modules/vm-workload-scanning/organizational.tf— updated the CloudFormation StackSet policy template (member accounts in org installs).Both files were changed together to keep the single-account and organizational deployment paths consistent, since the policy in main.tf is gated only by lambda_scanning_enabled and runs in both modes.
Notes
logs:ListTagsForResourceaction in the response-actions module was intentionally left untouched (different AWS service).