docs: update Bedrock and Vertex setup

[chrarnoldus]

What changed

Update the Bedrock and Vertex provider pages to match the VS Code credential setup introduced in #13100. The docs now list the exact access-key and service-account fields, explain credential storage, and distinguish the VS Code flows from CLI authentication.

Also document Bedrock bearer-token and named-profile CLI setup, which were missing from the existing page.

Why

The Vertex page still directed VS Code users to Application Default Credentials, and the Bedrock page still described only the AWS credential chain. Those instructions no longer matched the provider dialogs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs (docs-staging)	Ready	Preview	Aug 13, 2026 1:47pm

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Both previously reported findings (final dialog step should read Submit, not Connect) were fixed in bf75822 and re-verified at HEAD. The incremental change touches only those two lines and introduces no new issues.

Files Reviewed (2 files)

• packages/kilo-docs/pages/ai-providers/bedrock.md
• packages/kilo-docs/pages/ai-providers/vertex.md

Previous Review Summary (commit 6ee0872)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit 6ee0872)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
packages/kilo-docs/pages/ai-providers/bedrock.md	47	Final step says "Select Connect" but the dialog's submit button is labeled Submit
packages/kilo-docs/pages/ai-providers/vertex.md	31	Final step says "Select Connect" but the dialog's submit button is labeled Submit

Files Reviewed (2 files)

• packages/kilo-docs/pages/ai-providers/bedrock.md - 1 issue
• packages/kilo-docs/pages/ai-providers/vertex.md - 1 issue

All other claims verified against the implementation from #13100: dialog field labels ("Service-account JSON", "Google Cloud project ID", "Vertex AI location", AWS access key/secret/session token/region), credential-store storage (not kilo.json), visible JSON while editing, AWS_BEARER_TOKEN_BEDROCK and AWS_PROFILE CLI support, and GOOGLE_CLOUD_PROJECT / GOOGLE_CLOUD_LOCATION env vars. Markdoc callout syntax is valid; no images added, so the markdown-image-format rule does not apply.

Fix these issues in Kilo Cloud

---

_{Reviewed by kimi-k3 · Input: 85.1K · Output: 2.4K · Cached: 121.3K}

_{Review guidance: REVIEW.md from base branch main}