- Newest
- Most votes
- Most comments
Hello,
You have mentioned that you changed the region , hope both ec2 and efs are in same region ap-northeast-2 now. Can you ensure below things ?
- Whether mount targets created for efs and the security group allowing port 2049 from ec2 security group , and vice versa that ec2 allowing port 2049 from efs security group.
- Both ec2 & efs security groups having outbound rules (default 0.0.0.0/0)
- the directory that you are trying to mount exists (example /efs)
- Instead of DNS names of efs (fs-xxxxxxxxxxxxxx.efs.ap-northeast-2.amazonaws.com), try with ip as well.
Hi You can go through this once;
Security groups not allowing access (TCP 2049). Incorrect EFS file system ID in mount command. Missing EFS utilities package (non-Amazon Linux 2). DNS resolution problems on EC2 instance.
Troubleshooting Steps: Verify security group rules for both EFS and EC2. Double-check the EFS file system ID in your mount command. Install amazon-efs-utils if needed. Test DNS resolution from EC2 to EFS DNS name. Try temporary mount with -o no_subtree_check (for diagnostics). Confirm EC2 instance has IAM permissions for EFS access. Review AWS CloudTrail and EC2 logs for errors.
Additional Resources: EFS Mounting Guide: https://docs.aws.amazon.com/efs/latest/ug/mounting-fs.html EFS Mount Helper: https://docs.aws.amazon.com/efs/latest/ug/efs-mount-helper.html
Relevant content
- asked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 6 months ago