When wiring up the Chronosphere Pulumi provider, authenticate with an unrestricted service account token or a SysAdmin user's personal access token, nothing less. Export it as CHRONOSPHERE_API_TOKEN in the shell where you run Pulumi. Do not reuse the write-only ingestion service account for this; Pulumi needs admin rights and will fail otherwise. Keep that token out of your shell history and CI logs, and rotate it like any other admin credential since Chronosphere tokens do not expire on their own.

Context: Official docs (Chronosphere Pulumi provider): documents that Pulumi performs tasks requiring administrative privileges and therefore requires an API token with administrative privileges. That means either an unrestricted service account, or a user or service account on a team with the SysAdmin role. If you skip passing a token as an argument, the provider reads it from the CHRONOSPHERE_API_TOKEN environment variable. Agents that try a least-privilege restricted token get blocked on nearly every operation.