Skip to content

Context7 Platform -- Up-to-date docs for AI agents

CTX7-2792: Document native AWS Bedrock setup (#3199)

Fahreddin Özcanc4409f9470b5
diff --git a/docs/docs.json b/docs/docs.json
index 57c4357e..159e49a7 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -87,7 +87,8 @@
"enterprise/integrations/github",
"enterprise/integrations/other-git",
"enterprise/integrations/gerrit",
- "enterprise/integrations/confluence"
+ "enterprise/integrations/confluence",
+ "enterprise/integrations/aws-bedrock"
]
},
{
diff --git a/docs/enterprise/changelog.mdx b/docs/enterprise/changelog.mdx
index 3d6fbb8d..d2c2c0b6 100644
--- a/docs/enterprise/changelog.mdx
+++ b/docs/enterprise/changelog.mdx
@@ -3,6 +3,14 @@ title: "Changelog"
description: "Release notes for the Context7 On-Premise image."
---
+<Update label="2026-09-16" description="v1.3.9">
+
+### Added
+
+- Added native AWS Bedrock support for Anthropic Claude inference, Amazon Titan embeddings, reranking, and source-code documentation.
+
+</Update>
+
<Update label="2026-07-24" description="v1.3.0">
### Added
diff --git a/docs/enterprise/deployment/kubernetes.mdx b/docs/enterprise/deployment/kubernetes.mdx
index 5d04c632..d61b7bb6 100644
--- a/docs/enterprise/deployment/kubernetes.mdx
+++ b/docs/enterprise/deployment/kubernetes.mdx
@@ -257,7 +257,8 @@ Context7 requires outbound connectivity to the following:
|---|---|
| `ghcr.io` | Container image pulls (`imagePullPolicy: Always`) |
| `context7.com` | License validation |
-| Your LLM provider (e.g. `api.openai.com`) | AI inference and embeddings |
+| Your LLM provider (for example, `api.openai.com` or the regional AWS Bedrock Runtime endpoint) | AI inference and embeddings |
+| AWS credential endpoints, when using workload credentials | Resolving EKS Pod Identity, IRSA, ECS, or EC2 role credentials for Bedrock |
| `github.com` / `gitlab.com` | Repository cloning |
If you use NetworkPolicies, ensure egress to these endpoints is allowed:
@@ -280,6 +281,8 @@ spec:
For stricter policies, allow egress on port 443 to the specific domains listed above, and ensure egress to `kube-dns` on port 53 (UDP/TCP) is permitted for DNS resolution.
+When using AWS Bedrock, allow the regional Bedrock Runtime endpoint (`bedrock-runtime.<region>.amazonaws.com`) and any endpoint required by your AWS credential provider. For private clusters, you can instead use a Bedrock Runtime interface VPC endpoint and enter its URL in Context7. See [AWS Bedrock](/enterprise/integrations/aws-bedrock) for IAM, credential, region, and PrivateLink configuration.
+
## Operations
### Updating
diff --git a/docs/enterprise/integrations/aws-bedrock.mdx b/docs/enterprise/integrations/aws-bedrock.mdx
new file mode 100644
index 00000000..340f5b3a
--- /dev/null
+++ b/docs/enterprise/integrations/aws-bedrock.mdx
@@ -0,0 +1,104 @@
+---
+title: "AWS Bedrock"
+sidebarTitle: "AWS Bedrock"
+description: "Use Anthropic models and Amazon Titan embeddings through native AWS Bedrock APIs"
+---
+
+Context7 On-Premise can call AWS Bedrock directly for parsing, source-code documentation, reranking, and embeddings. LiteLLM and other OpenAI-compatible proxies are not required.
+
+Native AWS Bedrock support is available in Context7 Enterprise v1.3.9 and later.
+
+## Prerequisites
+
+- Enable access to the Claude and Amazon Titan models you plan to use in the selected AWS Region.
+- Allow `bedrock:InvokeModel` and `bedrock:InvokeModelWithResponseStream` for the models you use. For a [geographic cross-region inference profile](https://docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-inference.html), allow both the inference-profile ARN and the underlying foundation-model ARN in the source Region and every destination Region.
+- Give the Context7 container network access to the regional Bedrock Runtime endpoint.
+
+## Authenticate
+
+A workload IAM role is recommended. Context7 uses the standard AWS SDK credential chain, including environment credentials, web identity, shared profiles, and ECS or EC2 role credentials.
+
+<Tabs>
+ <Tab title="Workload role">
+ Attach an IAM role to the ECS task, EC2 instance, or Kubernetes service account that runs Context7. Leave the **API Key** field blank in Context7.
+ </Tab>
+ <Tab title="Environment credentials">
+ Pass credentials to the container:
+
+ ```yaml
+ environment:
+ AWS_REGION: us-east-1
+ AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
+ AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}
+ AWS_SESSION_TOKEN: ${AWS_SESSION_TOKEN}
+ ```
+
+ Omit `AWS_SESSION_TOKEN` for long-lived credentials.
+ </Tab>
+ <Tab title="Shared AWS profile">
+ The container image sets `HOME=/data/home`, so mount the AWS files there and select the profile:
+
+ ```yaml
+ environment:
+ AWS_PROFILE: context7
+ AWS_REGION: us-east-1
+ volumes:
+ - ~/.aws:/data/home/.aws:ro
+ ```
+
+ A profile that uses `credential_process` also requires its helper executable inside the container image.
+
+ Ensure the mounted files are readable by the UID that runs the container, especially when using Docker `--user` or Kubernetes `runAsUser`.
+ </Tab>
+ <Tab title="Bedrock API key">
+ Paste a Bedrock API key into Context7's **API Key** field, or pass it as `AWS_BEARER_TOKEN_BEDROCK`. The value is used for both Claude and Titan when both providers are set to Bedrock.
+
+ `AWS_BEARER_TOKEN_BEDROCK` takes precedence over the standard AWS credential chain. Remove an expired or revoked value from the container environment to fall back to a workload role or shared profile.
+
+ Console-generated short-term keys expire with the session or after at most 12 hours. A key saved in Context7 stops working when it expires, so use a workload role for unattended production deployments. AWS positions long-term Bedrock API keys for exploration and development rather than production workloads.
+ </Tab>
+</Tabs>
+
+<Warning>
+The AWS credential chain does not skip credentials merely because they are invalid. `AWS_BEARER_TOKEN_BEDROCK` takes precedence over SigV4 authentication, and `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` take precedence over a shared profile. Remove stale environment credentials if a valid role or profile unexpectedly returns `The security token included in the request is invalid`.
+</Warning>
+
+## Configure Context7
+
+<Steps>
+ <Step title="Configure the LLM">
+ In the setup wizard or **Settings → AI & Models**, select **AWS Bedrock**. Enter the raw Bedrock model or inference-profile ID—without an `amazon-bedrock/` prefix—and select its AWS Region.
+
+ For example: `us.anthropic.claude-haiku-4-5-20251001-v1:0`.
+ </Step>
+ <Step title="Configure embeddings">
+ Select **Same as LLM** to use Bedrock embeddings, or select **AWS Bedrock** separately. Use an Amazon Titan model such as `amazon.titan-embed-text-v2:0`.
+
+ The LLM and embedding configurations share one AWS Region. If both use Bedrock, choose models available from the same configured region.
+ </Step>
+ <Step title="Test and verify">
+ Test both connections, save the configuration, and parse a small repository. Query the resulting library to verify that parsing and semantic search both work.
+ </Step>
+</Steps>
+
+<Warning>
+Model IDs prefixed with values such as `us.`, `eu.`, `apac.`, or `global.` are cross-region inference profiles. They can route requests among supported regions. The AWS Region field selects the Bedrock endpoint; it does not constrain a cross-region profile to that single region.
+</Warning>
+
+## Private connectivity
+
+Create the `com.amazonaws.<region>.bedrock-runtime` interface VPC endpoint for AWS PrivateLink. With private DNS enabled, leave Context7's optional **Bedrock endpoint** field blank. Without private DNS, enter the full endpoint URL, such as:
+
+```text
+https://vpce-....bedrock-runtime.us-east-1.vpce.amazonaws.com
+```
+
+The endpoint, configured AWS Region, and selected models must agree. Credential discovery may also need access to STS, container or instance metadata, or another identity endpoint, depending on the authentication method.
+
+<Note>
+An offline Context7 license removes the Context7 Cloud license check, but Bedrock still requires AWS network connectivity. Content sent for parsing, embedding, reranking, or source-code documentation is processed by the selected Bedrock models.
+</Note>
+
+## Changing embedding models
+
+Bedrock indexes are stored separately from existing OpenAI or Gemini vector indexes because their dimensions can differ. After changing the embedding provider or model, refresh the libraries that should be available under the new embedding configuration.
diff --git a/docs/enterprise/on-premise.mdx b/docs/enterprise/on-premise.mdx
index 78419b2e..e145c00b 100644
--- a/docs/enterprise/on-premise.mdx
+++ b/docs/enterprise/on-premise.mdx
@@ -1,10 +1,10 @@
---
title: "On-Premise Deployment"
sidebarTitle: "Getting Started"
-description: "Run the full Context7 stack inside your own infrastructure, so code and documentation never leave your environment"
+description: "Run the Context7 stack inside your infrastructure with your chosen AI and storage services"
---
-Context7 On-Premise lets you run the full Context7 stack inside your own infrastructure. Your code, documentation, and embeddings never leave your environment.
+Context7 On-Premise keeps your repositories, generated documentation, application database, vector store, and MCP server in your infrastructure. Only the content required for parsing, embedding, reranking, or source-code documentation is sent to the AI provider you choose.
## What's Included
@@ -48,7 +48,7 @@ Follow the deployment guide for your platform:
Open `http://localhost:3000` in your browser. On first launch, the setup wizard guides you through configuring:
-1. **AI Provider** - Choose OpenAI, Anthropic, Gemini, or a custom OpenAI-compatible endpoint. Enter your API key and model name.
+1. **AI Provider** - Choose OpenAI, Anthropic, Gemini, AWS Bedrock, or a custom OpenAI-compatible endpoint. Enter the provider credentials and model name.
2. **Embedding Provider** - Use the same provider as your LLM, or configure a separate one for embeddings.
3. **Git Tokens** - Add a GitHub and/or GitLab token for the platforms you use.
@@ -189,10 +189,11 @@ Configured via the **Settings** page in the web UI.
| Setting | Description |
|---|---|
-| LLM Provider | `openai`, `anthropic`, `gemini`, or custom |
-| LLM API Key | API key for your chosen provider |
-| LLM Model | Model name (e.g. `gpt-4o`, `claude-sonnet-4-5`, `gemini-2.5-flash`) |
-| LLM Base URL | Custom OpenAI-compatible endpoint (for local models or proxies) |
+| LLM Provider | `openai`, `anthropic`, `gemini`, `bedrock`, or custom |
+| LLM API Key | API key for your chosen provider; optional for Bedrock with workload credentials |
+| LLM Model | Model name or Bedrock model/inference-profile ID |
+| AWS Region | Region used for Bedrock LLM and embedding requests |
+| Base URL / Bedrock endpoint | Custom OpenAI-compatible endpoint, or an optional Bedrock Runtime endpoint |
#### Examples
@@ -221,10 +222,12 @@ By default, Context7 uses the same provider as your LLM for generating embedding
| Setting | Description |
|---|---|
-| Embedding Provider | `openai` or `gemini` |
-| Embedding API Key | Separate API key for embeddings (falls back to LLM API key) |
-| Embedding Model | Embedding model name (e.g. `text-embedding-3-small`) |
-| Embedding Base URL | Custom embedding endpoint |
+| Embedding Provider | `openai`, `gemini`, `bedrock`, or custom |
+| Embedding API Key | Separate key; inherits the LLM key only when both use the same provider |
+| Embedding Model | Embedding model name, such as `text-embedding-3-small` or `amazon.titan-embed-text-v2:0` |
+| Embedding base URL / Bedrock endpoint | Custom embedding endpoint, or an optional Bedrock Runtime endpoint |
+
+See [AWS Bedrock](/enterprise/integrations/aws-bedrock) for IAM, model, region, and private-network configuration.
### Git Access Tokens