---
title: OCI Audit logs
description: This integration guide focuses on connecting your Oracle Cloud Infrastructure (OCI) environment to Coralogix using OCI Notification Service.
url: https://coralogix.com/docs/integrations/oci/oci-audit-logs/
product: ingress
feature: Logs Ingress
feature_id: logs.ingress
feature_identifier: ingress/logs.ingress
last_updated: '2026-07-06'
---

# OCI Audit logs

## Overview

This integration guide focuses on connecting your Oracle Cloud Infrastructure (OCI) environment to Coralogix using OCI Notification Service. To complete this integration, you'll need to create a topic, set up a subscription, and configure a service connector to send audit logs to Coralogix.

The process involves three main steps: creating a topic in OCI Notification Service, setting up a subscription with a Coralogix webhook, and configuring a service connector to route audit logs to the notification service. Each step requires specific configuration parameters which are detailed in the sections below.

## Prerequisites

* An OCI tenancy
* Audit logging must be enabled in the Audit section under Identity & Security

Note

Audit logging is generally enabled by default on all OCI tenancies. However, it's recommended to verify this by checking for events in the Audit Events section.

[![OCI Audit Events](/docs/assets/images/oci-audit-events-267bdb93e7ee180360b9f91efa2a7699.webp)](https://coralogix.com/docs/assets/images/oci-audit-events-267bdb93e7ee180360b9f91efa2a7699.webp)

## Installation instructions

### Step 1: Create a Topic

To send logs to Coralogix, you must first create a topic and subscribe to it to receive data. This is part of the OCI Notification Service.

Search for "topic" in the OCI search bar.

[![OCI create topics](/docs/assets/images/oci-create-topics-f4306e22da42b2b1ab316fafa40ed799.webp)](https://coralogix.com/docs/assets/images/oci-create-topics-f4306e22da42b2b1ab316fafa40ed799.webp)

### Step 2: Create a Subscription

Next, navigate to the topic and create a subscription so an endpoint can subscribe to it (similar to a Pub/Sub model).

[![OCI create subscription](/docs/assets/images/oci-create-subscription-17308c9597a858858fb0a8f2deae089e.webp)](https://coralogix.com/docs/assets/images/oci-create-subscription-17308c9597a858858fb0a8f2deae089e.webp)

To create the webhook URL refer to our documentation on [Generic Incoming Webhooks](https://coralogix.com/docs/integrations/incoming-webhooks/generic-incoming-webhooks.md)

After creating the subscription:

1. Go to your Coralogix account and check the Logs section
2. Select the appropriate app name and subsystem name
3. You should see a single log entry with a URL
4. Click on that URL to confirm the subscription

[![OCI confirm subscription](/docs/assets/images/oci-confirm-subscription-21edd16d43372fa4787fe71d8abeef05.webp)](https://coralogix.com/docs/assets/images/oci-confirm-subscription-21edd16d43372fa4787fe71d8abeef05.webp)

### Step 3: Create a Service Connector

To enable communication between OCI services, create a service connector. Search for "connector" with the messaging tag in the search bar, then click Create Connector.

#### Required parameters

1. **Name** - Choose a descriptive name for your connector
2. **Compartment** - Select the appropriate compartment
3. **Source** - Select "Logging" (since we're fetching logs from the default audit log group)
4. **Target** - Select "Notifications"
5. **Log Group** - For audit logs, use the default `_Audit` log group (alternatively, you can create a custom log group)
6. **Topic** - Select the topic created in [Step 1](#step-1-create-a-topic)

[![OCI create service connector](/docs/assets/images/oci-create-connector-8e95788d8d8be73d2d88c691873d5e5b.webp)](https://coralogix.com/docs/assets/images/oci-create-connector-8e95788d8d8be73d2d88c691873d5e5b.webp)

[![OCI enable logs](/docs/assets/images/oci-create-connector-enable-logs-4bfdb4487da2a646795e516d5274a242.webp)](https://coralogix.com/docs/assets/images/oci-create-connector-enable-logs-4bfdb4487da2a646795e516d5274a242.webp)

Note

Make sure to check the "Create default policy" checkbox before clicking Create. Log ingestion typically takes 2-3 minutes to begin.