- the instances have the correct IAM role applied
- mounting is via the access points
- TLS is enforced
Code: Select all
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::012345678901:role/ec2-efs-instance-role"
},
"Action": [
"elasticfilesystem:ClientWrite",
"elasticfilesystem:ClientRootAccess",
"elasticfilesystem:ClientMount"
],
"Resource": "arn:aws:elasticfilesystem:<region>:012345678901:file-system/fs-0123456789abcdefg",
"Condition": {
"Bool": {
"elasticfilesystem:AccessedViaMountTarget": "true",
"aws:SecureTransport": "true"
}
}
}
]
}
When using VBA to back up the EFS with Indexing turned on, it appears the instance that VBA launches to mount the share to perform indexing only uses the built in mount.nfs to mount the share, which won't work with the above file system policy applied:
Code: Select all
Processing efs-backup-policy failed: Failed to mount file system: Async command 44a321a1-8334-4a5b-8432-f0b73bc9852f failed with code 32: mount.nfs4: access denied by server while mounting 10.0.0.111:/
https://docs.aws.amazon.com/efs/latest/ ... elper.html
https://docs.aws.amazon.com/efs/latest/ ... ption.html
https://docs.aws.amazon.com/efs/latest/ ... oints.html