Private Load-balanced configuration with windows azure

Proposed Private Load-balanced configuration with windows azure

  • Friday, June 22, 2012 8:47 AM
     
     

    Hello,

    I did created two connected Virtual machines.

    A cloud service is now available (with common dns).

    I need to create a private access to this load-balanced configuration. Is it possible ?. DNS looks only created for public purpose.

    My infra require many private load-balanced configurations.

    Does someone have an idea about this ?

    Thanks,

    Gregory

All Replies

  • Monday, June 25, 2012 2:06 AM
    Moderator
     
     

    Hi,

    Load-balance endpoint traffic  for Azure Virtual Machine need 2 or more virtual machine for and the second VM need create connect to the frist one, the you can find load-balance traffic in second VM is available, create steps:

    • Create a virtual machine. You can use Quick Create or From Gallery to create the machine.
    • Add an endpoint to the new virtual machine. You assign a protocol, public port, and private port to the endpoint. The protocols that can be used for an endpoint are TCP and UDP. The TCP protocol also covers HTTP communication.
    • Create another virtual machine using From Gallery and choose to connect the new virtual machine to the virtual machine that you previously created. Virtual machines must be connected together under a cloud service to share a load-balanced endpoint.
    • Create an endpoint on the second virtual machine and choose to make it a load-balanced endpoint by selecting the endpoint that you created on the first virtual machine

    From this article:

    http://msdn.microsoft.com/en-us/library/windowsazure/jj156003.aspx

    Hope this helps.


    Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework


  • Monday, June 25, 2012 9:13 AM
     
     

    Hello,

    I had alrealdy tried this solution. But the entrypoint look public ?!

    I don't want my services to be publish over internet !

    Maybe I missed something ?

    thanks,

    Gregory

  • Wednesday, August 29, 2012 2:21 PM
     
     

    Hi,

    I have the same question, have you ever got an answer for this? I've been searching for a while now and it seems that Azure NLB can only be configured for public ports? All I found is this article: http://msdn.microsoft.com/en-us/magazine/hh148149.aspx but for me this isn't a good solution.

    Thanks, regards. 

  • Wednesday, August 29, 2012 4:59 PM
     
     Proposed

    Hello,

    It is still not supported.

    I guess Azure team is working on it. I really need this feature.

    Gregory

    • Proposed As Answer by Veerendra Kumar Monday, September 03, 2012 10:36 AM
    •  
  • Monday, September 03, 2012 10:36 AM
     
     Proposed

    As of now it is not supported.

    You can post your idea on Azure ideas.

    http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&cad=rja&ved=0CDsQFjAB&url=http%3A%2F%2Fwww.mygreatwindowsazureidea.com%2F&ei=S4hEULqsCcqrrAeicQ&usg=AFQjCNE5Rm-7z6KuBgScYcJHQ0eoz9mBPA



    Please mark the replies as Answered if they help and Vote if you found them helpful.

    • Proposed As Answer by Veerendra Kumar Monday, September 03, 2012 10:36 AM
    •  
  • Monday, September 03, 2012 1:29 PM
     
     

    So, if I understand correctly, every application running on Azure which is using NLB has publicly opened ports on their servers?

    Do you have any suggestions on how to ensure load ballancing on application servers that shouldn't have any public ports?

    Thanks,

    kind regards.

  • Monday, September 03, 2012 4:37 PM
     
     Proposed

    As per my knowledge there is no way as it works only on public DNS name. If you want to implement the restrictions, you can restrict IPs in your service config to restrict your application layer to allow only specific IPs. For example if you want to allow only web layer to talk to your application layer, you can simply restrict only web role IPs to access application layer.



    Please mark the replies as Answered if they help and Vote if you found them helpful.

    • Proposed As Answer by MARG Live Tuesday, September 04, 2012 8:01 AM
    •