Viewing docs for Kurrent Cloud v0.3.1
published on Tuesday, Oct 6, 2026 by Kurrent
published on Tuesday, Oct 6, 2026 by Kurrent
Kurrent Cloud: Installation & Configuration
I want to use the Pulumi Kurrent Cloud package (kurrentcloud) in my project.
## Provider details
- Package: kurrentcloud
- Version: v0.3.1
- Publisher: Kurrent
- Source: pulumi
- Repository: https://github.com/kurrent-io/pulumi-kurrentcloud
## Documentation
The Pulumi Cloud Registry API serves canonical, up-to-date docs for this package — including private packages and every published version. Send the "Accept: text/markdown" header for clean readable content, or "application/json" for structured data.
Start at the navigation tree, which cross-links to the readme, installation guide, and per-resource docs URL template:
- https://api.pulumi.com/api/registry/packages/pulumi/eventstore/kurrentcloud/versions/latest/nav
Returns a summary by default. The full tree can be hundreds of kB for large providers, so prefer targeted search: append "?q=<query>&depth=full" to filter by resource/function title or token (for example "?q=bucket&depth=full"). Only request the full nav without a query if you actually need to enumerate every resource.
Other endpoints:
- Overview and getting started: https://api.pulumi.com/api/registry/packages/pulumi/eventstore/kurrentcloud/versions/latest/readme
- Installation and configuration: https://api.pulumi.com/api/registry/packages/pulumi/eventstore/kurrentcloud/versions/latest/installation
- Per-resource/function docs: https://api.pulumi.com/api/registry/packages/pulumi/eventstore/kurrentcloud/versions/latest/docs/{token}?lang={lang}
Replace {token} with the percent-encoded token from the nav response (for example aws:s3/bucket:Bucket).
Replace {lang} with typescript, python, go, csharp, java, yaml, or hcl.
Fetch the installation endpoint above for the correct setup steps — install instructions vary between native providers, bridged Terraform providers, and component packages.
Help me get started using this provider. Show me a complete Pulumi program that provisions a common resource, including all necessary configuration and imports.
Kurrent CloudViewing docs for Kurrent Cloud v0.3.1
published on Tuesday, Oct 6, 2026 by Kurrent
published on Tuesday, Oct 6, 2026 by Kurrent
Installation
The Kurrent Cloud provider is available as a package in all Pulumi languages:
- JavaScript/TypeScript:
@kurrent/pulumi-kurrentcloud - Python:
pulumi_kurrentcloud - Go:
github.com/kurrent-io/pulumi-kurrentcloud/sdk/go/kurrentcloud - .NET:
Kurrent.Pulumi.KurrentCloud
Setup
Configure the provider
The Pulumi provider needs credentials to authenticate requests from your computer to Kurrent Cloud. Your credentials are never sent to pulumi.com. The provider needs to be configured with Kurrent Cloud credentials before it can be used to create resources.
The provider supports two authentication methods:
- Service Account credentials (recommended for automation) - configure
clientIdandclientSecretwith the credentials of a Kurrent Cloud Service Account. The provider then obtains short-lived access tokens via the OAuth2 client-credentials grant, andtokenis not used. - Refresh token - configure
tokenwith a personal refresh token. This is the legacy method; the token is bound to a user account.
In both cases you also need the organization id: go to the list of organizations you have access to in the Kurrent Cloud console, choose the organization that you will be provisioning resources for, and find the organization id in the settings.
Service Account credentials can be provided via environment variables:
$ export ESC_CLIENT_ID=<YOUR_CLIENT_ID>
$ export ESC_CLIENT_SECRET=<YOUR_CLIENT_SECRET>
$ export ESC_ORG_ID=<YOUR_ORGANIZATION_ID>
or via stack configuration:
pulumi config set kurrentcloud:clientId <YOUR_CLIENT_ID>
pulumi config set kurrentcloud:clientSecret <YOUR_CLIENT_SECRET> --secret
pulumi config set kurrentcloud:organizationId <YOUR_ORGANIZATION_ID> --secret
Refresh token authentication works the same way. First, you need an access token for your user, which you can obtain from the Kurrent Cloud console.
<YOUR_ACCESS_TOKEN>: your access token<YOUR_ORGANIZATION_ID>: the Kurrent Cloud organization id
Once the credentials are obtained, there are two ways to communicate your authorization tokens to Pulumi:
Set the environment variables
ESC_TOKENandESC_ORG_ID:$ export ESC_TOKEN=<YOUR_ACCESS_TOKEN> $ export ESC_ORG_ID=<YOUR_ORGANIZATION_ID>Set them using configuration, if you prefer that they be stored alongside your Pulumi stack for easy multi-user access:
pulumi config set kurrentcloud:token <YOUR_ACCESS_TOKEN> --secret pulumi config set kurrentcloud:organizationId <YOUR_ORGANIZATION_ID> --secret
Required options can be omitted if you configure them using environment variables.
| Option | Required/Optional | Description |
|---|---|---|
token | Required unless Service Account credentials are set | Refresh token. You can retrieve this from the ‘Access Tokens’ section of the Kurrent Cloud console. |
organizationId | Required | The organization id. You can find it in the organization settings page of the Kurrent Cloud console. |
clientId | Optional | Service Account client id. Must be set together with clientSecret. |
clientSecret | Optional | Service Account client secret. When both clientId and clientSecret are set, Service Account authentication is used and takes priority over token. |
url | Optional | The URL of the Kurrent Cloud API. This defaults to the public cloud instance of Kurrent Cloud. |
tokenStore | Optional | The location on the local filesystem of the token cache. This is shared with the Kurrent CLI. Only used with refresh token authentication. |
identityKitUrl | Optional | The base URL of the token endpoint used for Service Account authentication. You would normally not need to set it. |
Kurrent CloudViewing docs for Kurrent Cloud v0.3.1
published on Tuesday, Oct 6, 2026 by Kurrent
published on Tuesday, Oct 6, 2026 by Kurrent