OCI Onboarding


The purpose of onboarding is to help you setup an CoreStack account with respect to an Oracle Cloud Infrastructure (OCI) account with governance policies. To begin monitoring your resources for OCI, you must complete some tasks on the OCI Tenant Console and some on CoreStack. After you add your OCI tenant to CoreStack, the API integration between OCI and CoreStack is established and you can monitor resource configuration issues.


  • Root compartment (tenancyId).
  • An IAM user with user id (authUserId).
  • API key to be generated. Private Key and keyFingerprint used while onboarding.
  • Policy to be created with required access to the APIs and attach the policy to the Group where the created user is added into the group.

Oracle Cloud IDs (OCIDs)

Most types of Oracle Cloud Infrastructure resources have an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). It's included as part of the resource's information in both the Console and API.

To use the API, you need the OCID for your tenancy.

OCIDs use this syntax:


-- ocid1: The literal string indicating the version of the OCID.

-- resource type: The type of resource (for example, instance, volume, vcn, subnet, user, group, and so on).

-- realm: The realm the resource is in. A realm is a set of regions that share entities. Possible values are oc1 for the commercial realm, oc2 for the Government Cloud realm, or oc3 for the Federal Government Cloud realm. The regions in the commercial realm (OC1) belong to the domain oraclecloud.com. The regions in the Government Cloud (OC2) belong to the domain oraclegovcloud.com.

-- region: The region the resource is in (for example, phx, iad, eu-frankfurt-1). With the introduction of the Frankfurt region, the format switched from a three-character code to a longer string. This part is present in the OCID only for regional resources or those specific to a single availability domain. If the region is not applicable to the resource, this part might be blank (see the example tenancy ID below).

-- future use: Reserved for future use. Currently blank.

-- unique ID: The unique portion of the ID. The format may vary depending on the type of resource or service

Where to Find Your Tenancy's OCID

If you use the Oracle Cloud Infrastructure API, you need your tenancy's OCID in order to sign the API requests. You also use the tenancy ID in some of the IAM API operations.

Get the tenancy OCID from the Oracle Cloud Infrastructure Console on the Tenancy Details page:

1). Open the Profile menu (User menu icon) and click Tenancy: <your_tenancy_name>.

2). The tenancy OCID is shown under Tenancy Information. Click Copy to copy it to your clipboard.


The tenancy OCID looks something like this (notice the word "tenancy" in it):

IAM Service

The IAM service requires you to assign a unique, unchangeable name to each of your IAM resources (users, groups, dynamic groups, federations, and policies). The name must be unique within the scope of the type of resource (for example, you can only have one user with the name BobSmith). Notice that this requirement is specific to IAM, but also applies to some other services. (Most services let you assign an optional display name.)

The name you assign to a user at creation is their login for the Console.

You can use these names instead of the OCID when writing a policy (for example, Allow group <GROUP NAME> to manage all-resources in compartment <COMPARTMENT NAME>).

In addition to the name, you must also assign a description to each of your IAM resources.

Required IAM Policy

If you're in the Administrators group, then you have the required access for managing users. You can create a policy that gives someone the power to create new users and credentials but not control which groups those users are in.

For users resource type, you can use target.user.id as variable and Entity (OCID) as variable type.

Required Keys

1). After you have created a user in IAM for the person or system who will be calling the API, put that user in at least one IAM group with any desired permissions.

2). Get below items:

3). Upload the public key from the key pair in the Console. See How to Upload the Public Key.

Resource List

After onboarding, inventory will auto populate. We support below resources.

  • Compute -> Compute -> Instances
  • Compute -> Compute -> Dedicated_VM_Host
  • Compute -> Compute -> Instance_Configuration
  • Compute -> Compute -> Instance_Pools
  • Compute -> Compute -> Cluster_Networks
  • Compute -> Compute -> Autoscaling_Configuration
  • Databases -> MySQL -> DB_Systems
  • Databases -> MySQL -> Backups
  • Databases -> Oracle_NoSQL_Database -> Tables
  • Oracle_DataBase -> BareMetal_VM_Exadata -> ExaData_infrastructure
  • Oracle_DataBase -> BareMetal_VM_Exadata -> ExaData_VM_Clusters
  • Storage -> Block_Storage -> Block_Volumes
  • Storage -> Block_Storage -> Block_VolumeBackups
  • Storage -> Block_Storage -> Attached_Volumes
  • Storage -> File_Storage -> File_Systems
  • Storage -> Block_Storage -> Mount_Targets
  • Networking -> Virtual_Cloud_Networks -> VCN
  • Networking -> Virtual_Cloud_Networks -> Internet_Gateway
  • Networking -> Virtual_Cloud_Networks -> LocalPeeringGateways
  • Networking -> Virtual_Cloud_Networks -> Security_Lists
  • Networking -> Virtual_Cloud_Networks -> NetworkSecurityGroups
  • Networking -> Customer_Connectivity -> Fast_Connect
  • Networking -> Customer_Connectivity -> Dynamic_Routing_Gateway
  • Networking -> Ip_Management -> Reserved_Publics_IPs
  • Networking -> Load_Balancers -> Load_Balancer
  • Networking -> DNS_Management -> Zones
  • Identity_Security -> Web_Application_Firewall -> Waf_Policy
  • Identity_Security -> Identity -> Users
  • Identity_Security -> Identity -> Groups
  • Identity_Security -> Identity -> Policies
  • Identity_Security -> Identity -> Users_Api_Keys
  • Identity_Security -> Identity -> Users_Auth_Tokens
  • Identity_Security -> Scanning -> HostScan
  • Identity_Security -> Scanning -> PortScan
  • Developer_Services -> Containers -> Container_Registry
  • Developer_Services -> Containers -> Artifact_Registry
  • Developer_Services -> Functions -> Applications
  • Developer_Services -> Containers -> Kubernetes_Clusters
  • Analytics_AI -> Data_Lake -> Data_Flow
  • Application_Integration -> Content_Management -> Instances

Set Governance Configuration

Set below activity logs and alert configurations.

  1. Hover OCI Total Cloud Accounts and click Tenancy.
  1. Click View > View Settings.
  2. Click Governance Configuration.
  3. Click Configure. You can set Activity Logs configurations, Alerts configuration.
    Below policies are required for resource creation.
  • Allow group <group_name> to manage serviceconnectors in tenancy
  • Allow group <group_name> to manage ons-topics in tenancy
  • Allow group <group_name> to manage ons-subscriptions in tenancy
  1. Click Create New > Next.
  1. In Regions, select regions based on account onboarding.
  2. To create a service connector, enter Service Connector Name.
  3. To create a topic, enter Topic Name.
  4. To apply this selection as default template, select Apply Default Template.
  1. Click Save.
  2. In Notification settings, enter notification email address.
  3. To access a public URL, enter URL in Webhook.
  4. To allow external applications to share content in Microsoft Teams channels, add URL in Microsoft Teams Webhook.
  1. Click Finish. The Activity log is created.
  2. Click Alerts > Configure.
  1. Click Create New > Next.
  1. In Regions, select regions based on account onboarding.
  2. To create a topic, enter Topic Name.
  3. To apply this selection as default template, select Apply Default Template.
  4. Click Save.

Did this page help you?