Onboard Oracle Cloud Infrastructure

Run the downloadable tenancy setup script as a tenancy administrator, then paste the printed JSON into CloudPulse Accounts. Production uses identity-domain federation (no PEM stored).

Prerequisites

Tenancy administrator access.
Tenancy OCID and home region.
For federated setup: Python 3 with the oci SDK, and an authenticated oci session for the admin user (setup only — workers do not use your CLI session).

Steps

Accounts → Add OCI. Enter a display name and the tenancy OCID. When federation IDs are available from CloudPulse, include them so the download can auto-run WIF grant.
Download cloudpulse-oci-customer-setup.ps1 (filename may include a short suffix). The script creates the CloudPulse IAM group/user/policy (config-audit / config-audit-policy pre-GA names) and, when federation IDs are filled, runs the embedded WIF helper to create the service user, OAuth app, and Identity Propagation Trust.
Paste the JSON printed by the script into Accounts (federated shape: domain URL + OAuth client id/secret). Do not commit this JSON to source control.
Save and wait until data appears in Insights. Compartments are discovered automatically — one CloudPulse row per tenancy, not per compartment.
Verify in OCI Insights (compute, networking, Object Storage, Cloud Guard, usage costs, and so on).

Billing

Usage costs use Oracle’s usage/reporting APIs with the CloudPulse policy (including the usage-report endorse). There is typically no separate “export bucket” step like Azure or GCP.

You vs CloudPulse support

You	CloudPulse support
Run setup with tenancy admin session; paste federated JSON; provide tenancy OCID.	Provide federation tenant/principal IDs for the download; help if Domain APIs reject WIF creation.

API

GET /v1/accounts/oci-setup-script?tenancy_ocid=…&region=…
GET /v1/accounts/{account_id}/oci-setup-script

Hosted CloudPulse rejects PEM private keys on create/patch. Use the federated JSON path for production.