LogoLogo
Contact Us
  • Finout Documentation
  • Get Started with Finout
    • Introduction to Finout's Suite of Features
    • Onboarding New Users to Your Finout Account
    • Single Sign-On (SSO) Setup
    • Enterprise Discount Program (EDP)
    • Cost and Usage Types
      • FairShare Cost
      • List Cost
  • Integrations
    • Cloud Services
      • Connect to AWS
      • Connect to Azure
      • Connect to Oracle
      • Connect to GCP
    • Third Party
      • Connect to Confluent
      • Connect to Databricks
      • Connect to Snowflake
      • Connect to Jira
      • Connect to Datadog
        • Datadog API Cost Calculation
        • Datadog Integration Levels
        • Datadog Usage Attribution Tags (UAT)
      • Connect to Microsoft Teams
      • Connect to ServiceNow
      • Custom Cost Centers
      • Credentials Vault
    • Telemetry
      • S3 Telemetry Integration
      • Setting Up a Datadog - Finout Metrics Integration (Export)
      • MegaBill Telemetry
    • Kubernetes
      • Connect to Kubernetes Prometheus
      • Kubernetes - How Finout Calculates K8s Costs
      • Kubernetes MegaBill
      • Kubernetes Budgeting
      • Kubernetes Anomaly Detection
      • Kubernetes Custom Dashboards
      • Kubernetes Predefined Dashboards
      • Ensure Compatibility of Your Kubernetes Monitoring with Finout
  • User Guide
    • Inform
      • MegaBill
      • Custom Drilldown
      • Custom Cost Input
      • Virtual Tags
        • Relational Virtual Tags
      • Shared Cost Reallocation
        • How to Use Shared Cost Reallocation
      • FinOps Dashboards
      • Financial Plans
      • Data Explorer
    • Optimize
      • My Commitments
      • Commitments Log
      • Anomalies
      • CostGuard
        • CostGuard - Scans
        • Connect CostGuard for AWS
        • Connect CostGuard for GCP
    • Operate
      • Reports
      • Tag Governance
  • Configuration
    • Finout API
      • Generate an API Token
      • Filter Object Definition
      • Cost API
      • Query Language API
      • Virtual Tags API
      • CostGuard API
      • Endpoint API
      • Virtual Tag Metadata API
    • Role-Based Access Control (RBAC)
      • Role Permissions
      • Managing Roles
        • Creating a Custom Role
        • Permissions List
        • Managing a Role and its Permissions
      • Managing Users
        • Inviting a User
        • Edit a User's Roles
      • Data Access Control
      • Groups
        • Create a New Group
        • Edit Group Data Access
        • Delete a group
        • Edit Group Users and SAML Groups
      • RBAC FAQs
    • Endpoints
      • Slack Notification Endpoint
  • Common Features
    • List of Common Features
      • ACL Permissions
      • Saved Views
Powered by GitBook

Still need help? Please feel free to reach out to our team at support@finout.io.

On this page
  • Oracle Integration Overview
  • 1. Create a New Group for Finout
  • 2. Add the Group a Policy to Access the Cost Reports
  • 3. Create a User for Finout
  • 4. Generate an API Key
  • 5. Integrate Oracle with Finout

Was this helpful?

Export as PDF
  1. Integrations
  2. Cloud Services

Connect to Oracle

PreviousConnect to AzureNextConnect to GCP

Last updated 2 months ago

Was this helpful?

Oracle Integration Overview

Oracle Cloud Infrastructure (OCI) is a comprehensive platform offering high-performance computing and a wide range of cloud services, designed for reliability, scalability, and security.

Integrating Finout with OCI allows you to efficiently manage your cloud resources, optimize spending, and gain valuable insights into your OCI cloud operations.

For official OCI documentation on these steps, refer to

1. Create a New Group for Finout

Access permissions in Oracle are assigned to groups. Create a separate group for Finout to ensure access only to the necessary billing resources.

  1. Go to the OCI navigation menu → Identity & Security → Domains → <Finout domain> → Groups (in the right-hand menu).

Note: If you choose to use a domain other than “Default” to set up the integration user make sure that both the user and group are contained in the same domain.

  1. Click Create Group.

  1. Fill in the Group Name and add some Description.

  1. Click Create.

2. Add the Group a Policy to Access the Cost Reports

Assign a policy to the group for accessing cost reports. In OCI, group permissions are managed through policies. By assigning a policy to the Finout group, you ensure that all its members can access only what the group policies allow.

  1. Go to the OCI navigation menu → Identity & Security → Policies.

  2. Click Create policy.

  3. Choose a name for the policy that clearly indicates its purpose for accessing cost reports.

  4. In the policy builder box at the bottom of the screen, activate the Show manual editor button and enter the following statements:

    Note: Save your tenancy for step 5.

    • Statement 1:

      Important: The following statement is not an example. You need to run this statement exactly as it is shown below.

      define tenancy usage-report as ocid1.tenancy.oc1..aaaaaaaaned4fkpkisbwjlr56u7cj63lf3wffbilvqknstgtvzub7vhqkggq This specifies the tenancy for usage reports, which is in a bucket owned by Oracle.

    • Statement 2: endorse group <group name> to read objects in tenancy usage-report Replace <group name> with the name of the group created for Finout. If you want your own groups/users to access the cost reports as well, add another policy with the relevant <group name>.

      Examples:

      • If you chose the “Default” domain: endorse group default to read objects in tenancy usage-report

      • If you chose a custom domain named “finoutdomain”: endorse group finoutdomain/default to read objects in tenancy usage-report

  5. Click Create.

3. Create a User for Finout

  1. Go to the OCI navigation menu → Identity & Security → Domains → Users.

  2. Click Create User.

  3. Fill in the name and email of the Finout user.

Note: This setup ensures that a Finout user will have access only to the specified policies, specifically the cost reports bucket. It's important to avoid selecting the administrator option and instead choose only the group dedicated to Finout for proper access control.

  1. Click Create.

4. Generate an API Key

Generate an API key to enable Finout users to access the reporting bucket via the Oracle API key.

Create an API key pair in the OCI console to enable API signing for the Finout user:

  1. Ensure an administrator user is logged into Oracle, as only administrators can perform these steps.

  2. Navigate to Identity & Security → Domains → <Finout user domain> → Users, and click the Finout user to access their profile.

  3. Navigate to the Resources section in the bottom left screen and select API keys.

  4. Make sure that the Generate API key pair is chosen.

  5. Click Download Private Key and save the key in a local directory.

  6. Click Add.

  7. A configuration is displayed. Click on the copy button below the text box and paste it into a local file editor (save for step 5).

5. Integrate Oracle with Finout

  1. In Finout, navigate to Settings > Cost Centers and click Add cost center. The Connect Accounts window appears.

  2. In OCI, click Connect Now. The Connect to OCI window appears.

  3. Fill the relevant fields from the "Configuration file preview" text box you copied in the previous step (Step 4). For “Private key data” you need to open the file and copy the entire file contents, including the key header.

  4. Click Next. The cost center is created.

Assign the user to the new Finout group you created in by selecting the appropriate box under the Groups section.

Note: You can Edit the user capabilities and limit to only API keys.

For detailed instructions, refer to the official Oracle documentation .

Note: The Oracle offers alternative methods for generating the key. Ensure that you have the complete configuration details as outlined in the following step.

here
documentation
step 1
Oracle's documentation.