Skip to main content

Oracle Billing

Use Oracle Billing to ingest Oracle Cloud Infrastructure (OCI) usage and cost report data into Cloudaware Cost Management.

info
  • Audience: Cloudaware administrators, FinOps, finance teams
  • Outcome: Oracle usage and cost reports discovered and ingested into Cloudaware

This guide covers:

  • OCI usage and cost report access.
  • Required tenancy-level policies.
  • IAM group and user requirements.
  • Oracle Billing configuration in Cloudaware.
  • Verification and troubleshooting steps.

Prerequisites​

  • Oracle Cloud integration configured in Cloudaware (see Setup).
  • OCI tenancy access with permission to create or update policies.
  • IAM group used by the Cloudaware OCI credentials.
tip

Ensure that the user or group used by Cloudaware for OCI access is clearly identified, as you will reference it in the policy.

How It Works​

  • Oracle Cloud generates usage and cost reports and stores them in an Object Storage bucket managed by Oracle.
  • A tenancy-level policy grants your group permission to read those reports.
  • Cloudaware uses the same tenancy credentials you configured for OCI integration to read billing data.

Configure OCI Usage and Cost Report Access​

  1. Sign in to the Oracle Cloud Console with administrator permissions.

  2. Open the Navigation menu and go to Identity & Security → Policies.

  3. Create (or update) a tenancy‑level policy that grants read access to the usage report tenancy. For example:

    define tenancy usage-report as ocid1.tenancy.oc1..aaaaaaaaned4fkpkisbwjlr56u7cj63lf3wffbilvqknstgtvzub7vhqkggq
    endorse group {your-group-name} to read objects in tenancy usage-report

    Where:

    • ocid1.tenancy.oc1..aaaaaaaaned4fkpkisbwjlr56u7cj63lf3wffbilvqknstgtvzub7vhqkggq is the Oracle tenancy OCID used by Oracle for centralized usage-report storage (see Oracle documentation for the latest value).
    • {your-group-name} is the group whose user credentials are used to add the Oracle tenancy to Cloudaware.

  4. Save the policy and allow time for it to propagate.

note

Oracle may take 12–24 hours to generate and expose billing reports after configuration changes.

Oracle Billing Discovery in Cloudaware​

Cloudaware automatically discovers Oracle billing integrations once the prerequisites are met.

To review discovered billing sources:

  1. In Cloudaware, go to Admin.
  2. Locate Oracle Billing under Billing integrations.
  3. Click CONFIGURED to see discovered billing sources.
  4. Review the list of Oracle billing integrations and check the Status column:
    • Green status indicates successful configuration and data access.
    • Red status indicates a problem; verify policies and OCI integration settings.

Verification​

After initial setup:

  • In Cloudaware Admin → Oracle Billing, verify that the integration status is green.
  • In Cost Management dashboards, verify that Oracle spend appears alongside other providers for the expected periods.
  • Validate that tenancy and compartment information aligns with what you see in the Oracle console.

Troubleshooting​

Oracle Usage and Cost Reports Not Accessible​

  • In Oracle Cloud:

    • Open Identity & Security → Policies.

    • Verify that a tenancy‑level policy exists to allow read access to the usage report tenancy, for example:

      define tenancy usage-report as ocid1.tenancy.oc1..aaaaaaaaned4fkpkisbwjlr56u7cj63lf3wffbilvqknstgtvzub7vhqkggq
      endorse group {your-group-name} to read objects in tenancy usage-report

    • Confirm that {your-group-name} is the group whose user credentials are used for Cloudaware OCI integration.

  • Allow 12–24 hours after policy changes for Oracle to expose usage and cost reports.

Cloudaware Oracle Billing Integration Red or Missing​

  • In Cloudaware, go to Admin:
    • Open Oracle Cloud section. Check that the Oracle tenancy integration is configured and has green status.
    • Open the Oracle Billing section. Confirm that discovered billing integrations have green status.
  • If status remains red:
    • Recheck the policy definition and group membership in Oracle.
    • Confirm credentials used in Cloudaware belong to the group referenced in the policy.

Security Notes​

  • Limit the policy scope to read‑only access to Oracle’s usage‑report tenancy.
  • Use a dedicated IAM group for Cloudaware access and review group membership regularly.
  • Rotate user credentials used by Cloudaware for OCI integration in accordance with your security standards.