AI models

AWS Bedrock

Use AWS credentials for Bedrock text, embeddings, image generation, vision, structured output, and direct model invocation.

01 / Workflows

What you can automate.

AWS credentials are registered as a connection type for Bedrock and other AWS services. Bedrock capabilities handle SigV4 authentication directly instead of using a generic HTTP extractor.

  1. Run Bedrock text completion and structured-output workflows.
  2. Generate embeddings and image outputs with Bedrock models.
  3. Invoke a specific Bedrock model or list available foundation models.

02 / Capabilities

What it covers.

The full reference, with connection types, is in the AWS Bedrock docs.

Capabilities

  • Text completion
  • Embeddings
  • Image generation
  • Structured output
  • Vision to text
  • Vision to image
  • Invoke model
  • List models

Data handled

  • Prompts
  • Images
  • Embeddings
  • Model responses

03 / Availability

In every edition.

AWS Bedrock is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans

  • Open-source engineAGPL-3.0, run and operate it yourself.Included
  • CloudWe host and manage your instance.Included
  • EnterpriseYour cloud or on-premises, supported by our team.Included

04 / Questions

Common questions.

Is AWS Bedrock included in my plan?

Yes. AWS Bedrock is a standard integration, included in Cloud, Enterprise and the open-source engine.

How is it set up?

A connection stores the AWS Bedrock credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.

Can a person approve before anything is written?

Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.

More in AI models

Put AWS Bedrock to work.

Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.

Discuss your process

All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.