← Coding

Amazon Q DeveloperAmazon Q Developer

AWS

海外Outside China AWS生态AWS ecosystem IDE插件IDE plugin 即将停支持Support ending BedrockBedrock 代码升级Code upgrades 安全扫描Security scanning partial lifecycle: maintenance 核验Checked 2026-10-22

Amazon Q Developer 是 AWS 的编码与运维助手（Bedrock 驱动）：IDE 插件做补全/生成/安全扫描/Java 升级，问答面锚在你的 AWS 资源与架构——但官方已给 EOL：IDE 插件 2027-04-30 停止支持、CLI 已变 Kiro CLI， AWS 把 agentic 编码未来押在 Kiro 上。

Amazon Q Developer is AWS's coding-and-operations assistant (powered by Bedrock): the IDE plugin does completions/generation/security scans/Java upgrades, and Q&A is grounded in your AWS resources and architecture — but AWS has published an EOL: IDE plugin support ends 2027-04-30 and the Q CLI has become the Kiro CLI; AWS is betting its agentic-coding future on Kiro.

适合与不适合When to use it, when not to

适合：重度 AWS 用户做架构问答、资源排障、Java 升级与安全扫描这类官方招牌任务。不适合：新项目押 IDE 插件线（有 EOL 日期）、要 agentic 编码新能力（官方指向 Kiro）。

Fits: heavy AWS users — architecture Q&A with citations, resource troubleshooting, Java upgrades and security scans (the official flagship tasks). Not a fit: betting new projects on the IDE plugin line (it has an EOL date); wanting agentic-coding capabilities (AWS points to Kiro).

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-22

出品属地Origin: 国外出品foreign-made　AWS（亚马逊云科技）；中国区（光环新网/西云数据）另有独立运营口径，未逐条核验。AWS (Amazon Web Services); the China regions (GDS/NNET) have separate operations, not verified dossier by dossier in the 2026-10-08 pass.
国内使用Direct access: 大陆可直连direct OK　aws.amazon.com / docs.aws.amazon.com 大陆直连实测 200（2026-10-22）。aws.amazon.com / docs.aws.amazon.com measured 200 direct from mainland (2026-10-22).
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-22 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-22); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 官方 what-is 页明示 Powered by Amazon Bedrock：模型经 Bedrock 托管调用，模型本身经 Bedrock 增强 AWS 内容做问答；含自动滥用检测（Bedrock 侧安全机制）。用户不能自选底层模型（官方未给模型选择器）；BYOK 不适用——计费与账号走 AWS。
The official what-is page states explicitly: Powered by Amazon Bedrock — models are invoked through Bedrock; the models answer questions over Bedrock-augmented AWS content; includes automated abuse detection (a Bedrock-side safety mechanism). Users cannot self-select the underlying model (the official gives no model picker); BYOK does not apply — billing and accounts go through AWS.
运行位置Where it runs: 两条形态线：IDE 插件（VS Code / JetBrains 内的对话、内联补全、生成新代码、安全漏洞扫描、语言升级/调试/优化等代码改造）与命令行（官方 CLI 页原文「The Q CLI has become the Kiro CLI」—— CLI 线已迁 Kiro 品牌）。定位是「理解、构建、扩展、运维 AWS 应用」的生成式助手， AWS 架构/资源/最佳实践/文档问答是官方主线。
Two form lines: the IDE plugin (conversation, inline completion, generating new code, security vulnerability scans, language upgrades/debugging/optimization and other code transformations inside VS Code / JetBrains) and the command line (official CLI page original: "The Q CLI has become the Kiro CLI" — the CLI line has migrated to the Kiro brand). The positioning is a generative assistant for "understanding, building, extending and operating AWS applications"; AWS architecture/resources/best-practices/docs Q&A is the official main line.
本地文件Local files: IDE 插件在你本机 IDE 内处理代码（补全/生成/扫描在插件工作流内发生）；代码是否离开本机上传服务侧未逐条核验（Bedrock 推理在服务侧是确定事实）。问答面引用你的 AWS 资源上下文（官方口径：针对你的 AWS 资源与架构给带引用的回答）。
The IDE plugin processes code inside your local IDE (completion/generation/scanning happen within the plugin workflow). Whether code leaves the machine to the service side is not verified one by one (Bedrock inference being service-side is a settled fact). The Q&A surface references your AWS resource context (official framing: cited answers grounded in your AWS resources and architecture).
关机后的任务Tasks after shutdown: 无官方长时异步任务面（未核验到后台续跑声明）；Agentic 编码能力官方指向 Kiro （EOL 公告原文：For capabilities similar to Amazon Q Developer IDE plugins, explore Kiro… including agentic coding, chat and MCP support）。
No official long-running async task surface (no background-continuation statement verified). Agentic coding capabilities are pointed by the official to Kiro (EOL announcement original: "For capabilities similar to Amazon Q Developer IDE plugins, explore Kiro… including agentic coding, chat and MCP support").
工具与扩展Tools & extensions: IDE 插件内置能力官方列：代码对话、内联补全、生成新代码、安全漏洞扫描（security scans）、代码升级（Java 版本升级等 transformations）、调试与优化； MCP 支持在 Kiro 侧（EOL 公告点名 Kiro 有 MCP support），Amazon Q 插件侧 MCP 未核验到。
Built-in IDE-plugin capabilities listed officially: code conversation, inline completion, generating new code, security scans, code transformations (Java version upgrades etc.), debugging and optimization. MCP support sits on the Kiro side (the EOL announcement names Kiro as having MCP support); MCP on the Amazon Q plugin side is not verified.
上下文与记忆Context & memory: 上下文锚在 AWS 侧：你的 AWS 资源、架构、文档与支持内容（官方 what-is 页口径）； IDE 内跟随当前工程。跨会话记忆机制未核验到官方声明。
Context is anchored on the AWS side: your AWS resources, architecture, documentation and support content (official what-is page framing); inside the IDE it follows the current project. Cross-session memory: not verified to an official statement.
权限与限制Permissions & limits: 账号与计费走 AWS（IAM/账户体系）；IDE 插件操作本机文件的审批细节未逐条核验。 Bedrock 侧自动滥用检测是官方明示的安全机制。
Accounts and billing go through AWS (IAM/account system). Approval details for the IDE plugin operating on local files are not verified one by one. Bedrock-side automated abuse detection is the officially stated safety mechanism.
适合什么任务Best for: 适合：重度 AWS 用户——问架构/资源/最佳实践带引用、IDE 内做 Java 升级与安全扫描这类官方招牌改造任务。不适合：要 agentic 编码新能力（官方明确指向 Kiro）、要长期押注 IDE 插件线（2027-04-30 停止支持，见 pitfalls）。
Good fit: heavy AWS users — architecture/resource/best-practice questions with citations, and official-signature transformation tasks in the IDE like Java upgrades and security scans.

