AWS becomes first cloud provider to offer native Claude platform access

Most enterprise teams are not short on vendor accounts. They are short on time to manage them. Another contract, another billing portal, another set of credentials sitting in a shared doc somewhere. AWS just cut one of those headaches out entirely for developers working with Anthropic’s Claude.

This week, AWS made Claude Platform generally available through existing AWS accounts. Developers skip the separate account, the standalone contract, and the extra billing setup entirely. Developers simply use the IAM credentials they already have, and CloudTrail handles audit logging the way it normally would.

The setup differs from what AWS already offered through Amazon Bedrock. Bedrock gives customers access to Claude models inside AWS’s managed AI service, where AWS acts as the data processor. Claude Platform on AWS works differently. Anthropic operates the service directly and processes customer data outside the AWS security boundary. In other words, developers get Anthropic’s native environment, with AWS sitting at the access layer rather than underneath the workload itself.

The feature set covers a lot of ground. Specifically, access includes Claude Managed Agents, code execution, web search, web fetch, prompt caching, batch processing, and citations. The Files API lets teams upload and reference documents mid-conversation.

Meanwhile, the MCP connector links Claude to remote Model Context Protocol servers without requiring any client code. Anthropic also committed to shipping new API features and beta capabilities on the same day they hit its native platform, which matters for teams that want to stay current without chasing separate release schedules.

The financial relationship behind this partnership is worth understanding. Amazon’s total investment in Anthropic hit eight billion dollars in late 2024. Then in April 2026, Anthropic committed more than one hundred billion dollars to AWS technologies over the next decade. That is not a casual partnership. Consequently, moves like this one reflect a tightly integrated strategy rather than a one-off product decision.

Early users described the access model as the core appeal. ReliaQuest pointed to simpler access for cybersecurity and engineering workflows. OpenRouter highlighted native API features through existing credentials. Emergent called it the canonical Anthropic API with AWS as the entry point.

For teams already living inside AWS, the gap between their existing infrastructure and one of the more capable AI platforms just got considerably smaller.