Home > Software design >  Network interface of AWS EFS fails to be associated with a static IP
Network interface of AWS EFS fails to be associated with a static IP

Time:12-06

My issue is basically what is said in AWS EC2 admin console showing the error

I don't think that I "do not have permission" because I'm the owner of the account and I have the AdministratorAccess IAM policy.

Is there a way to make EFS publicly accessible or mount it in any other way on my own machine?

CodePudding user response:

Therefore, I want to assign a static Elastic IP to the network interface of EFS, so I can access it publicly, but I get the following error:

That's not a supported configuration on AWS. You can't assign a public IP to EFS. You need to look into SSH tunneling, or a VPN connection into the VPC, in order to mount an EFS volume from outside the VPC.

My guess is that AWS doesn't allow me to make EFS publicly available because that might make their AWS Transfer Family product obsolete, since it seems to solve the same problem - using EFS outside the cloud.

That's a very cynical take on things. In actuality Amazon simply designed EFS to be a service that complemented their compute services (EC2, ECS, EKS, Fargate, and Lambda). They did not design it to be a global, public NFS mountable file system.

  • Related