227 points
• 7 days ago
• Article
Link
AWS 上的 Claude 平台现已全面可用，AWS 客户现在可以通过原生的 AWS 身份验证、计费和承诺抵消，访问完整的 Claude API 功能集。对于已经在 AWS 上构建的团队而言，这意味着可沿用现有的 IAM 凭证与权限来使用 Claude，且计费可合并到同一张 AWS 发票中。
平台支持的高级功能包括 Claude Managed Agents（用于大规模部署 agent）、用于提升 agent 智能的 advisor 策略，以及代码执行、网络搜索、 Skills 、 Files API 、 Prompt Caching 、批量处理（Batch Processing）和 MCP connector 等实用工具。 Anthropic 的开发环境 Claude Console 也一并提供，包含 prompt improver 、 generator 和评估工具。目前可用的模型有 Claude Opus 4.7 、 Sonnet 4.6 和 Haiku 4.5，新模型在发布后会立即上架。
该产品面向想要完整 Claude 平台体验的 AWS 用户。服务由 Anthropic 运营，数据处理位于 AWS 边界之外，因此在功能上与原生 Claude API 完全一致，且可在第一时间访问所有新能力和 beta 功能。这使得它对追求最新模型特性和简化云运营的工程团队非常有吸引力，例如使用 Claude Code 的团队。 ReliaQuest 、 OpenRouter 和 Emergent 等早期采用者表示，这一方案让他们更快将先进 AI 集成到网络安全、工程和平台工作流中，同时保持现有云治理和工具链不变。
公告还明确区分了 Claude Platform on AWS 与 Amazon Bedrock 上的 Claude：两者虽都运行在 AWS 上，但 Bedrock 将 AWS 作为数据处理方并在其基础设施内处理数据，这对有严格数据驻留要求的客户至关重要。相比之下，AWS 上的 Claude 平台在 AWS 边界之外运行，更适合将功能广度和迭代速度放在首位而非将所有处理留在 AWS 内部的客户。企业应根据合规需求做出选择：需要数据完全留在 AWS 内部的可选 Bedrock，追求完整功能与更快更新的可选 AWS 上的 Claude 平台。
从落地角度看，AWS 客户可以沿用熟悉的上手流程：身份验证通过 IAM，审计通过 CloudTrail，计费纳入 AWS 承诺，从而无需对接额外供应商或管理新账户。该平台支持全球与美国的推理地域，并在大多数 AWS 商业区可用，便于安全、财务与工程团队在统一的云合同和治理框架下，直接访问 Anthropic 的最新模型与工具。
部分功能仍属 beta，例如 Managed Agents 、 advisor 策略、 Files API 和 Skills，但已作为平台功能提供。当前在 Bedrock 并拥有 private offers 的客户需与 Anthropic 或 AWS 客户经理沟通，妥善转移折扣，因为折扣无法追溯。总体而言，AWS 上的 Claude 平台被定位为 Anthropic 的一项首创产品，使 AWS 客户能在现有云环境中更便捷地构建更强大的 agent 与应用，减少运营负担折衷，并即时使用不断演进的 Claude API 。
The Claude Platform on AWS is now generally available, giving AWS customers a new way to access the full Claude API feature set with native AWS authentication, billing, and commitment retirement. This launch means that teams already building on AWS can use their existing IAM credentials and permissions to work with Claude, with billing consolidated onto a single AWS invoice. Customers can access advanced tools like Claude Managed Agents for deploying agents at scale, the advisor strategy for boosting agent intelligence, and practical utilities such as code execution, web search, skills, files API, prompt caching, batch processing, and the MCP connector. The Claude Console, Anthropic's development environment, is included and provides a prompt improver, generator, and evaluation tools. Currently, Claude Opus 4.7, Sonnet 4.6, and Haiku 4.5 are available, with new models shipping as they launch.
This offering is designed specifically for AWS users who want the complete Claude Platform experience. Anthropic operates the service and data is processed outside the AWS boundary, which means full feature parity with the native Claude API and day-one access to all new capabilities and betas. That makes it a strong fit for engineering teams, like those using Claude Code, who want cutting-edge model features and a streamlined cloud operating model. Several early adopters, including ReliaQuest, OpenRouter, and Emergent, highlight that this setup let them integrate advanced AI into cybersecurity, engineering, and platform workflows faster, while keeping existing cloud governance and tooling intact.
The announcement clarifies that this is different from Claude on Amazon Bedrock. While both run on AWS, Bedrock keeps AWS as the data processor within its infrastructure, which is important for customers with strict data residency requirements. The Claude Platform on AWS runs outside the AWS boundary, so it appeals to those who prioritize feature breadth and velocity over keeping all processing inside AWS's own perimeter. Companies are encouraged to choose based on their compliance needs: fully in-AWS data handling with Bedrock versus full feature access and control with the Claude Platform on AWS.
From a practical standpoint, AWS customers get a familiar onboarding path. Authentication happens via IAM, auditing through CloudTrail, and billing through AWS commitments, so teams don't have to integrate a separate provider or manage new accounts. The platform supports global and U.S. inference geographies, with availability across most AWS commercial regions. For organizations, this means security, finance, and engineering teams can align on a single cloud contract and governance model while still getting direct access to Anthropic's latest models and tools.
Some features are still in beta, such as Managed Agents, the advisor strategy, Files API, and Skills, but they are included now as part of the platform. Customers already on Bedrock with private offers should coordinate with their Anthropic or AWS account executives to transfer discounts correctly, since discounts cannot be applied retroactively. Overall, the Claude Platform on AWS is positioned as a first-of-its-kind offering from Anthropic, letting AWS customers build more capable agents and applications inside their existing cloud environment, with fewer operational overhead trade-offs and immediate access to the evolving Claude API surface.
89 comments • Comments Link
• 在 AWS 上的 Claude 方案主要目标是简化企业采购与计费流程：团队可以用现有的 AWS 账户、 IAM 策略和 FinOps 流程来接入 Claude AI 服务，而不必经历冗长的供应商入驻、法律审查或签订新合同——这些环节在大型组织中会带来显著摩擦。
• 目前在 AWS 上访问 Claude 有两种方式。"Amazon Bedrock 上的 Claude"把 AWS 作为数据处理方，在 AWS 边界内完成推理，适合有严格数据驻留要求的公司。而新推出的 "AWS 上的 Claude 平台"则通过 AWS 计费、由 Anthropic 运营，数据在 AWS 边界外处理，并从一开始就提供完整的 Claude 原生 API 功能集。
• 多位受访者表示，与 AWS 计费集成是他们选择该路径的"唯一原因"，因为这允许团队将 AI 支出掩盖或合并进现有的 AWS 账单，从而避免每月数千美元波动触发额外审批；若走独立供应商合同，则通常需要严格的审批流程。
• 对于账单规模巨大的中端市场和大型企业（每月 AWS 账单处于中高八位数到低九位数），通过 AWS 管道路由 Anthropic 付款可以完全绕过繁琐审批，这也有助于满足年度 AWS 支出承诺，并有可能在高用量层级获得私有定价折扣。
• 但需要注意的是，通过 AWS Marketplace 的支出通常受限于年度承诺合同总额的大约 25%，这限制了组织可通过该渠道转移的金额。此外，Bedrock 上的 Claude 在某些情况下仍会产生单独的 Marketplace 发票，因而计费整合的好处并非始终无缝。
• 对初创公司而言，将 AWS 积分用于 Claude 的政策各有不同。自 2024 年 4 月起，标准的 AWS Activate 积分已覆盖 Bedrock 上的 Claude（此前存在一些例外）；AWS Activate 的 Builder 积分通常可用于多类服务，而 YC 提供的积分是否包含 Marketplace 消费则取决于具体项目。
• 在功能对等性方面，Bedrock 落后于原生 Claude API 平台，有时滞后数月甚至超过一年；据报道，Bedrock 在高负载下更易出现 500 错误且成本更高，因此需要完整 API 功能访问并设计跨供应商工作负载平衡的团队会更倾向于新的 AWS 上的 Claude 平台。
• 对于有严格合规与数据驻留要求的组织（例如要求在美国境内推理的受控出口工作负载），Bedrock 仍是必选方案，因为新的 Claude 平台在 AWS 边界外处理数据；部分此类评论者对 Anthropic 的运营可靠性未能与其模型质量相匹配表示失望。
• "Amazon Bedrock 上的 Claude"与"AWS 上的 Claude 平台"之间令人迷惑的命名差异，被视为 AWS 命名复杂性问题的一部分，部分原因是 Amazon 内部对用户体验设计的优先级较低。
• 还存在定价与采购方面的担忧：通过 AWS Marketplace 路由供应商采购可能让低质量供应商绕过正常采购审查，因而引发企业对采购控制合规性的质疑。
讨论的核心是：这项新服务本质上更像是企业采购与计费的解决方案，而非纯技术创新。其主要价值主张在于为深度嵌入 AWS 生态的组织减少摩擦——在这些组织中，引入新供应商合同需经过法律、采购和安全审查，通常耗时数月。尽管两种方案在数据驻留和功能对等性上存在合理的技术差异，但总体共识是采购便利性是主要驱动力；混淆的命名在已经碎片化的 AWS 服务格局中只会增加不必要的复杂性。部分评论者还提出了合规影响的担忧，以及现有 AWS 承诺合同中 Marketplace 支出上限可能带来的限制。 • The Claude Platform on AWS offering is primarily about simplifying enterprise procurement and billing, allowing teams to use existing AWS accounts, IAM policies, and FinOps processes to adopt Claude AI services without going through lengthy vendor onboarding, legal reviews, or new contract negotiations, which adds significant friction in large organizations.
• There are now two distinct ways to access Claude on AWS. "Claude on Amazon Bedrock" keeps AWS as the data processor and handles inference within the AWS boundary, making it suitable for companies with strict data residency requirements. "Claude Platform on AWS" (the new offering) is billed through AWS but is operated by Anthropic with data processed outside the AWS boundary, giving access to the full native Claude API feature set from day one.
• Several commenters confirm that the billing integration with AWS is "the one and only reason" for using this route, as it allows teams to launder or obscure AI spend within their existing AWS bills, where monthly spend fluctuations of several thousand dollars go unquestioned, unlike the rigorous approval processes required for new standalone vendor contracts.
• Middle market and large enterprises with massive AWS bills (mid eight to low nine figures monthly) can bypass red tape entirely by routing Anthropic payments through their AWS pipeline, which also helps companies meet their annual AWS spending commitments and potentially unlock private pricing discounts at higher volume tiers.
• However, marketplace spending through AWS is often capped at around 25% of the total annual commitment contract, limiting how much organizations can funnel through this channel. Additionally, Claude models on Bedrock still generate separate marketplace invoices in some cases, so the billing consolidation benefits may not be as seamless as assumed.
• For startups, the ability to apply AWS credits to Claude usage varies. While standard AWS Activate startup credits have covered Claude on Bedrock since April 2024 (with some earlier exceptions), AWS Activate builder credits broadly apply across services, and YC-provided credits may or may not cover marketplace consumption depending on the program.
• Bedrock lags behind the native Claude API platform in terms of feature parity, sometimes by months or over a year, and Bedrock has been reported as both more expensive and more prone to 500 errors under load, making the new Claude Platform on AWS offering more attractive to teams that need full API feature access and design parity for workload balancing across providers.
• For organizations with strict compliance and data residency needs (such as export-controlled workloads requiring US-only inference), Bedrock remains the required option because the new Claude Platform processes data outside the AWS boundary, and some commenters in this position express frustration that Anthropic's operational reliability has not matched the quality of its models.
• The confusing naming distinction between "Claude on Amazon Bedrock" and "Claude Platform on AWS" is seen as a continuation of AWS's well-known naming complexity problem, with blame partly attributed to UX design being deprioritized internally at Amazon.
• There is also pricing and procurement concern that routing vendor purchases through AWS Marketplace could allow lower-quality vendors to bypass normal procurement scrutiny, raising compliance questions about procurement controls in many enterprises.
The discussion centers on the fact that this new offering is fundamentally an enterprise procurement and billing solution rather than a technical one. The core value proposition is friction reduction for organizations already deeply embedded in the AWS ecosystem, where adding a new vendor contract requires legal, procurement, and security reviews that can take months. While there are legitimate technical differences between the two options—particularly around data residency and feature parity—the overwhelming consensus is that procurement convenience is the primary driver, and the confusing naming adds unnecessary complexity to an already fragmented AWS service landscape. Some commentators also raise concerns about compliance implications and the potential limitations of marketplace spending caps within existing AWS commitment contracts.