简体繁体 English

私有Azure云服务？

[英]Private Azure Cloud Service?

原文 2015-05-27 11:03:01 1 1 c#/ asp.net/ wcf/ azure

In a microservice architecture it's quite common to have tens of "internal" services, ie those services that are only intended to be called by other services in the architecture and not publicly accessible. 在微服务架构中，拥有数十个“内部”服务是很普遍的，即那些只打算由架构中的其他服务调用并且不能公开访问的服务。

We're very happy with Azure Cloud Services (web and worker roles) and all the nice PAAS deployment benefits they bring. 我们对Azure云服务（Web和工作角色）以及它们带来的所有不错的PAAS部署好处感到非常满意。 We'd like to develop several internal microservices as Azure Cloud Services but at the same time avoid having to add custom application security code to them (OAuth etc.) by ensuring they can only be accessed by other machines in the same Azure Virtual Network. 我们想开发一些内部微服务作为Azure云服务，但同时避免通过向它们添加自定义应用程序安全代码（OAuth等），以确保它们只能被同一Azure虚拟网络中的其他计算机访问。

What are the options for achieving this? 有哪些选择可以实现这一目标？ Is there anyway to stop an Azure Cloud Service being assigned a Public VIP Address / Site URL (*.cloudapp.net)? 无论如何，有没有要停止向Azure云服务分配公共VIP地址/站点URL（* .cloudapp.net）？

One option we're aware of is using the IIS ipSecurity element to lock down the services to a defined range of internal IP addresses but wondering if there are any better alternatives? 我们知道的一种选择是使用IIS ipSecurity元素将服务锁定到内部IP地址的已定义范围，但是想知道是否还有更好的选择？

1 个解决方案

Look into Internal Endpoints. 查看内部端点。 They allow your services to communicate internally without going thru public internet and thus allow you to not have any public endpoints 它们使您的服务无需通过公共互联网就可以在内部进行通信，从而使您没有任何公共端点

https://msdn.microsoft.com/en-us/library/azure/hh180158.aspx https://msdn.microsoft.com/en-us/library/azure/hh180158.aspx

HTH HTH