Overview
Identity (also known as a workload identity) is one of the four Control Plane principal types (users, service accounts, groups, and identities). A workload needing to consume cloud resources from one or more cloud providers (e.g., AWS, Azure, and GCP) without storing credentials or needing to communicate to endpoints within a private network - must be assigned an identity. An identity is a named object that allows an authorized administrator to define:Cloud Provider Access (Universal Cloud Identity)
- Least-privilege access rules allowed on cloud resources across cloud providers. Each identity can reference only one cloud account per provider. For example, you can have one account in Azure and one account in GCP, but not two different accounts in GCP within the same identity. You define access policies granted to the identity for each cloud provider you need to use (one, two, or all three clouds, depending on your workload requirements).
Private Network Access (Cloud Wormhole)
- Network traversal rules from workloads into specific endpoints in private networks (e.g., a VPC). These rules connect an agent in a private network to the Control Plane infrastructure, allowing workloads to selectively access TCP endpoints inside private networks where agents are installed and running.
Native Cloud Network Access
- Provides secure, private connectivity from a workload to cloud-hosted services across AWS (vpc endpoints) and GCP (private service connect) without traversing the public internet. It leverages cloud provider-specific private networking services to route traffic over internal infrastructure. This enables low-latency, secure communication to private resources while maintaining strict network isolation and identity-based access control.
- Access specific resources of AWS, Azure, and/or GCP
- Access private network resources from external cloud accounts, data centers or any other private network. (Tunneling network traffic from workloads to specific TCP hosts and ports is facilitated using agents. This capability is referred to as “wormholes”.)
- Access the NATS NGS service using scoped credentials automatically supplied at runtime
Create an Identity
Refer to the Create an Identity guide for additional details.Identity Specification
An identity can be configured with the following fields:Cloud Provider Access
AWS Identity (aws)
*Either
roleName OR policyRefs is required, but not both.
Trust Policy Structure:
GCP Identity (gcp)
*Either
serviceAccount OR bindings is required, but not both.
Binding Structure:
Azure Identity (azure)
Role Assignment Structure:
NATS Identity (ngs)
Permission Structure:
Private Network Access
Network Resources (networkResources)
*Either
IPs OR FQDN is required.
All agents referenced in an identity must be the same protocol version (v1 or v2).
Native Network Resources (nativeNetworkResources)
*Either
awsPrivateLink OR gcpServiceConnect is required.
AWS PrivateLink Structure:
Status
Provider Status Structure: