[BugFix] Explicitly set the policy for ECR private repo so prevent policy removal on stack update impacting Lambda function #373
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
Explicitly set the policy for ECR private repo so prevent policy removal on stack update impacting Lambda function.
The minimum set of permissions required by Lambda to fetch the code from the repository is:
ecr:BatchGetImage
ecr:GetDownloadUrlForLayer
However, Lambda sets the policy with the below extra permissions when the policy is not set m(current behavhoir on stack create):
ecr:DeleteRepositoryPolicy
ecr:GetRepositoryPolicy
ecr:SetRepositoryPolicy
So we decided to go with the permissions currently set by Lambda to prevent impacts.
We will restrict the permissions once Lambda will confirm that they are enough.
How Has This Been Tested?
Deployed in personal account and verified that:
References
PR Quality Checklist
react-i18next
library (useTranslation hook and/or Trans component), see an example herenpm run build
builds without any errorIn order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.