feat: Add SourceArn
condition to Fargate profile trust policy
#3039
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.
Description
As suggested in AWS docs to prevent the security issue known as the confused deputy problem, adds
SourceArn
condition tofargate-profile
module'sassume_role_policy
Motivation and Context
Fixes #3038.
Suggested IAM trust policy per AWS docs "to avoid a confused deputy security problem."
Breaking Changes
Potentially breaks workflows where users may be using/assuming the IAM role generated by
fargate-profile
in an unintended manner, namely from other EKS instances.How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request