16 ‐ OCI Object Storage ↔ Compute API Connectivity using CLI - SanjeevOCI/Ocidocs GitHub Wiki

Objective: Establish API-based connectivity between OCI Object Storage and a Compute instance, configure OCI CLI, and perform file transfers securely.

✅ Prerequisites

  • A Bastion (public) VM for access
  • A Private Application VM (target for API access)
  • Proper NSG/SecList rules between Bastion ↔ App VM

Object storage_to_instance through API connectivity

Objective- API connectivity between Object Storage and a Compute instance in Oracle Cloud Infrastructure (OCI)

16_Object storage_to_instance_API connectivity_1

16_Object storage_to_instance_API connectivity_2

16_Object storage_to_instance_API connectivity_3

16_Object storage_to_instance_API connectivity_4

16_Object storage_to_instance_API connectivity_5

16_Object storage_to_instance_API connectivity_6

16_Object storage_to_instance_API connectivity_7

New_Server_1

Successful_Ping_Telnet

Privkey_1

Privkey_2

Successful_login_Application_Server

Successful_Ping_Application_to_Bastion_server

OCI CLI Install_1

OCI CLI Install_2

OCI CLI Install_3

Create_Bucket_1

Create_Bucket_2

Create_Bucket_3

OCI CLI Install_4

OCI CLI Install_5

API_Connectivity_12

API_Connectivity_12_1

API_Connectivity_13

OCI CLI Install_6

OCI CLI Install_7

Add_API_Key

Add_API_Key_2

Add_API_Key_3

OCI CLI Install_8

Sample file uploaded to bucket

✅ Summary

  • Set up network connectivity between Bastion and Private App VM
  • Installed and configured OCI CLI for API access
  • Created API keys and configured user authentication
  • Created an Object Storage bucket
  • Uploaded and retrieved objects securely via CLI

This approach is ideal for private workloads, secure backups, or headless automation without exposing Object Storage via public endpoints.