Use this topic to connect Anthropic Claude models via Amazon Bedrock as a Bring Your Own Model (BYOM) for Cribl AI. This page covers:

• What you need from the Anthropic via Amazon Bedrock side.
• How to fill in each step of the Cribl configuration wizard.

For the generic wizard flow, prerequisites, and how to edit or delete a configured provider, see Configure Custom AI Providers.

Prerequisites ​

In addition to the general prerequisites, you need:

• An AWS account with Amazon Bedrock enabled in at least one Region.
• Access to the specific Anthropic Claude models that Cribl requires (see Required Model IDs below).
• An API key that your Organization exposes for Anthropic via Bedrock access (often via an internal API gateway or proxy).
• On-prem only: Network connectivity from the Leader to the endpoint your Organization uses for Anthropic via Bedrock (public internet, VPC endpoint, or corporate proxy).

Required Model IDs ​

Cribl AI agents use one model per tier. The wizard pre-fills suggested defaults and accepts only supported models. The model IDs in the following tables use the us. inference profile prefix. To use another geography, see Use Region-Prefixed Model IDs.

Suggested defaults:

All supported models:

Assign each model to a tier listed in Available Tiers. For example, assign Claude Opus 4.8 only to the Deep tier. Filling a tier with an inappropriate model can degrade the performance and accuracy of Cribl AI features.

Make sure each model you assign is enabled in your AWS Bedrock account under Model access before saving. If you need to serve multiple tiers from a smaller set of deployments, you have two options:

• Proxy remapping: Use a proxy (such as LiteLLM) to map incoming model names to available models.
• API gateway aliasing: Configure your API gateway to translate model IDs before forwarding to your Bedrock deployment.

For details on model categories and token limits, see Model IDs and Feature Routing.

Use Region-Prefixed Model IDs ​

The first segment of a Bedrock model ID, such as us in us.anthropic.claude-opus-4-8, is the geography of the cross-Region inference profile. You can enter any supported model with a different geographic prefix. For example, enter au.anthropic.claude-opus-4-8 instead of us.anthropic.claude-opus-4-8 to use the model’s Australia cross-Region inference profile. Cribl matches the rest of the ID against the supported models in the preceding tables, so a regional ID is valid when its model is supported, regardless of prefix.

Note the following:

• The ID must start with a geography prefix. An ID such as anthropic.claude-opus-4-8, with no prefix, is rejected.
• This applies only to AWS Bedrock. Microsoft Foundry and Google Gemini require exact model IDs.
• Cribl does not check which inference profiles AWS offers in your Region. Confirm in the AWS Bedrock console that each profile exists and that model access is enabled for it.
• Cribl does not fail over to another Region or inference profile if a request fails.
• A regional ID uses the same token limit as the equivalent supported model. See Token Limits.

When you select an AWS Region in Step 2, the wizard pre-fills the suggested defaults with the prefix for that Region:

The wizard changes only the suggested defaults. IDs that you enter yourself are never rewritten. The wizard pre-fills the defaults only when you add a provider. When you edit a provider, your saved model IDs remain unchanged.

Step 1: Select the Provider Type ​

Navigate to your AI Settings and open the configuration wizard:

1. Select Use Custom AI Provider.
2. Select the AWS Bedrock tile. This provider is selected by default.
3. Select Continue.

Step 2: Enter Connection Details ​

Provide the credentials Cribl needs to reach your Bedrock deployment.

• ID: Enter a short, unique identifier (for example, anthropic-bedrock-prod). Avoid putting secrets or keys in this field.
• Description: Enter a human-readable label for the provider card (for example, Anthropic Claude via Amazon Bedrock - us-east-1). This field is optional.
• API Key: Paste the API key or bearer token provided by your AWS team.
• AWS Region (optional): Select the AWS Region to use for Bedrock requests (for example, ap-southeast-2). The models and inference profiles that you assign must be available in this Region. Cribl uses this Region for the connection test in Step 3 and for all AI requests to Bedrock. The selected Region also determines the prefix of the suggested model IDs. If you leave it blank, Cribl uses the Cribl Workspace Region, or us-west-2 when no default Region is set. Cribl rejects a value that is not a valid AWS Region when you save.

Depending on your environment setup, this key is one of the following:

• Amazon Bedrock API key: A native AWS bearer token. This is the modern, streamlined way to access Bedrock without managing IAM users.
• Gateway/proxy key: A custom token generated by an internal API gateway (such as a Mulesoft or Apigee layer) that fronts your AWS environment.

If you are unsure which key to use, ask the team that manages AI providers and Bedrock access to issue or confirm the correct key for your deployment.

When editing an existing provider, leave the API Key field blank to keep the stored key, or enter a new value to replace it. See Edit an Existing Custom AI Provider.

Select Continue.

Step 3: Assign Models to Tiers and Test ​

Assign models to each tier. For AWS Bedrock, the wizard pre-fills the following defaults: Claude Haiku 4.5 (Fast), Claude Sonnet 4.6 (Balanced), Claude Opus 4.8 (Deep). If you selected an AWS Region in Step 2, the pre-filled IDs use that Region’s prefix. Enter model IDs as text. For the full list of supported models, see Required Model IDs.

The Deep tier supports multiple model IDs, with the first model in the list serving as the system default. While most features exclusively use this first model, Cribl Search investigations allow you to switch between any listed models via a drop-down menu.

1. For Fast and Balanced, accept the pre-filled default or enter a different supported model ID.
2. For Deep, accept the pre-filled default or add additional model IDs.
3. Select Test and Save.

Cribl runs a connectivity check for each assigned model, sending a basic request through your configured endpoint to confirm that the model is reachable and responds. This does not test model performance or feature compatibility.

• A results panel shows how many models passed and failed.
• If any test fails, verify that the API key is valid, that the AWS Region is correct, and that the corresponding Claude models are enabled and accessible in your Bedrock account in that Region. Select Retry to test again.
• When all models pass, the configuration is saved automatically.

After you save:

• A Custom AI provider card appears at the top of AI Settings, showing your ID, description, Anthropic via Amazon Bedrock as the provider type, and the number of configured models.
• Supported Cribl AI capabilities in that Workspace begin using Anthropic via Bedrock as their AI backend.

Verify Cribl AI Behavior ​

To confirm that Anthropic via Bedrock is correctly configured:

1. In AI Settings, confirm that the Custom AI provider card lists Anthropic via Amazon Bedrock.
2. Use a Cribl AI capability that supports custom providers (for example, the KQL assistant or Git commit message suggestions).
3. Verify that:
   • Requests succeed without provider-related errors.
   • Latency and behavior align with your expectations for the Anthropic models and Regions you use.

If you see failures or unexpected behavior:

• Select the gear (⚙️) on the provider card and select Edit to reopen the wizard, then use Test and Save to review error details.
• Confirm with your AWS/AI team that:
  • The key is valid and not rate-limited.
  • The Anthropic Claude models you assigned are enabled and accessible in the intended Region(s).
  • For on-prem deployments: Network rules allow the Leader to reach the Anthropic/Bedrock gateway or endpoint.

Change or Stop Using Anthropic via Bedrock ​

• To update the provider (for example, after a key rotation or model change), see Edit an Existing Custom AI Provider.
• To stop using Anthropic via Bedrock, see Delete a Custom AI Provider.
• To use this provider again after deletion, follow the steps in this topic to reopen the wizard and reconfigure.