Repository navigation
Correct regional ECS task-definition inspection permission - #58
Merged
Merged
Conversation
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.
The first hosted production qualification created the inactive AWS stack, then CloudTrail recorded AccessDenied for ecs:DescribeTaskDefinition. AWS authorizes that read API against Resource "*" rather than task-definition ARNs.
Use the supported resource scope for this single read action and restrict it to the deployment region. Preserve production OIDC trust, all other IAM statements, and rollout checks that bind the returned task definition to the exact account and candidate. No database secret-value access is added.
Validation: seven targeted deployment IAM checks and diff checks pass. Exact0293080 CI37559019609 and CodeQL37559019618 passed, including application bundles, actual Docker/PostgreSQL smoke and infrastructure checks. The reviewed AWS change set modified only the existing inline IAM policy without replacement; live policy matches source and simulation allows us-east-1 while denying us-west-2. The current application stack is CREATE_COMPLETE with actual ECS desired/running/pending capacity zero; migration proof remains pending.