Fix CRLY.01176: Constrain IAM Write Access #43
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-s3.yaml
Remediation Summary
Description
The IAM policy associated with the
PipelineExecutionRole
allows write access without constraints, which is a security risk. This policy should be updated to ensure that write access is constrained appropriately.Steps
Identify the IAM Policy: Locate the IAM policy attached to the
PipelineExecutionRole
in thecfn-deploypipeline-s3.yaml
file.Modify the IAM Policy: Update the IAM policy to constrain write access. Specifically, remove or modify the
Effect: Allow
statement withResource: '*'
to ensure it only allows write access to specific resources.Update the CloudFormation Template: Modify the
cfn-deploypipeline-s3.yaml
file to include the updated IAM policy.Here is an example of how you can update the IAM policy:
In this example, replace
arn:aws:s3:::my-bucket
andarn:aws:lambda:*:*:function:my-function
with the actual resource ARNs that should have access.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.