OSS Configuration

OSS Configuration looks like it should do something, and then it doesn't. It makes zero network calls, does no processing, and returns exactly one string. That's not a bug - it's a config node. Its whole job is to bundle your object-storage settings into a single JSON blob that the rest of this pack can consume.

You'd wire it into the pack's FFmpeg Batch Convert node, which has an optional oss_config_json input. Feed it this node's output and the converter switches from writing audio files to a local folder into uploading them to a bucket and handing back URLs - presigned ones, if you ask. So instead of re-entering five credential fields on every node that touches storage, you type them once and drag one wire.

How it works

Boring in the best way. The node takes five text fields and serializes them with json.dumps. It even normalizes path_prefix so trailing slashes don't turn into double slashes later. The endpoint default is Alibaba's OSS Beijing region, which tells you who this pack is for - but because the upload side uses boto3's S3 API, any S3-compatible endpoint works. The code's own docstring names Aliyun OSS, Cloudflare R2, and AWS S3.

The fields

All five are required, and there are no optional inputs:

• endpoint - default https://oss-cn-beijing.aliyuncs.com
• access_key_id and access_key_secret - your storage credentials
• bucket_name - the target bucket
• path_prefix - where inside the bucket files land, default comfyui/output/

The single output, oss_config_json, is the string you wire into FFmpegBatchConvertNode's oss_config_json input.

The honest warning

Your access key secret is sitting in a plain text field, which means it's embedded in your workflow JSON and will travel inside any PNG metadata you save. That's acceptable on a disposable cloud pod. It is not acceptable in a workflow you share publicly - scrub the credentials before you post it, or you're handing out a bucket key to the entire internet. This is one of those cases where the convenience of "type it once" has a real cost.

Since this node is pure config, a workflow that loads with it and appears to do nothing is behaving correctly. If you're looking for an OSS provider node to use across a broader pipeline, this one is hardwired to its own pack - other packs' storage uploaders will expect their own config shapes, so don't assume this JSON is portable. Install via ComfyUI Manager (search dll-comfyui-node) or git clone https://github.com/dlliang14/dll-comfyui-node into custom_nodes, then restart. No extra model files - its only real dependency, boto3, rides along with the pack's requirements.