Developer access to data
Authorize the approved team to reach the database endpoint and port without opening other services on the database host.
Declare the protocol, host and port of a private database, API or administration service. For cross-account sharing, a narrower L4 Service Grant gives selected users, groups, or source Nodes the exact path without granting the whole Node.
Keep the resource where it already runs. Give each audience only the declared service that matches its work.
Authorize the approved team to reach the database endpoint and port without opening other services on the database host.
Expose an internal API inside the selected Space while its surrounding environment remains out of scope.
Let operators reach a private management interface without publishing it to the public internet.
Describe the service in the protocol terms it already uses instead of redesigning the application around a generic tunnel.
Directional Grants shape cross-account sharing. Same-account members retain system access to their own Nodes and private Services.
The Service definition names the endpoint the user can actually consume.
Cross-account sharing can select users, groups, or source Nodes for that Service path.
Node access is a different, broader choice and is never implied by a Service Grant.
The App shows Services authorized to the currently selected Organization and Network Space.
Define the private Service in NSD, then let approved users consume it from the App.
资源继续运行在原来的位置,只为每类使用者提供与工作匹配的已声明服务。
授权获批团队访问数据库端点和端口,而不开放数据库主机上的其他服务。
在当前空间内提供内部 API,同时让它周围的环境继续处于授权范围之外。
让操作人员访问私有管理界面,而无需把它发布到公网。
按照服务已经使用的协议描述它,不必为了通用隧道重新设计应用。
方向明确的授权用于跨账号共享;同账号成员仍可使用自己的节点和私有服务。
服务定义准确说明用户真正可以使用的端点。
跨账号共享可以为该服务路径选择用户、用户组或来源节点。
节点访问是范围更广的另一种选择,服务授权永远不会隐含节点访问。
App 展示当前所选组织和网络空间授权的服务。