feat: bedrock vpc endpoints support

[TejasGhatte]

Summary

Adds support for routing AWS Bedrock traffic through interface VPC endpoints (AWS PrivateLink), allowing deployments where Bedrock services are accessed over private networking rather than the public regional endpoints. Each AWS endpoint service Bifrost dials (bedrock-runtime, bedrock, bedrock-mantle, bedrock-agent-runtime, s3) can be independently overridden with a VPC endpoint DNS name per key config.

Changes

• Introduced BedrockEndpoints schema type holding per-service VPC endpoint host overrides for both BedrockKeyConfig and BedrockMantleKeyConfig.
• Added resolveBedrockHost utility that returns the configured VPC endpoint host when set, falling back to the public regional hostname. Mantle is handled as a special case since its public host lives under api.aws rather than amazonaws.com.
• Added bedrockEndpoints helper to safely extract endpoint config from a potentially nil BedrockKeyConfig.
• Replaced all hardcoded fmt.Sprintf("https://bedrock-runtime.%s.amazonaws.com/...") style URL construction across bedrock.go, mantle.go, and bedrockmantle.go with calls to resolveBedrockHost, covering inference, streaming, agent runtime, control plane, S3 file operations, and batch job endpoints.
• Updated mantleOpenAIURL, mantleAnthropicURL, and mantleAnthropicCountTokensURL to accept an *schemas.BedrockEndpoints argument so the override propagates through all Mantle call sites.
• Added NormalizeEndpointHost to strip scheme and path from a pasted endpoint value, so users can paste a full URL from the AWS console without breaking URL construction.
• Added bedrockService typed constants (bedrockServiceRuntime, bedrockServiceControlPlane, bedrockServiceMantle, bedrockServiceAgentRuntime, bedrockServiceS3) to make service identity explicit and avoid stringly-typed dispatch.
• Persisted BedrockEndpoints as encrypted JSON columns (bedrock_endpoints_json, bedrock_mantle_endpoints_json) in the config_keys table, with full BeforeSave/AfterFind encrypt/decrypt lifecycle and a database migration.
• Exposed VPC endpoint hosts in the redacted config view (they are network addresses, not credentials).
• Added a collapsible VPC Endpoints section to the Bedrock and Bedrock Mantle key forms in the UI, with per-service fields and a validation rule requiring a DNS name (containing a dot) rather than a bare endpoint ID.
• Updated config.schema.json with the endpoints object for both Bedrock and Bedrock Mantle key configs.
• Added vpcendpoints_test.go covering default host resolution, per-service override isolation, host normalization edge cases, and SigV4 signing correctness with a VPC endpoint host. Updated existing tests to pass nil endpoints where the new parameter was added.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

# Core/Transports
go test ./core/providers/bedrock/... ./core/providers/bedrockmantle/... ./framework/configstore/...

# UI
cd ui
pnpm i
pnpm build

To validate end-to-end, configure a Bedrock key with an endpoints.runtime value set to a VPC endpoint DNS name and confirm inference requests are directed to that host. Confirm that omitting the field falls back to the standard bedrock-runtime.{region}.amazonaws.com host. Confirm SigV4 signing still uses the configured region regardless of which host is dialled.

New config fields (BedrockKeyConfig.endpoints):

Field	AWS endpoint service	Default public host
runtime	bedrock-runtime	bedrock-runtime.{region}.amazonaws.com
control_plane	bedrock	bedrock.{region}.amazonaws.com
mantle	bedrock-mantle	bedrock-mantle.{region}.api.aws
agent_runtime	bedrock-agent-runtime	bedrock-agent-runtime.{region}.amazonaws.com
s3	s3	s3.{region}.amazonaws.com

Values accept the full DNS name from the VPC console (e.g. vpce-0abc123-x1y2z3.bedrock-runtime.eu-west-2.vpce.amazonaws.com), a URL with scheme, or a URL with a trailing path — all are normalized to a bare host.

Breaking changes

• Yes
• No

Security considerations

VPC endpoint hosts are stored encrypted at rest alongside other key config. They are surfaced in plaintext in the redacted config view because they are network addresses rather than credentials. SigV4 signing is unaffected: the credential scope continues to use the configured region, not the hostname, so a VPC endpoint host does not alter the signature scope.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added optional AWS PrivateLink endpoint configuration for Bedrock services.
  • Added endpoint settings to Bedrock and Bedrock Mantle credential forms, with hostname validation.
  • Added support for runtime, control plane, Mantle, agent runtime, and S3 endpoints.
