Nodes/ComfyUI-MinioConnector/Init Aliyun OSS Connector ๐Ÿ‘
ComfyUI Node

Init Aliyun OSS Connector ๐Ÿ‘

One node holds your bucket, keys, and connection

By MieMieeeeeยทCreated about a year agoยทUpdated about a year agoยท 5
Init Aliyun OSS Connector ๐Ÿ‘
    • aliyun_oss_connector
    โ—„endpointโ–บ
    โ—„access_key_idโ–บ
    โ—„access_key_secretโ–บ
    โ—„bucket_nameโ–บ

    If you use Alibaba Cloud, this is your front door. InitAliyunOSSConnector is the Aliyun twin of the pack's InitMinioConnector: it takes your credentials and produces a connector object that every Aliyun node in the pack consumes. Aliyun OSS is Alibaba Cloud's object storage - the commercial, cloud-hosted sibling of self-hosted MinIO, and arguably the default storage backend for anyone building AI pipelines on Chinese cloud infrastructure.

    The one real difference from the MinIO init node: bucket selection. On the MinIO side, you pass the bucket name into each upload/download node separately. Here, the bucket_name is baked into the connector at init time. Every Aliyun node downstream just works against that one bucket - there's no bucket input on them. That's simpler to wire, but it means if you want to touch two buckets you need two of these init nodes.

    The inputs. Four strings:

    • endpoint - your OSS region endpoint, something like oss-cn-hangzhou.aliyuncs.com. No scheme, no trailing slash.
    • access_key_id / access_key_secret - the AccessKey pair you generate in the Alibaba Cloud console (keep the secret genuinely secret; this node stores it as plaintext).
    • bucket_name - the bucket this connection will read and write.

    The output is one aliyun_oss_connector of custom type ALIYUN_OSS_CONNECTOR, feeding AliyunOSSUploadFile, AliyunOSSUploadFolder, and AliyunOSSDownloadBucket.

    How it works. It constructs an oss2.Bucket(oss2.Auth(access_key_id, access_key_secret), endpoint, bucket_name) using Alibaba's official oss2 SDK and returns it. Same lazy-connection caveat as the MinIO side: nothing actually hits the network here. A bad key surfaces as an OssError on your first upload or download, not at init. So if your first Aliyun node in the chain throws, don't blame it - audit the credentials in this one.

    Install. ComfyUI Manager, search "ComfyUI-MinioConnector", install, restart. Manual:

    cd ComfyUI/custom_nodes
    git clone https://github.com/MieMieeeee/ComfyUI-MinioConnector
    cd ComfyUI-MinioConnector
    pip install -r requirements.txt
    

    Requirements include oss2, tqdm, and a couple of Aliyun SDK packages. No models, no GPU dependencies.

    Gotchas. The endpoint is the classic first mistake - people paste a full URL and the SDK chokes. Use bare region-endpoint format. And because the keys live in the workflow JSON, treat any workflow file that contains them as confidential: don't post it, don't drag it onto a shared machine. This is Alibaba Cloud real money storage, after all - a leaked key is a bill, not a bummer.

    Category๐Ÿ‘ Minio-Connector/๐Ÿ‘ Aliyun OSS Connector

    Inputs (4)

    NameTypeDefaultDescription
    endpointSTRINGโ€”
    access_key_idSTRINGโ€”
    access_key_secretSTRINGโ€”
    bucket_nameSTRINGโ€”

    Outputs (1)

    NameTypeDescription
    aliyun_oss_connectorALIYUN_OSS_CONNECTORโ€”