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:
VPC Peering, route tables, 'DNS resolution', validated NACLs, etc.
EFS data load instance C5 (or M5) required by EFS to mount within VPC Peering connection
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...
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.
@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