ResourceInitializationError: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-file-system-id.efs.us-west-1.amazonaws.com" - check that your file system ID is
0
We are mounting EFS volume to our task and we are running the task on fargate but it giving above mentioned error. we made sure everything running the Fargate task and EFS is in the same VPC, using the same sub net and availability zone. We also opened port 2049 for NFS. We also tried opening all traffic for all ports and attached to the task but still we are facing the same issue.
asked 2 months ago14 views
1 Answers
0
Can you please verify the debugging methods mentioned by AWS support, i think this will help you
answered 2 months ago
Relevant questions
ResourceInitializationError: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-file-system-id.efs.us-west-1.amazonaws.com" - check that your file system ID is
asked 2 months agoAWS Directory Service unable to resolve EFS dns name
Accepted Answerasked 3 years agoSend efs backup to S3
Accepted Answerasked 5 months agofailed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com"
Accepted Answerasked 4 months agoFargate EFS Issue: ResourceInitializationError: failed to invoke EFS utils
asked 2 years agoTransitioning from EFS-to-EFS backup solution to AWS Backup service
asked 3 years agoIs it possible to make EFS publicly accessible?
asked 4 months agoDocker: Elastic Beanstalk with EFS filesystem
asked a month agoHow to Mount an EFS in WSL2
asked a year agoWhat is the total number of EFS volumes that can be created in a VPC?
asked 3 months ago
We referred and checked the debugging methods provided by AWS for the error. All the configurations looks okay and we are still facing the same error.
We tried creating the entire pipeline in different VPC and it worked. But when we try in the VPC we tried earlier, it is still giving an error.