Add aws Config permissions to the Federated Identity template - #7589
Draft
seanrathier wants to merge 1 commit into
Draft
Add aws Config permissions to the Federated Identity template#7589seanrathier wants to merge 1 commit into
seanrathier wants to merge 1 commit into
Conversation
3 tasks
Mirror the AWS Config permission set from the patch files in elastic/integrations#20240 into the incremental Federated Identity template: config:DescribeConfigRules and config:GetComplianceDetailsByConfigRule, the two operations the Config data stream's CEL program calls (elastic/integrations#20437). config:DescribeComplianceByConfigRule from the #20240 patch set is deliberately omitted — the program never calls it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
seanrathier
force-pushed
the
seanrathier/federated-identity-aws-config
branch
from
July 31, 2026 20:47
833983d to
ec24a13
Compare
seanrathier
changed the base branch from
seanrathier/federated-identity-aws-securityhub
to
seanrathier/federated-identity-aws-cft
July 31, 2026 20:47
3 tasks
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
Adds the
ElasticAwsConfiginline policy to the incremental Federated Identity template:config:DescribeConfigRulesconfig:GetComplianceDetailsByConfigRuleThese are the two operations the AWS Config data stream's CEL program calls, paired with elastic/integrations#20437 (the Config
auth.awsmigration + ungate). Both IAM actions map 1:1 to their API operation names.Deliberate omission: the permission patch sets in elastic/integrations#20240 also list
config:DescribeComplianceByConfigRule— the program never calls it, so it is left out (least privilege; likely stale in #20240 since the service-linked-rules fix reshaped the collection flow).Background
Part of https://github.com/elastic/ingest-dev/issues/8802.
Stacked on #7422 (the incremental baseline); retargets to
mainautomatically when it merges. One CFT PR per federated integration, each paired with the elastic/integrations PR that defines the stream's actual API surface.Sibling PRs on the same baseline: #7422 (GuardDuty baseline) is the base; #7588 (aws_securityhub) and #7590 (Amazon Inspector) are the sibling per-integration additions. Whichever merges second rebases over a trivial same-region conflict.
Test plan
cfn-lintandrainpass in pre-commitElasticAwsConfigDescribeConfigRules+GetComplianceDetailsByConfigRuleto confirm both authorize🤖 Generated with Claude Code