Bulk Export of Audit Log Events
You can request a bulk export of audit logs, and within 3–4 business days Oracle support will begin making copies of the logs and adding them to buckets in your tenancy. The export includes logs for the specified regions, beginning after you make the request and continuing into the future.
Required IAM Policy
To access the bucket where Oracle exports the audit logs, you must be a member of the Administrators group. See The Administrators Group and Policy
Requesting an Export of Audit Logs
A member of the Administrators group for your tenancy must create a ticket at My Oracle Support and provide the following information:
- Ticket name: Export Audit Logs - <your_company_name>
- Tenancy OCID
- Ticket name: Export Audit Logs - ACME
- Tenancy OCID: ocid1.tenancy.oc1.<unique_ID>
- Regions: US East (Ashburn), region identifier= us-ashburn-1; (US West (Phoenix)), region identifier = us-phoenix-1
It can take 3–4 business days before your My Oracle Support ticket is complete and the logs are available to you.
Bucket and Object Details
This section specifies the naming conventions of the bucket and objects you receive.
Bucket Name Format
Oracle support creates buckets for audit log exports using the following naming format:
oci-logs identifies that Oracle created this bucket.
_audit identifies that the bucket contains audit events.
- <compartment_OCID> identifies the compartment where the audit events were generated.
If the OCID of the compartment that generated the audit log contains a colon, your bucket name will not match the OCID. To create a bucket, Oracle must substitute colon characters (
:) from the OCID with dot characters (
.) in the bucket name.
Object Name Format
Objects use the following naming format:
- <region> identifies the region where the audit events were generated.
- <ad> identifies the availability domain where the audit events were generated.
- <YYYY-MM-DDTHH:MMZ> identifies the start time of the earliest audit event listed in the object.
- [_<seqNum>] identifies a conditional sequence number. If present, this number means that either an event came in late or the object became too large to write. Sequence numbers start at two. Apply multiple sequence numbers to the original object in the order listed.
Files list a single audit event per line. For more information, see Contents of an Audit Log Event.
Audit introduced a version 2 schema of Audit logs but bulk export is currently only available for version 1 schema logs.