Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm interested in knowing best practices for securing communications between a Linux VM and a Windows VM/Web Role.

So in the end, i need to communicate securely like so--

Linux VM < -- > Windows Web Role

I know that you can create public IPs for VMs, but i'm not sure i want to allow that-- is that opening up too much?

Specifically I am planning on hosting Redis/Elasticsearch on these VMs, if that helps at all.


share|improve this question

closed as not a real question by Michael Hampton, mgorven, Greg Askew, Scott Pack, mdpc Feb 4 '13 at 20:00

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

What are you securing, and from what? – Michael Hampton Feb 4 '13 at 19:20
Communication between a .NET program and a Linux VM running Redis. Can you guys give me a chance to respond before closing this out? If i knew everything about this i wouldn't need the help, you know? – Micah Feb 4 '13 at 20:15
@MichaelHampton come on-- – Micah Feb 4 '13 at 20:39

I don't know a lot about Azure networks, but you could look at Azure VPN. For us, we build our services on Amazon EC2, and we have firewall rules set to make sure only some of our machines can see others. The Azure firewall can allow that also (your Reddis/elasticsearch box should be locked down to only your internal boxes).

share|improve this answer

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