Not a fit: wanting agentic coding's new capabilities (the official clearly points to Kiro), betting long-term on the IDE plugin line (support ends 2027-04-30, see pitfalls).

头号误解Top misconception

官方 EOL 公告：Amazon Q Developer IDE 插件 2027-04-30 停止支持（AWS 官方 End of support notice），官方点名替代是 Kiro（agentic coding/chat/MCP）——现在选型新项目的 IDE 面应直接看 Kiro 档案Official EOL notice: support for Amazon Q Developer IDE plugins ends 2027-04-30 (AWS End of support notice); the official alternative is Kiro (agentic coding/chat/MCP) — new-project IDE choices should go straight to the Kiro dossier
CLI 线已改名：官方 CLI 页原文「The Q CLI has become the Kiro CLI」——搜到的旧 Q CLI 教程实际指向 Kiro CLI（kiro.dev/docs/cli）The CLI line has been renamed: the official CLI page says 'The Q CLI has become the Kiro CLI' — old Q CLI tutorials actually point to Kiro CLI (kiro.dev/docs/cli)
产品未停运（2026-10-22 官网与文档均 200，lifecycle 仍 active）——「有 EOL 公告」与「已死」是两回事，过渡期内插件仍可用The product is not dead (site and docs measured 200 on 2026-10-22, lifecycle still active) — 'an EOL notice exists' and 'it is gone' are different things; the plugin keeps working during the transition window

未知项清单Known unknowns

IDE 插件侧是否支持 MCP（官方只在 Kiro 侧点名 MCP support）
跨会话记忆机制（未核验到官方声明）
插件操作本机文件的审批模型细节（未逐条核验）
中国区功能面（未核验）

Whether the IDE plugin side supports MCP (the official names MCP support only on the Kiro side)
Cross-session memory mechanism (not verified to an official statement)
Details of the approval model for the plugin operating on local files (not verified one by one)
Feature surface in the China regions (not verified)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-22，内容更新日content updated on 2026-10-22。

类型Type	名称Name	链接Link
official	AWS 文档 · What is Amazon Q Developer（Bedrock 驱动/IDE 能力清单/EOL 公告横幅）AWS docs · What is Amazon Q Developer (Bedrock-driven / IDE capability list / EOL announcement banner)	https://docs.aws.amazon.com/en_en/amazonq/latest/qdeveloper-ug/what-is.html
official	AWS 文档 · Amazon Q Developer IDE plugins end of support（2027-04-30 停支持公告）AWS docs · Amazon Q Developer IDE plugins end of support (2027-04-30 end-of-support notice)	https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-developer-ide-end-of-support.html
official	AWS 文档 · Using Amazon Q Developer on the command line（Q CLI 已变 Kiro CLI）AWS docs · Using Amazon Q Developer on the command line (the Q CLI has become the Kiro CLI)	https://docs.aws.amazon.com/en_en/amazonq/latest/qdeveloper-ug/command-line.html
changelog	AWS 文档 · Document history（changelog）AWS docs · Document history (changelog)	https://docs.aws.amazon.com/en_en/amazonq/latest/qdeveloper-ug/doc-history.html
official	Amazon Q Developer 产品页（定价/形态入口）Amazon Q Developer product page (pricing / form entry points)	https://aws.amazon.com/q/developer/

实测记录Measured runs

本档未跑端到端编码任务；能力结论来自官方文档，编码向测量协议见 protocols/coding/_protocol.md。

实测建议（三条，都指向官方可读页没给的东西）：

EOL 后插件的实际可用窗口（2027-04-30 前插件是否随 IDE 版本继续更新）
IDE 插件代码上传服务侧的具体边界（补全/扫描哪些内容出本机）
中国区（光环新网/西云数据）是否有对应功能面（未核验）

This site has not completed measured runs. The test protocol is at protocols/coding/_protocol.md.

Suggested measurement (three, each pointing at something the official readable pages do not give):

The plugin's actual usable window after EOL (whether the plugin keeps updating with IDE versions before 2027-04-30)
The concrete boundary of what the IDE plugin uploads to the service side (which content leaves the machine for completion/scanning)
Whether the China regions (GDS/NNET) have corresponding feature surfaces (not verified)