Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a number of servers which all need external IP addresses, as they provide different services and need to be invidually accessible: > > >
... > n.n.n.n

Shared among these servers is a NFS share on a server called files.mydomain.

Basically, I want to have my public servers be able to privately access files.mydomain over an intranet (secure) rather than over the internet (totally not secure). How can I do this? All servers need to be publicly accessible to SSH and other services, but NFS specifically needs to be done over a local network within the Amazon cloud privately. I was thinking of using a VPC, but I'm not sure how to make this happen to keep the servers externally accessible while still keeping internal networking available between them.

share|improve this question
up vote 2 down vote accepted

You absolutely should use a VPC for this. All of your instances will get a private IP inside the VPC, and then for those that need public IP addresses, either associate an EIP with them or set up port forwarding from a NAT instance.

With regards to NFS traffic, create a Security Group that allows traffic on NFS ports from group members, and add that group to each of your instances.

share|improve this answer
Do I need multiple subnets, or can all this be managed in a single subnet? – Naftuli Tzvi Kay Apr 11 '13 at 0:31
You don't need multiple subnets for this. – EEAA Apr 11 '13 at 0:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.