OpenID Connect Integration for Pulumi Deployments
Pulumi Deployments supports OpenID Connect (OIDC) integration with cloud providers. OIDC enables your deployments to exchange a signed, short-lived token issued by the Pulumi Service for short-term credentials from your cloud provider. This can improve the security of your deployments by eliminating the need for hardcoded cloud provider credentials. If you are unfamiliar with OIDC, GitHub provides a fine introduction to the topic.
Every time a deployment runs, the Pulumi Service issues a new OIDC token specific to that deployment. The OIDC token is a short-lived, signed JSON Web Token that contains information about the deployment and that can be exchanged for credentials from a cloud provider. For AWS, Azure, and GCP, this credential exchange can be done automatically as part of deployment setup. For advanced scenarios or other cloud providers, the token is available in the
PULUMI_OIDC_TOKEN environment variable as well as in the
The token contains the standard audience, issuer, and subject claims:
|(Audience) The name of the organization associated with the deployment.|
|(Issuer) The issuer of the OIDC token: |
|(Subject) The subject of the OIDC token. Because this value is often used for configuring trust relationships, the subject claim contains information about the associated deployment. The value is composed as follows: |
The token also contains custom claims that provide additional, deployment-specific information:
|The fully-qualified identifier of the stack being deployed.|
|The deployment operation (one of |
|The name of the organization associated with the deployment.|
|The name of the project being deployed.|
|The name of the stack being deployed.|
|The deployment version.|
|The scope of the OIDC token. Always |
Configuring trust relationships
As part of the process that exchanges your deployment’s OIDC token for cloud provider credentials, the cloud provider must check the OIDC token’s claims against the conditions configured in the provider’s trust relationship. The configuration of a trust relationship varies depending on the cloud provider, but typically uses at least the Audience, Subject, and Issuer claims. These claims can be use to restrict trust to specific organizations, projects, stacks, etc.:
- The Issuer claim is typically used to validate that the token is properly signed. The issuer’s public signing key is fetched and used to validate the token’s signature.
- The Audience claim contains the name of the organization associated with the deployment. You can use this claim to restrict credentials to a specific organizaiton or organizations.
- The Subject claim contains a variety of information about the deployment. You can use this claim to restrict credentials to a specific organization, project, stack, operation, or scope.
- The various custom claims contain the same information as the Subject claim. If your cloud provider supports configuring trust relationships based on custom claims, you can use these claims for the same purposes as the Subject claim.
The Subject and custom claims are particularly useful for configuring trust relationships, as they allow you to set very fine-grained conditions for credentials.
Configuring OpenID Connect for your cloud provider
To configure OIDC for your cloud provider, refer to one of our guides: