We use analytics cookies and anonymised session recordings to improve the product. Do you accept?

Oracle Cloud Coverage

Inventory and cost visibility for OCI Compute instances, block and boot volumes, Object Storage buckets, OKE clusters, Autonomous Databases and Load Balancers, across every compartment of the tenancy, with least-privilege read-only access.

3 min read

How it works

One cloud account maps to one OCI tenancy. The app signs every request with the API key of a dedicated IAM user whose group can only read.

Inventory
Lists instances, block and boot volumes, buckets, OKE clusters, Autonomous Databases, Load Balancers, VCNs and subnets in every active compartment of each selected region — with the instance each volume is attached to and the node count of each cluster.
Cost estimation
Prices each resource from Oracle's public price list (USD list prices): OCPUs and memory by shape, storage and performance units (VPUs) by volume, GB by bucket tier, ECPUs and storage by database, base and bandwidth by load balancer, and the enhanced OKE control plane. Stopped instances on standard shapes cost nothing; the Always Free allowance is not deducted.
Billed cost
Imports daily costs from the Usage API (per service, SKU, region and resource, in the tenancy's currency) for the previous and current month, refreshed daily — the figures in Costs, next to the estimates.
Optimization
Flags stopped Dense I/O, GPU and HPC instances (still billed), previous-generation shapes with their E5 equivalent, unattached volumes and boot volumes, volumes above the Balanced performance level, public buckets and large Standard buckets without auto-tiering, enhanced OKE clusters without nodes, stopped Autonomous Databases still paying for storage, load balancers without backends, and VCNs without subnets.
Connection
The credentials tab checks the key, signs a call that lists the tenancy's region subscriptions, and warns about any selected region the tenancy is not subscribed to.
Least privilege
The credentials tab generates the exact IAM policy: one inspect/read statement per resource type the app reads, never read all-resources (that would also read Vault secrets).

Coverage by service

One card per service. Each card lists its resource types and the capabilities they support.

Inventory Metrics Optimization Drift detection
Database
1 resource type
  • Autonomous Databases
Storage
2 resource types
  • Block Volumes
  • Boot Volumes
Compute
1 resource type
  • Instances
Kubernetes
1 resource type
  • OKE Clusters
Network
3 resource types
  • Load Balancers
  • VCNs
  • Subnets
Object Storage
1 resource type
  • Buckets

Group, user and policy

Done once per tenancy, in the OCI console, as a tenancy administrator.

  1. Go to Identity & Security → Domains → Default → Groups and create the group shown on the credentials tab.

  2. In the same domain, create a user (no console password needed) and add it to that group.

  3. Go to Identity & Security → Policies, choose the root compartment, create a policy and paste the statements from the credentials tab.

API key

The key the app signs its requests with.

  1. Open the user, go to API keys → Add API key, choose Generate API key pair and download the private key.

  2. Click Add: the console shows a configuration file snippet (user, fingerprint, tenancy, region). Copy it.

  3. Go to Organization → Integrations → Cloud Accounts → Add Account, choose Oracle Cloud, paste the snippet and the private key, and select the regions to monitor.

First sync

Once the account is saved, the connection test runs straight away and the inventory runs on the next hourly cycle — or trigger it from the account detail. Resources appear under Audit → OCI (Compute, Storage, Database and Network).