Kimi Code CLI v2.7.0 Adds Native Amazon Bedrock Provider, Streamlining AWS Integration
The latest Kimi Code CLI introduces a native 'bedrock' provider, allowing direct integration with Amazon Bedrock models using AWS standard credential chains, removing the need for separate API key management.
What changed?
Kimi Code CLI v2.7.0 introduces a native 'bedrock' provider. This update lets users connect directly to Amazon Bedrock hosted models like Kimi K3.1 Pro using standard AWS credential chains, including named profiles and single sign-on (SSO). Previously, users had to configure a generic provider, supply regional endpoints, and manage separate Amazon Bedrock API keys. Now, authentication leverages AWS credentials and generates short-lived bearer tokens automatically, reducing manual credential handling.

Why does it matter to an everyday developer?
This change simplifies workflow and improves security. Developers can authenticate through standard AWS mechanisms—typically already in use in their organizations—so they no longer need to manage additional Bedrock API keys. It also aligns with AWS best practices by favoring short-term credentials and least-privilege IAM roles. Integration now supports seamless use of named AWS CLI profiles or SSO sessions. The CLI also supports streaming model responses and client-side tool-calling for coding scenarios, without requiring new credential workflows.
What can the developer do now?
- Upgrade to Kimi Code CLI v2.7.0 or later.
- Ensure you have AWS credentials (via default chain, named profile, or SSO) with sufficient permissions to access the desired Bedrock models and inference profiles.
- Optionally, configure or select a named AWS CLI profile if your organization uses roles or SSO.
- Update your `~/.kimi-code/config.toml` to use the new 'bedrock' provider, specifying your region and, if necessary, your named AWS profile.
