---
date: 2026-04-13
title: Amazon Bedrock API Keys
description: Use Amazon Bedrock API keys to connect Bedrock models to Langfuse for Playground, LLM-as-a-judge evaluations, and prompt experiments.
author: tobiaswochinger
ogImage: /images/changelog/2026-04-13-bedrock-api-keys.png
canonical: /docs/administration/llm-connection
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/administration/llm-connection) and the API/SDK reference (https://api.reference.langfuse.com).

Langfuse now supports Amazon Bedrock API keys for LLM Connections in addition to AWS Access Keys. This makes it easier to use Bedrock models in the Langfuse Playground, LLM-as-a-judge evaluations, and prompt experiments with the credential type that best fits your AWS setup.

For teams already building on AWS, this shortens the path from "we have Bedrock access" to "we can test prompts, run evals, and compare experiment results in Langfuse." Create a Bedrock API key in AWS, add it to Langfuse as an LLM Connection, and use your Bedrock models across the evaluation workflow.

For Langfuse LLM Connections, we recommend long-term Bedrock API keys to avoid interruptions from expired short-term keys. See the [Amazon Bedrock API keys documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html) for setup, permissions, and key management guidance.

## What's New [#whats-new]

- Add Amazon Bedrock API keys as bearer tokens for LLM Connections
- Keep existing AWS credential-based Bedrock setups working while adopting the simpler API key flow where it fits

## Get started [#get-started]

- [LLM Connections](/docs/administration/llm-connection)
- [Amazon Bedrock API Keys](https://docs.aws.amazon.com/bedrock/latest/userguide/api-keys.html)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-04-13-amazon-bedrock-api-keys.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.