📢 New Feature in OCI: Attach Files to Support Requests Using CLI & API

 

Managing Oracle Cloud Infrastructure (OCI) Support Requests (SRs) just got easier.

As of the latest release, you can now attach files — such as logs, screenshots, or diagnostic reports — directly to your Support Requests using the OCI CLI or REST API.

This eliminates the need to switch between interfaces and allows faster collaboration with Oracle Support teams.

Why This Matters

When you raise a support request, Oracle Support often asks for:

  • Logs, configuration files, or screenshots

  • Diagnostic outputs from database, compute, or network services

  • Supporting documents that speed up troubleshooting

With this feature, you can now automate and script file attachments, making it easy to integrate into your existing support workflows.

Prerequisites

Before you begin, ensure:

  1. You have a valid OCI account and access to the tenancy.

  2. Your OCI CLI is installed and configured with API keys. Refer to for setup: https://docs.oracle.com/en-us/iaas/Content/GSG/Tasks/usingsupport.htm

  3. You already created a Support Request (Incident) and have its Incident Key.

Attaching Files Using OCI CLI

The new command oci support incident put-attachment allows you to upload files directly to an SR.

Syntax

oci support incident put-attachment \
--attachment-name <text> \
--compartment-id <compartment-ocid> \
--file <text> \
--incident-key <support-request-id> \
--is-restricted-flag <true_or_false> \
[OPTIONS]

Example

oci support incident put-attachment \
--attachment-name "db-alert-log" \
--compartment-id ocid1.compartment.oc1..aaaaexampleuniqueID \
--file /u01/oracle/19chome/trace/db_alert.log \
--incident-key ocid1.supportrequest.oc1..aaaaexampleuniqueID \
--is-restricted-flag false

✅ In this example:

  • db-alert-log is the name of the file as it appears in the SR.

  • The file /u01/oracle/19chome/trace/db_alert.log will be uploaded.

  • The attachment is visible to both customer and Oracle Support (false = not restricted).

Attaching Files Using REST API

For developers and automation workflows, the feature is also available via the Incident Management API.

API Reference

https://docs.oracle.com/en-us/iaas/api/#/en/incidentmanagement/20181231/Incident/PutAttachment

Request Example

POST https://incidentmanagement.<region>.oci.oraclecloud.com/20181231/incidents/{incidentKey}/attachments
Content-Type: multipart/form-data
Authorization: Bearer <auth_token>

--boundary
Content-Disposition: form-data; name="file"; filename="db_alert.log"
Content-Type: text/plain

<contents of db_alert.log>
--boundary--

Key Parameters

  • incidentKey → The support request ID.

  • file → The log or document you want to upload.

  • isRestrictedFlag → Whether Oracle only can view it (true) or customer also can (false).

Putting It All Together

  1. Raise a Support Request (SR) in OCI Console or via API.

  2. Identify the Incident Key (SR ID).

  3. Attach files via CLI for simple scripts or API for automation pipelines.

  4. Monitor the SR in OCI Console — your attachments will now be visible to Oracle Support.

Key Benefits

  • Faster Response/Actions: Provide logs and files without delays.

  • Automation-ready: Integrate with your scripts and CI/CD pipelines.

  • Security control: Decide whether files are restricted to Oracle only.


Author: Narasimharao Karanam


Comments

Post a Comment