• Improvements
  • Bedrock requests now honor configured endpoints while retaining default regional routing.
  • Endpoint settings are securely persisted and restored with credentials.
• Bug Fixes
  • Corrected Mantle URL handling across supported requests.

Walkthrough

Bedrock and Bedrock Mantle now support configurable AWS PrivateLink endpoint hosts. The configuration flows through validation, UI forms, encrypted persistence, host resolution, request routing, and tests.

Changes

Bedrock VPC endpoint support

Layer / File(s)	Summary
Endpoint contracts and configuration UI core/schemas/account.go, transports/config.schema.json, ui/lib/types/*, ui/lib/schemas/providerForm.ts, ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx, helm-charts/bifrost/*	Adds service-specific endpoint fields for Bedrock and Bedrock Mantle. The UI and deployment schemas validate and expose endpoint configuration.
Endpoint persistence and redaction framework/configstore/...	Adds migration, encrypted JSON persistence, restore and clear behavior, round-trip tests, and redacted configuration support.
Bedrock host resolution and request routing core/providers/bedrock/types.go, core/providers/bedrock/utils.go, core/providers/bedrock/bedrock.go	Resolves configured or regional hosts for runtime, agent-runtime, control-plane, Mantle, S3, and batch requests. Existing signing remains unchanged.
Mantle endpoint routing core/providers/bedrock/mantle.go, core/providers/bedrockmantle/*	Uses configured Mantle hosts for OpenAI-compatible, Anthropic, streaming, Responses, model-listing, and count-tokens requests.
Endpoint resolution and persistence validation core/providers/bedrock/*_test.go, framework/configstore/tables/encryption_test.go	Tests defaults, per-service overrides, normalization, Mantle URLs, SigV4 signing, encrypted persistence, and endpoint removal.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant ProviderForm
  participant ConfigStore
  participant BedrockProvider
  participant AWSPrivateLink
  ProviderForm->>ConfigStore: save endpoint host configuration
  ConfigStore->>BedrockProvider: restore endpoint configuration
  BedrockProvider->>AWSPrivateLink: send signed request to resolved host

Loading

Suggested reviewers: akshaydeo, pratham-mishra04

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 70.83% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely identifies the main change: support for AWS Bedrock VPC endpoints.
Description check	✅ Passed	The description covers the required sections, explains the implementation and testing steps, and documents security, configuration, and breaking-change considerations.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 08-06-feat_bedrock_vpc_endpoints_support

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Trivy (0.72.0)

Trivy execution failed: 2026-08-11T15:34:27Z FATAL Fatal error run error: fs scan error: scan error: scan failed: failed analysis: post analysis error: post analysis error: cloudformation scan error: fs filter error: fs filter error: walk error range error: stat core/.golangci.yml: no such file or directory: range error: stat core/.golangci.yml: no such file or directory

---

_{Comment @coderabbitai help to get the list of available commands.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

tejas ghatte seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[TejasGhatte]

• feat: bedrock vpc endpoints support #6064 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (5)

ui/lib/types/schemas.ts (1)

220-220: 🗄️ Data Integrity & Integration | 🔵 Trivial

bedrockMantleKeyConfigSchema.endpoints accepts fields Mantle ignores.

bedrockMantleKeyConfigSchema reuses the full bedrockEndpointsSchema, so runtime, control_plane, and agent_runtime pass validation for a Mantle key even though only mantle has any effect downstream. Restrict the Mantle schema to the mantle field only, or add a .refine() that rejects the other fields for this config.

See the consolidated comment for the paired finding in core/schemas/account.go.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/lib/types/schemas.ts` at line 220, Update bedrockMantleKeyConfigSchema so
its endpoints configuration accepts only the mantle field and rejects runtime,
control_plane, and agent_runtime; do not reuse the unrestricted
bedrockEndpointsSchema for this Mantle-specific config.

Source: Path instructions

core/schemas/account.go (2)

1-1: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Mantle endpoint config accepts fields it never uses. BedrockMantleKeyConfig.Endpoints and the paired Zod schema both validate against the full BedrockEndpoints/bedrockEndpointsSchema shape (runtime, control_plane, mantle, agent_runtime, s3), but the Mantle host-resolution path (mantleHost in core/providers/bedrockmantle/bedrockmantle.go) only reads the mantle field, and the referenced config-schema documentation states Mantle keys support only endpoints.mantle. The UI form already restricts the Mantle section to a single field, but a client calling the API directly (or a config.json sync) can set the other four fields with no validation error, and they will be silently persisted and ignored.

• core/schemas/account.go#L784-786: narrow BedrockMantleKeyConfig.Endpoints to a Mantle-only type, or add explicit validation elsewhere in the Go path that rejects non-mantle fields for this config.
• ui/lib/types/schemas.ts#L220-220: restrict bedrockMantleKeyConfigSchema.endpoints to a mantle-only schema (or add a .refine() rejecting the other fields) instead of reusing bedrockEndpointsSchema as-is.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@core/schemas/account.go` at line 1, Restrict Mantle endpoint validation to
the supported mantle field only. Update BedrockMantleKeyConfig.Endpoints in the
Go schemas and bedrockMantleKeyConfigSchema in the UI schemas to use
Mantle-specific endpoint shapes, rejecting runtime, control_plane,
agent_runtime, and s3 fields while preserving mantle host resolution.

Source: Path instructions

---

784-786: 🗄️ Data Integrity & Integration | 🔵 Trivial

BedrockMantleKeyConfig.Endpoints accepts fields that Mantle never uses.

BedrockMantleKeyConfig.Endpoints reuses the full BedrockEndpoints type, which exposes Runtime, ControlPlane, AgentRuntime, and S3 in addition to Mantle. The Mantle host-resolution path only reads Endpoints.Mantle (see core/providers/bedrockmantle/bedrockmantle.go's mantleHost), so setting any of the other four fields on a Mantle key is silently accepted and has no effect. This diverges from the documented contract that "Bedrock Mantle keys support only endpoints.mantle."

See the consolidated comment for the corresponding schema-side finding.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@core/schemas/account.go` around lines 784 - 786, Change
BedrockMantleKeyConfig.Endpoints to use a Mantle-specific endpoint type that
exposes only the Mantle field, rather than the full BedrockEndpoints type.
Update the schema and any related serialization or validation references so
Bedrock Mantle keys reject Runtime, ControlPlane, AgentRuntime, and S3 while
preserving mantleHost’s existing Endpoints.Mantle resolution.

Source: Path instructions

ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx (1)

64-73: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Collapsible section stays closed even when endpoints are already configured.

VPCEndpointsFormField always starts with open = false. When a user edits an existing key that already has one or more VPC endpoint overrides set, the section stays collapsed by default and hides that fact. Other auth-type selectors in this file (bedrockAuthType, azureAuthType, vertexAuthType) detect existing configuration on edit via a useEffect keyed on form.formState.isDirty/form.getValues(...) and set their initial UI state accordingly. Apply the same pattern here: default open to true when any ${configKey}.endpoints.* field already has a value.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx` around lines 64
- 73, Update VPCEndpointsFormField so its open state is initialized or
synchronized to true when any ${configKey}.endpoints.* field already contains a
value, while remaining closed when no endpoints are configured. Follow the
existing bedrockAuthType, azureAuthType, and vertexAuthType useEffect pattern,
keyed appropriately to form dirtiness and current form values.

ui/lib/schemas/providerForm.ts (1)

165-176: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Restrict the Bedrock Mantle key's endpoints schema to the mantle field only.

BedrockMantleKeyConfigSchema reuses the full BedrockEndpointsSchema (all 5 fields: runtime, control_plane, mantle, agent_runtime, s3). transports/config.schema.json's bedrock_mantle_key_config.endpoints only allows mantle (additionalProperties: false rejects the rest), matching the documented contract that "Bedrock Mantle keys support only endpoints.mantle."

Define a dedicated BedrockMantleEndpointsSchema with only the mantle field, and use it here instead of the full BedrockEndpointsSchema, so the UI validator matches the authoritative schema and does not accept fields that are meaningless for a Mantle key.

♻️ Proposed fix

+const BedrockMantleEndpointsSchema = z.object({
+	mantle: VPCEndpointHostSchema,
+});
+
 const BedrockMantleKeyConfigSchema = z
 	.object({
 		access_key: z.string(),
 		secret_key: z.string(),
 		session_token: z.string().optional(),
 		region: z.string().min(1, "Region is required for Bedrock Mantle keys"),
 		role_arn: z.string().optional(),
 		external_id: z.string().optional(),
 		session_name: z.string().optional(),
 		project_id: z.string().optional(),
-		endpoints: BedrockEndpointsSchema.optional(),
+		endpoints: BedrockMantleEndpointsSchema.optional(),
 	})

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ui/lib/schemas/providerForm.ts` around lines 165 - 176, Define a dedicated
BedrockMantleEndpointsSchema containing only the mantle endpoint field, then
update BedrockMantleKeyConfigSchema to use it instead of BedrockEndpointsSchema.
Preserve the existing optional endpoints behavior while rejecting runtime,
control_plane, agent_runtime, and s3 fields.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx`:
- Around line 76-85: Replace FormLabel and FormDescription in the VPC Endpoints
section within the CollapsibleTrigger with plain p elements, preserving the
existing text and styling as appropriate. Do not use form-field context
components there, so undefined field metadata cannot generate invalid htmlFor or
id attributes.

---

Nitpick comments:
In `@core/schemas/account.go`:
- Line 1: Restrict Mantle endpoint validation to the supported mantle field
only. Update BedrockMantleKeyConfig.Endpoints in the Go schemas and
bedrockMantleKeyConfigSchema in the UI schemas to use Mantle-specific endpoint
shapes, rejecting runtime, control_plane, agent_runtime, and s3 fields while
preserving mantle host resolution.
- Around line 784-786: Change BedrockMantleKeyConfig.Endpoints to use a
Mantle-specific endpoint type that exposes only the Mantle field, rather than
the full BedrockEndpoints type. Update the schema and any related serialization
or validation references so Bedrock Mantle keys reject Runtime, ControlPlane,
AgentRuntime, and S3 while preserving mantleHost’s existing Endpoints.Mantle
resolution.

In `@ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx`:
- Around line 64-73: Update VPCEndpointsFormField so its open state is
initialized or synchronized to true when any ${configKey}.endpoints.* field
already contains a value, while remaining closed when no endpoints are
configured. Follow the existing bedrockAuthType, azureAuthType, and
vertexAuthType useEffect pattern, keyed appropriately to form dirtiness and
current form values.

In `@ui/lib/schemas/providerForm.ts`:
- Around line 165-176: Define a dedicated BedrockMantleEndpointsSchema
containing only the mantle endpoint field, then update
BedrockMantleKeyConfigSchema to use it instead of BedrockEndpointsSchema.
Preserve the existing optional endpoints behavior while rejecting runtime,
control_plane, agent_runtime, and s3 fields.

In `@ui/lib/types/schemas.ts`:
- Line 220: Update bedrockMantleKeyConfigSchema so its endpoints configuration
accepts only the mantle field and rejects runtime, control_plane, and
agent_runtime; do not reuse the unrestricted bedrockEndpointsSchema for this
Mantle-specific config.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 00d6e434-0240-45a9-b284-861f41f42c9b

📥 Commits

Reviewing files that changed from the base of the PR and between c01a0a2 and d0b4dfe.

📒 Files selected for processing (20)

• core/providers/bedrock/bedrock.go
• core/providers/bedrock/mantle.go
• core/providers/bedrock/mantle_test.go
• core/providers/bedrock/types.go
• core/providers/bedrock/utils.go
• core/providers/bedrock/vpcendpoints_test.go
• core/providers/bedrockmantle/bedrockmantle.go
• core/providers/bedrockmantle/counttokens.go
• core/providers/bedrockmantle/counttokens_test.go
• core/schemas/account.go
• framework/configstore/clientconfig.go
• framework/configstore/migrations.go
• framework/configstore/rdb.go
• framework/configstore/tables/encryption_test.go
• framework/configstore/tables/key.go
• transports/config.schema.json
• ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx
• ui/lib/schemas/providerForm.ts
• ui/lib/types/config.ts
• ui/lib/types/schemas.ts

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@helm-charts/bifrost/values.schema.json`:
- Around line 5501-5507: Update both S3 endpoint schema copies to validate
literal hosts with the required `bucket.` prefix while continuing to accept
`env.<NAME>` references. Replace the current period-only pattern on the s3
property in each copy, preserving the existing description and
additionalProperties behavior.
- Around line 6460-6463: Update the virtual-key Bedrock configuration schema
containing the endpoints property to require region, matching the standard
bedrock_key_config contract. Add region to that configuration’s required fields
so endpoint overrides cannot pass Helm validation without a signing region.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5b695941-ae89-4480-9f01-a5bf7357b7c1

📥 Commits

Reviewing files that changed from the base of the PR and between d0b4dfe and 62a939e.

📒 Files selected for processing (5)

• core/schemas/account.go
• helm-charts/bifrost/values.schema.json
• helm-charts/bifrost/values.yaml
• transports/config.schema.json
• ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx

🚧 Files skipped from review as they are similar to previous changes (3)

• transports/config.schema.json
• ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx
• core/schemas/account.go

[akshaydeo]

Merge activity

• Aug 11, 5:28 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 11, 5:29 PM UTC: @akshaydeo merged this pull request with Graphite.