AWS Bedrock Claude API

If you already run on AWS, this is how you call Anthropic's Claude from ComfyUI without a separate Anthropic account - you go through Amazon Bedrock, AWS's managed model service, using your AWS credentials. It's a connection node: it authenticates against Bedrock and hands out an LLM_API handle for the Chat and Completion nodes. Functionally it's the Bedrock-flavored sibling of the Gemini API node - same role in the graph, different provider.

Who's this for? People whose billing, quotas, and compliance already live in AWS, and who'd rather keep Claude access inside that boundary than manage another vendor key. If that's not you, a direct Claude or Gemini key is simpler.

How it fits together

Same three-node LLM pattern: this API node for credentials, an LLM API Config for the model and settings, and an LLM Chat or LLM Completion to run it. This node's job is purely the AWS handshake.

The inputs and outputs

• aws_access_key_id / aws_secret_access_key (STRING) - your AWS credentials.
• aws_session_token (STRING) - for temporary credentials from AWS STS (assumed roles, SSO). If you're using long-lived keys you may not need it, but the field is there for the token-based flow.
• region - the AWS region to hit (default us-east-1, plus eight others). This matters more than it looks: Bedrock model availability is per-region.
• version - the Bedrock API version, bedrock-2023-05-31.
• llm_api (output) - the handle for the Chat/Completion nodes.

Installing it

ComfyUI Manager → search comfyui-art-venture → install → restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/sipherxyz/comfyui-art-venture

then restart ComfyUI. Pre-installed on comfy.icu. The AWS path relies on the boto3 SDK, pulled in with the pack's requirements.

Common issues

Missing-node red means the pack isn't installed - Manager → "Install Missing Custom Nodes."

The Bedrock-specific traps, because there are a few. Model access isn't automatic: in the AWS console you have to request access to the specific Claude model in Bedrock, per region, before it'll answer - a fresh account has none enabled by default. Region has to match where you enabled the model; asking us-east-1 for a model you only turned on in us-west-2 fails. IAM permissions need to allow bedrock:InvokeModel. If the Chat node throws an auth or access-denied error, walk those three before touching the workflow - nine times out of ten it's an AWS-side config gap, not the node.

And the security note that applies to every credentialed node here: your AWS keys go into node fields, and node fields save into the workflow. Do not share or embed a workflow with live AWS secrets in it - scrub them first. Leaking cloud credentials is a worse day than leaking an LLM key. Prefer short-lived STS session tokens over long-lived keys where you can.