Fix CRLY.01176: Constrain IAM Write Access #47
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.
Issue Details
ID: CRLY.01176
Severity: HIGH
File: pipeline/cfn-deploypipeline-github.yaml
Remediation Summary
Description
The IAM policy associated with the
PipelineExecutionRoleallows unrestricted write access, which is a security risk. This policy should be updated to constrain write access to only necessary resources.Steps
Identify the IAM Policy: Locate the
PolicyDocumentwithin thePoliciessection of thePipelineExecutionRole.Update the Policy: Modify the
PolicyDocumentto restrict write actions to specific resources. Below is an example of how you can update the policy to restrictiam:PassRoleandlambda:InvokeFunctionactions to specific resources.By following these steps, you will ensure that the IAM policy does not allow write access without constraints, thereby improving the security of your AWS environment.