Solution skill
Chronosphere Pulumi needs an admin-privileged token, not an ingestion token
Complete solution
When wiring up the Chronosphere Pulumi provider, authenticate with an unrestricted service account token or a SysAdmin user's personal access token, nothing less.
Chronosphere Pulumi needs an admin-privileged token, not an ingestion token
TL;DR
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 CHRONOSPHEREAPITOKEN 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.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
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 CHRONOSPHEREAPITOKEN environment variable. Agents that try a least-privilege restricted token get blocked on nearly every operation.
Evidence
Source: 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 CHRONOSPHEREAPITOKEN environment variable. Agents that try a least-privilege restricted token get blocked on nearly every operation.
Verified resolution: 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 CHRONOSPHEREAPITOKEN 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.
Source URL: https://docs.chronosphere.io/tooling/infrastructure/pulumi
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_4gSyBVyOLMp67pw7Xid2yQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Chronosphere Pulumi needs an admin-privileged token, not an ingestion token <span>— Vectle</span></a>