Skip to main content
Technical Preview

Overview

Client-mode REST API connectors for Amazon Bedrock: triage alarms and summarize shift logs with the Converse API, create Titan embeddings with InvokeModel, count tokens, screen text with a guardrail, and list foundation models and inference profiles, all with a Bedrock API key. This is one of the templates in the Amazon Bedrock REST API app (amazon-bedrock). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).

Auth

Amazon Bedrock API key as Authorization: Bearer {value.json.api_key} (long-term ABSK…, short-term bedrock-api-key-…). Hub secret suggested AWS_BEARER_TOKEN_BEDROCK + GET SECRET. Alternative: AWS SigV4 (service bedrock) computed outside the broker, documented in comments. Never commit keys. Auth headers used by the template: Authorization: Bearer {value.json.api_key}.

Template parameters

BASE_ADDRESS default: https://bedrock-runtime.eu-west-1.amazonaws.com.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addConnector (do not include ADD METADATA).

Usage example

Call Converse by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 26, 2026