/oci/. All operations involve network
I/O to the remote object store. Uses aioboto3 against OCI’s
S3-compatible API.
For credential setup, see OCI Setup.
Install the extra:
Config
OCIVFS(config) takes an OCIConfig object with the bucket name,
OCI tenancy namespace, region, and Customer Secret Key credentials.
The S3-compatible endpoint is auto-built from namespace + region
unless endpoint_url is supplied. Both READ and WRITE modes are
supported.
Fields marked secret are redacted in snapshots.
For
write: conditional on this provider, see S3-compatible stores.
VFS.md
The VFS.md an agent reads with OCI Object Storage mounted at/<path>.
- Rendered
- Raw
my-bucket contains:
/oci/ exposes:
/oci/data/users.csv maps to OCI key
data/users.csv.
Cache
The OCI VFS usesIndexCacheStore with index_ttl = 600
(10 minutes). Directory listings are cached for up to 600 seconds before
being refreshed from OCI. A configured index: replaces this lifetime with its own ttl, and the mount’s ttl: caps it.
Integration
What OCI answers through its own API, so fewer files are read. Integration explains each command.Example
Shell Commands
The OCI VFS supports the full set of shell commands since it operates on real file content (text, binary, JSON, CSV, etc.). Large files benefit from range reads to avoid downloading entire objects.Read Commands
Text Processing
File Operations
Path Utilities
Compression
Encoding
Use Cases
- AI agents accessing OCI data: Mount OCI buckets for agents to read and process datasets
- Data pipelines: Read and write OCI objects with shell-like commands
- FUSE mounting: Expose OCI buckets through a virtual FUSE mount for external tools