Merged
Conversation
Covers CLI flags (--targets, --role, --org), architecture for parallel cross-account scanning via STS AssumeRole, output changes with per-target sub-summaries, and IAM role setup docs (Terraform + CloudFormation).
Add ResolveTargets function that resolves scan targets based on --targets, --org, --role, and --skip-self options. Self account uses original credentials (no AssumeRole), failed assumptions are collected as TargetError rather than being fatal. Add STSClient and OrgClient interfaces, Target and TargetError types, multi-target fields to ScanOptions, and organizations SDK dependency. Includes 6 tests covering: self-only, explicit targets, skip-self, partial failure, org discovery with suspended account filtering, and self-in-targets deduplication.
ResolveTargets now returns selfAccount separately so Scan() always gets the correct caller identity regardless of --skip-self. Extracted models.MaxSeverity to replace three copies of severity classification. Removed dead error return from scanTarget. Added missing copyright headers.
maksimov
added a commit
that referenced
this pull request
Apr 21, 2026
Add multi-account AWS scanning
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
1 participant
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.
Summary
Scan multiple AWS accounts in a single invocation via STS AssumeRole or automatic discovery via AWS Organizations.
--targets,--role,--external-id,--org,--skip-selfResolveTargets()handles credential resolution with self-detection, org discovery, and partial failure tolerancegpuaudit iam-policynow includes cross-account and Organizations policy statementsKey design decisions
--targetsnot--accounts) for future GCP/Azure supportomitemptyon new JSON fields ensures backward-compatible output for single-account scansmodels.MaxSeverity()Changes
internal/providers/aws/multiaccount.go— ResolveTargets, AssumeRole, org account listinginternal/providers/aws/multiaccount_test.go— 6 tests covering all targeting modesinternal/providers/aws/summary.go— BuildSummary (extracted) + BuildTargetSummariesinternal/providers/aws/summary_test.go— 3 testsinternal/providers/aws/scanner.go— Refactored Scan() for parallel multi-target scanninginternal/models/models.go— TargetSummary, TargetErrorInfo, MaxSeverityinternal/output/table.go— Per-target summary table, conditional target columninternal/output/markdown.go— Per-target markdown sectioninternal/output/slack.go— Per-target Slack blockscmd/gpuaudit/main.go— New flags, validation, IAM policy updatesTest plan
go test ./...)go vetclean--targetsand--role--org🤖 Generated with Claude Code