Introducing Kimi K3 on Amazon Bedrock
https://aws.amazon.com/blogs/machine-learning/introducing-kimi-k3-on-amazon-bedrock/📌 2.8兆參數開源模型上線,Kimi K3進駐Amazon Bedrock
TL;DR:Moonshot AI的2.8T參數開源模型Kimi K3登陸Bedrock,支援百萬token與明確prompt快取。
當開源模型的參數規模開始逼近甚至超越部分閉源旗艦模型時,「要不要用開源」已經不再是能力問題,而是部署信任問題。Amazon Bedrock這次把Moonshot AI的Kimi K3納入平臺,某種程度上正是在回應這個問題。
🤔 開源權重模型正在改變AI部署的成本結構
隨著開源模型的智慧與效率快速提升,企業能依工作負載挑選最適合的能力、速度與成本組合。AWS這次上線Kimi K3,延續的是自2025年以來持續在Bedrock擴充開源模型陣容的策略——目前已涵蓋DeepSeek、Google、MiniMax、Mistral AI、Moonshot AI、NVIDIA、OpenAI、Qwen等多家提供者的數十款模型,而Bedrock在2026年陸續補上的tool calling、structured output、reasoning、串流回應,以及Responses與Chat Completions API,都是平臺層級的能力,新加入的開源模型可以直接沿用,不必個別重新對接。
🧩 原生視覺、百萬token context,以及首個支援明確prompt快取的開源模型
根據Moonshot AI的說法,Kimi K3是其目前最強大的模型,也是首個突破2.8兆參數的開源模型。它結合原生視覺(vision)能力與100萬token的context window,並宣稱相較於前代Kimi K2,在scaling效率上有約2.5倍的提升。這些特性讓它適合需要在大型程式碼庫、長文件與圖片間維持長期上下文的長時間coding與知識工作流程。值得一提的是,Kimi K3是Bedrock上第一個支援explicit prompt caching的開源權重模型——當你在多次呼叫間重複使用同一段上下文(例如repository說明、工具定義或參考文件)時,明確標記可重用的prompt前綴,能讓後續請求命中快取,降低回應延遲與輸入token成本。
在資料安全方面,Bedrock上所有開源權重模型都遵循相同原則:資料處理在AWS資料邊界內完成、不會與模型提供者共享、也不會用於訓練底層模型;推論請求永遠啟用zero data retention,zero operator access則確保連AWS自己的維運人員都無法在推論過程中存取你的prompt與回應內容。
🧩 兩種跨區域推論設定檔,以及與OpenCode、Hermes Agent的整合
要試用Kimi K3,最快的方式是打開Bedrock console,進入Test > Playground選擇模型;程式化呼叫則透過bedrock-runtime端點,同時支援OpenAI相容的Responses/Chat Completions API,以及Bedrock自己的Invoke與Converse API。呼叫時需透過跨區域推論設定檔:沒有地區限制需求的話,建議使用global.moonshotai.kimi-k3,它會把每個請求路由到任何支援的商用AWS區域,成本比地理性設定檔低約10%;若有資料落地需求,us.moonshotai.kimi-k3會把處理限定在美國地理範圍內。文中也示範了用OpenAI Python SDK搭配aws-bedrock-token-generator函式庫產生短期bearer token進行驗證,並展示了如何在OpenAI Python API中設定explicit caching。
除了直接呼叫API,Kimi K3也能透過支援Bedrock或OpenAI相容供應商的各類coding agent與框架使用。文中以開源、model-agnostic的coding agent OpenCode為例,說明如何在opencode.json設定檔中配置amazon-bedrock供應商(底層走Converse API),設定完成後用/models指令切換到global.moonshotai.kimi-k3即可開始開發;另一個例子是通用生產力助手Hermes Agent,它可透過桌面應用、常見通訊軟體或終端機使用,原生支援Bedrock上的模型,適合deep research與任務自動化等場景。
⚠️ 細節仍有待補齊之處
文中提到Hermes目前若要在多組AWS憑證環境下運作,需要設定AWS_PROFILE環境變數或使用預設profile,尚未支援在設定檔中直接指定AWS profile,這點還有一個開放中的issue在追蹤後續支援進度。至於Kimi K3實際效能表現,除了Moonshot AI自身宣稱的2.5倍scaling效率提升外,本文並未提供具體的benchmark分數,讀者評估時仍需自行測試驗證。
🎯 實務啟示
對已經在使用Bedrock、又想嘗試超大規模開源模型的團隊來說,Kimi K3的吸引力在於「用開源模型的成本彈性,配上受管服務的資料邊界保證」——不需要自己承擔模型權重的部署與維運,也不用因為使用開源模型就放寬資料安全的要求。若你的工作流程本身就需要長文本與圖片混合輸入,或已經在跨多次呼叫重用相同上下文,explicit prompt caching能直接反映在成本與延遲上,值得優先評估。
🔗 來源
- 標題:Introducing Kimi K3 on Amazon Bedrock
- 作者/機構:Alex Thewsey
- 連結:https://aws.amazon.com/blogs/machine-learning/introducing-kimi-k3-on-amazon-bedrock/
#AmazonBedrock #KimiK3 #MoonshotAI #OpenWeightModels #LLM #AWS #PromptCaching #AICoding #CloudAI #GenerativeAI
原始資料 AWS ML · 收集於 2026-09-18
摘要原文
Open-weight models are changing the economics of building and deploying AI at scale. Rapid gains in intelligence and efficiency mean companies can match each workload with the right balance of capability, speed, and cost. AWS is building for a future in which organizations can adopt open-weight innovation with the reliability and security required for production. Today, Kimi K3 from Moonshot AI is available on Amazon Bedrock, giving you a powerful new option for coding and knowledge work. According to Moonshot AI, Kimi K3 is its most capable model and the first open model to reach 2.8 trillion parameters. It combines native vision capabilities with a 1-million-token context window and delivers an approximate 2.5x improvement in scaling efficiency over Kimi K2. These advances make Kimi K3 well suited to long-running coding and knowledge workflows that require sustained context across large repositories, documents, and images. Kimi K3 is the first open-weight model on Amazon Bedrock to support explicit prompt caching , helping you reduce latency and input costs when reusing context across model calls. The launch of Kimi K3 reflects the sustained investment by AWS in open-weight models on Amazon Bedrock. Since 2025, Bedrock has added dozens of open-weight models from providers including DeepSeek, Google, MiniMax, Mistral AI, Moonshot AI, NVIDIA, OpenAI, and Qwen. Supporting this expanding selection is continued advancement of the inference technology that serves these models at scale. In 2026, Bedrock added support for tool calling, structured output, reasoning, response streaming, and the Responses and Chat Completions APIs. Because these are platform capabilities rather than per-model integrations, new open-weight models can benefit from them as they become available on Amazon Bedrock. As with all open-weight models on Amazon Bedrock, you can adopt Kimi K3 without changing your security posture. Your data is processed within the AWS data boundary, is not shared with the model provider, and is not used to train the underlying model. Zero data retention is always enabled for inference requests, while zero operator access prevents even AWS operators from accessing your prompts and completions during inference. Together, these protections let you use open-weight models with confidence while maintaining control of your data. To try Kimi K3, open the Amazon Bedrock console , go to Test > Playground , and select Kimi K3 as the model. From there, you can test your first prompt. Programmatically, you can call the model using the bedrock-runtime endpoint, which supports the OpenAI-compatible Responses and Chat Completions APIs, and the Amazon Bedrock Invoke and Converse API APIs. You can invoke Kimi K3 through a cross-Region inference profile. For workloads without regional restrictions we recommend using the global profile, global.moonshotai.kimi-k3 , which routes each request to any supported commercial AWS Region worldwide. Global cross-Region inference costs approximately 10% less than a geographic profile. The US geographic profile, us.moonshotai.kimi-k3 , keeps processing within the US geography for data residency requirements. Here is a quick example that uses the OpenAI SDK and the aws-bedrock-token-generator library for Python to generate short-term bearer tokens for authentication to Amazon Bedrock. Long-running coding and knowledge workflows often resend stable context, such as repository instructions, tool definitions, or reference documents. With explicit prompt caching , you identify reusable prompt prefixes so later requests can use cached content. When a request matches a cached prefix, Amazon Bedrock can reduce response latency and input token costs. Caching for Kimi K3 on Amazon Bedrock: With the OpenAI Python API, explicit caching can be configured as shown in the following example: You can explore the Moonshot AI on AWS samples repository for more examples. In addition to using the APIs directly, you can use Kimi K3 through the wide range of coding assistants, personal agents, and agentic frameworks that support Amazon Bedrock specifically, or OpenAI-compatible model providers in general. There are several popular coding agents available to builders today, so consider OpenCode as an example. OpenCode is open source, model agnostic, and has a native amazon-bedrock model provider , which uses the Converse API. To get started, you can configure the amazon-bedrock provider either in your user-level or project-level opencode.json configuration files as shown in the OpenCode documentation . With the provider configured, OpenCode will automatically detect available Amazon Bedrock models which you can select from using the /models command. For example, a minimal ~/.config/opencode.json file could look like: Once the Amazon Bedrock provider is set up, you can use the /models command to switch models to global.moonshotai.kimi-k3 and start building. Kimi K3 can build substantial features and work over long-horizon tasks. In the following video, we try it out building a single-file browser-based game to get started: Figure 1: Building a browser-based game with Kimi K3 in OpenCode Beyond coding, Hermes Agent is one example of an open source assistant for general productivity. It can be used through a desktop app or popular messaging apps as well as the terminal, and supports use cases like deep research and task automation where Kimi K3 can also perform well. As detailed in their documentation , Hermes natively supports models on Amazon Bedrock. To get started: If you use named profiles to manage multiple AWS credentials in your environment, then at the time of writing you need to set the AWS_PROFILE environment variable or use your default profile for Hermes. Alternatively, you can switch to an API key. Follow the open issue here for updates on support for setting AWS profile via the Hermes configuration file. Once the Amazon Bedrock provider is set up and the model configured, you can start using Kimi K3 for your agentic workflows in Hermes. For example, see the following short video in which we ask the agent to build out a personalized study plan: Figure 2: Building a personalized study plan with Kimi K3 in Hermes Agent Kimi K3 is available today on Amazon Bedrock through the US Geo (us.) and Global (global.) cross-Region inference profiles. See Bedrock documentation for the full list of supported Regions. For pricing information, see Amazon Bedrock pricing . Give Kimi K3 a try in the Amazon Bedrock console , or explore the Moonshot AI on AWS samples repository on GitHub. Interested in how Amazon Bedrock can support your team? Connect with us to start the conversation.
由 claude-code/sonnet 自動生成