failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com"

Question

Hi,

I'm following the APPLICATION MODERNIZATION WITH AWS AND DOCKER workshop steps as mentioned and in module 2, Step 1 -  Section: ***Deploy to Amazon ECS***, really got stuck when deploying application to AWS ECS.

When I execute the "*docker compose up*" command as mentioned, it starts deploying resources and The Docker Compose CLI first concatenates the compose files passed through and generates an opinionated AWS CloudFormation template and deploys it to create the AWS resources defined in our compose file.

After few mins , its shows in cloudformation "DELETE_IN_PROGRESS" and when all the resources get decommissioned it throws an error message saying

"*DbService TaskFailedToStart: ResourceInitializationError: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve '*fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com*' - check that your file system ID is correct.*"

When I checked in the EFS console, the EFS was created successfully. Not sure why is this causing an issue?

**GitHub Repo:**
https://github.com/spawar1991/docker-compose-ecs-sample

-------------------------------------------------------------------------

Workshop URL: https://docker.awsworkshop.io/31_docker_ecs_integration/10_migrate_to_ecs.html

Can someone know how to mitigate this error and why is it causing an issue?

Thanks in advance.

Accepted Answer

It finally worked. I was going through the workshop instructions again to check if I have missed anything. So, They have specifically mentioned in the instructions to use *default VPC* for the workshop.

***This is the note they have mentioned:***

**All the resources were deployed to the *Default VPC *for this lab. In real life scenario, you can deploy to your own VPC and subnets using x-aws-vpc extension (commented in docker-compose.prod.migrate.yaml).**

I had used my custom VPC using "*x-aws-vpc*" parameter in *docker-compose.prod.migrate.yaml* file and due to that, it was creating an issue when creating AWS resources.

In the cloud9 terminal logs, I'm able to see that all services has been successfully created and also verified in cloudformation "*Resources*" section.

Thank you Madhav_P for your input. Appreciate it.

Answer

Though I haven't tried this, what I would do is to set the rollback option for cloudformation script to 'no' so that it remains in the same state when a failure occurs rather than rolling back and deleting the cloud components it created so far. That way one would be able to debug better.

failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com"

관련 콘텐츠