search

aws-samples / aws-refarch-wordpress

This reference architecture provides best practices and a set of YAML CloudFormation templates for deploying WordPress on AWS.
MIT No Attribution
1.08k stars 601 forks source link

CANNOT Clone EFS, use the System ID of an existing EFS Filesystem #44

Closed michael-newman closed 6 years ago

michael-newman commented 6 years ago

@darrylsosborne

Not withstanding issue #42, I am using the templates individually, and am having issues with the EFS template not enabling the mount to my existing EFS to then facilitate the copy to the new template EFS.

My existing EFS is in the AWS Std. VPC 172.31.x.x/16, the RefArch templates use a new VPC 10.1.x.x/16. We have successfully worked with AWS technicians to understand & resolve:

This line in the template is failing as the the DNS Name cannot be resolved: sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 $COPY_SYSTEM_ID.efs.$region.amazonaws.com:/ /$COPY_SYSTEM_ID and we have been informed by AWS Engineers, that AWS does not support this DNS Resolution across VPC Peering connections. We can only manually mount across the VPC peering connection if we use an IP address.

Would welcome your assistance, thoughts, or any suggested workarounds...

Thank you, Mike

michael-newman commented 6 years ago

Until such time that the DNS Name can be resolved across a VPC Peering connection, it appears editing the template to hardcode an IP Address for the source EFS mount point is the workaround.

Regards, Mike