Ino S3 Config

Every S3 node in ComfyUI Ino Nodes takes an s3_config - a JSON string holding your access key, secret, endpoint, region, and bucket. Ino S3 Config is the node that builds that string for you. Instead of hand-typing a JSON blob you'll paste into a dozen places, you fill in five fields once and wire the config output wherever it's needed. It's the boring-but-essential setup node that the whole S3 half of this pack depends on.

It's part of ComfyUI Ino Nodes (nobandegani/ComfyUI-InoNodes), the 125+-node V3-schema pack, and it's the first of the pack's 16 S3 helper nodes - the largest single feature area of the pack.

How it works

Five string inputs, each mapping to an S3 credential:

• access_key_id and access_key_secret - your credentials. Required; the other nodes reject a config without them.
• endpoint_url - the S3 endpoint. For AWS this is something like https://s3.<region>.amazonaws.com; for MinIO, DigitalOcean Spaces, Cloudflare R2, or any S3-compatible store, it's their URL. This is what makes the whole pack work with non-AWS storage.
• region_name - the bucket's region.
• bucket_name - the target bucket.

Two outputs: success (boolean) and config (STRING) - the JSON string every other Ino S3 node accepts. Wire config into any S3 node's s3_config input and you're done.

The genuinely nice part: env vars

You don't strictly need this node at all, because every S3 node can read credentials from environment variables instead. If S3_ACCESS_KEY, S3_ACCESS_SECRET, S3_ENDPOINT_URL, S3_REGION_NAME, and S3_BUCKET_NAME are set, the S3 nodes fill in any empty fields from them automatically. So there are two clean ways to work:

• One machine, fixed bucket: set the env vars once (in your ComfyUI launch script) and leave every node's s3_config empty. Zero credential-handling in the graph.
• Multiple buckets in one workflow: build a config string per bucket with Ino S3 Config and wire each where it belongs.

The env var overlay is smart about precedence too - it only fills fields you left empty, so a real value in the JSON isn't clobbered.

The security note

Those credentials travel inside your workflow JSON. That's fine for a local graph, but if you share workflows or expose ComfyUI to a network, the config string goes along for the ride - and it's plaintext. The env-var route keeps secrets out of the graph entirely, which is a real argument for using it.

Installing it

ComfyUI Ino Nodes installs like any custom node pack:

• ComfyUI Manager (easiest): search for "ComfyUI Ino Nodes", install, restart.
• Manual:

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

  Then restart ComfyUI.

Requires inopyutils and a current ComfyUI. The pack is niche - near-zero Reddit footprint - but the S3 tooling is the pack's standout feature, and this config node is its front door.