Amazon Bedrock uses the AWS CLI to list foundation models for a given region and profile. No browser cookies or API tokens beyond standard AWS credentials.
Data sources + fallback order
- AWS CLI (
aws bedrock list-foundation-models)- No fallback — single-source CLI strategy.
Credentials (if applicable)
- Requires AWS CLI installed and configured (
aws configure). - Uses standard AWS credential chain (env vars,
~/.aws/credentials, IAM roles). - Optional
AWS_PROFILEfor named profile selection.
API endpoints / Probe mechanism
- Strategy:
bedrock.cli(kind:.cli) - Command:
aws bedrock list-foundation-models --region <region> --output json - Timeout: 20 seconds
- PATH augmentation: Ensures
/opt/homebrew/bin,/usr/local/bin,/usr/bin,/bin,/usr/sbin,/sbinare on PATH.
Configuration resolution (in order)
Region (required):
- Preferences setting
bedrock.region AWS_REGIONenv varAWS_DEFAULT_REGIONenv var
Profile (optional):
- Preferences setting
bedrock.profile AWS_PROFILEenv var
Model filter (optional, client-side filtering):
- Preferences setting
bedrock.modelID BEDROCK_MODEL_IDenv var
When a model filter is set, results are filtered client-side by matching the filter string (case-insensitive) against modelId, modelName, and providerName.
Parsing + mapping
- AWS CLI returns JSON with
modelSummaries[], each containingmodelId,modelName,providerName. - Snapshot shows model count, region, profile (if set), filter (if set), and up to 3 model IDs.
- No quota/rate-limit windows —
usedPercentis always 0,hasKnownLimitis false. - Primary
RateWindowlabel: “Foundation models”. - Supports model breakdown via
supportsModelBreakdown: true.
Key files
Sources/RunicCore/Providers/Bedrock/BedrockProviderDescriptor.swiftSources/RunicCore/Providers/Bedrock/BedrockUsageFetcher.swift
Read the source ↗ Checked against Runic 2.13.5 · 9730f91