check that your file system ID is correct, and ensure that the VPC has an EFS mount target for this file system ID about cloud-is-free HOT 2 CLOSED

In view of the error message, and after analyzing the screenshots, I am sure that the problem is due to the fact that DNS hostnames have not been activated on the VPC when created.

To fix this problem, follow the steps on the screens below:

https://imgur.com/a/vxs7bv

By doing this:

• The EC2 instance will have a public hostname (convenient but not important);
• the EFS volume will have a public hostname (PRIMORDIAL to link the EFS volume to ECS containers).

And by the way, be sure that the EFS volume is linked to the correct VPC and AZ! If you followed the step 7 correctly, this should have been done.

Please let me know if this fixed the problem.
Good luck with the rest of the project!

from cloud-is-free.

It looks like I had a few things wrong but you've pointed me in the right direction. As you guessed the DNS hostnames were disabled. I was also building the EFS in ap-northeast-1a when my EC2 Instance was in 1a. It's still failing but now I know where to look. Thanks for the help! This has given me some great insight into how AWS works.

from cloud-is-free.