2 Answers
- Newest
- Most votes
- Most comments
1
See following blog post: https://aws.amazon.com/blogs/containers/developers-guide-to-using-amazon-efs-with-amazon-ecs-and-aws-fargate-part-2/ The trick is, to enable IAM authorization for the ECS volume integration.
When this is enabled, the ECS cluster can be identified by the EFS volume and you can define the EFS task role as principal in the EFS file system policy.
answered a year ago
0
Can you try, for number 1. https://docs.amazonaws.cn/en_us/efs/latest/ug/access-control-overview.html
"elasticfilesystem:CreateFileSystem",
"elasticfilesystem:CreateMountTarget"
On number 2, try this: https://aws.amazon.com/premiumsupport/knowledge-center/troubleshoot-iam-permission-errors/
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 3 months ago
I added "elasticfilesystem:CreateMountTarget" to the EFS policy OK, but adding "elasticfilesystem:CreateFileSystem" generates "Invalid policy" error in the File System Policy tab. Both of those links are quite broad. For instance "Mounting with IAM authorization", in your second link, demos how to specify an IAM role using sudo at the command line. That might help for debugging, but I'm not clear how to limit access by IAM role instead of just "AWS": "*"