fix(stepfunctions-tasks): fix the generated IAM policy for EFS operations#30896
Conversation
aws-cdk-automation
left a comment
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
d274c9e to
f8506e1
Compare
f8506e1 to
8715bb9
Compare
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #30862.
Reason for this change
Per TagResource, the operation requires permissions for the
elasticfilesystem:TagResourceaction. Also per AWS managed policies for Amazon EFS, all theAction(s) are prefixed withelasticfilesystem:(notefs).Description of changes
Updates the
iamServiceMapthat maintains list of services having mapping to IAM policy prefix names.Description of how you validated changes
Added unit test and integration test (along with snapshot).
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license