I came across this question: You have decided to use EFS for sharing files across many EC2 instances and you want to be able to tolerate an AZ failure. You should:
Answer I choose{
Create EFS mount targets in each AZ and configure each EC2 instance to mount its local AZ mount target FQDN
}
Results show the above answer is wrong
Sorry!
As of December 2016, the common mount target name of an EFS file system will resolve to its local mount target in each AZ. So, you only need to create mount targets in each AZ within the same subnet as the EC2 instances then use the common FQDN. Further information: https://docs.aws.amazon.com/efs/latest/ug/accessing-fs.html
I am not sure if this statement is valid"you only need to create mount targets in each AZ within the same subnet as the EC2 instances then use the common FQDN."
I believe EC2 instances can access the Mount targets in different subnets within the same AZ, Also the question doesn’t mention anything about subnet ..so the answer I chose seems more appropriate, Please share your opinion, I may be missing something here, looking for some inputs.
2 Answers
WWhat are the other options in answers?
I read the documentation, and mainly see that EC2 mount the EFS using the file system DNS name
Is this one of the options??
Hi sk,
The correct answer is to use the common FQDN to mount the EFS targets. This will automatically resolve to the local EFS mount-point depending on which AZ the EC2 instance is in. You should not use the local mount target name. I encourage you to go create an EFS instance and configure it for multiple AZs. You’ll see right on the console that it instructs you to use the common FQDN in your FSTAB entries.
–Scott
they mentioned this is the correct answer" Create EFS mount targets in each AZ and configure each EC2 instance to mount the common mount target FQDN"
all the options available " Create EFS mount targets in each AZ and configure each EC2 instance to mount its local AZ mount target FQDN" – "Configure EFS File Sync agent on the EC2 instances"-"Create EFS shares in each AZ and configure each EC2 instance to mount the share in its local AZ via the FQDN"-"Do nothing as EFS is already multi-AZ"