Fill gaps from assistant conversations: S3 403 and ComfyUI-to-API invocation - #777
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: S3 403 and ComfyUI-to-API invocation#777mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Close two recurring assistant-conversation gaps: S3-compatible API
403 Forbiddentroubleshooting, and how to actually invoke a ComfyUI workflow after deploying via ComfyUI-to-API.Changes
storage/s3-api.mdx: added a "403 Forbidden on HeadObject, GetObject, or CopyObject" accordion under Known issues. Covers the credential/user-ID mismatch, cross-account access, region/endpoint mismatch,aws s3 syncintermittency, and the split between auth-level (all ops fail) and object-level (lsworks,cp/HeadObjectfails) causes.community-solutions/comfyui-to-api/overview.mdx: added a "Step 7: Send requests to your endpoint" section clarifying that ComfyUI-to-API only generates a Dockerfile (dependency analysis) and does not bake the workflow into the worker. Points at the existing Serverless ComfyUI tutorial for the full request body and at Send API requests for auth/response details. Added Send API requests to Related documentation.Context
Both edits target unanswered assistant threads in the 2026-08-03 → 2026-08-10 window where existing pages had the underlying facts but weren't structured to answer the recurring question directly.