5
votes
Accepted
Startup of ECS Fargate task fails with ResourceInitializationError mount.nfs4 Connection timed out
Underlying reason:
The ECS service's network access security group did not have permission to access EFS.
Solution:
Add an inbound rule for type NFS in the security group as described in this ...
4
votes
Accepted
In what way does a new ECS Fargate service not satisfy the task definition's required capabilities?
This is by design because AWS have yet to upgrade LATEST to point to v1.4.0 (as per 2020-06-23, see AWS ECS Developer Guide). Set the service platform version explicitly to 1.4.0 (instead of LATEST).
3
votes
Is it possible to ask AWS-EFS to automatically remove those files that never been read in a period of time?
You can't do this natively in AWS EFS. You can move it to cheaper storage natively in EFS by setting up Lifecycle Management to move the files last accessed X days ago to Infrequently Accessed (IA) ...
1
vote
In what way does a new ECS Fargate service not satisfy the task definition's required capabilities?
It doesn't tell the exact error message, however in my case,
I was using firelens log driver with S3 configuration type. Since Fargate only supports local file at this point, I got the same error ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
amazon-efs × 6terraform × 3
amazon-web-services × 2
amazon-ecs × 2
fargate × 2
amazon-ec2 × 1
aws-lambda × 1
aws-cli × 1