You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In AWS we have seen an user trying to mount EFS as part of deploying appsmith getting the following error:
ResourceInitializationError: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-01bd17a53b98b8014.efs.eu-west-1.amazonaws.com" - check that your file system ID is correct, and ensure that the VPC has an EFS mount target for this file system ID. See https://docs.aws.amazon.com/console/efs/mount-dns-name for more detail. Attempting to lookup mount target ip address using botocore. Failed to import necessary dependency botocore, please install botocore first. : unsuccessful EFS utils command execution; code: 1
The root cause :
In aws ecs. Users can mount EFS only via the DNS and not via IP and the user had DNS resolution disabled in the VPN.
Use Cases / User query reference
To avoid this confusion. It will be good if we add a statement under
Before you Begin section
like follows Please make sure dns-resolution is enabled in your VPC
Problem Statement
In AWS we have seen an user trying to mount EFS as part of deploying appsmith getting the following error:
The root cause :
In aws ecs. Users can mount EFS only via the DNS and not via IP and the user had DNS resolution disabled in the VPN.
Use Cases / User query reference
To avoid this confusion. It will be good if we add a statement under
Before you Begin section
like follows
Please make sure dns-resolution is enabled in your VPC
Audio/Video Recording
https://theappsmith.slack.com/archives/C0341RERY4R/p1713268898369059?thread_ts=1712767965.097279&cid=C0341RERY4R
Product Requirements Document
No response
Other Relevant Links
No response
Checklist
The text was updated successfully, but these errors were encountered: