The deck looked great. The proof-of-concept worked. The marketing team had three workflows mapped out and a six-week pilot plan. Then it hit the security review queue, and that’s where it sat for 11 weeks.
We’ve watched several B2B SaaS marketing teams kill AI pilots this way in the last quarter. None of them lost on the technology. They lost on the procurement memo.
On May 11, 2026, AWS announced general availability of Claude Platform on AWS — and the most interesting thing about it isn’t the product. It’s the org chart it routes around.
What’s actually new
Claude on AWS already existed through Bedrock. You could call the models. What you couldn’t do was use the full native Claude platform — Managed Agents, Agent Skills, the MCP connector, code execution, the files API, the advisor tool. That’s the stack Anthropic ships to its direct customers. Claude Bedrock got the engine. AWS customers who wanted the chassis had to go sign a separate Anthropic contract.
Now they don’t.
Claude Platform on AWS is the full native experience, accessed through AWS Marketplace, authenticated with the same IAM credentials your team already uses, billed on your existing AWS invoice, logged in CloudTrail next to your S3 buckets. AWS is the first cloud to ship anthropic on aws this way — not just model access, the entire platform.
That distinction sounds like a feature comparison. It isn’t. It’s a procurement story.
The procurement story marketing teams will recognise
Here’s the actual sequence of events that kills most marketing AI pilots inside B2B SaaS:
The marketing ops lead trials something on a personal API key. It works. They write up the use case. Finance flags a new vendor. Security flags a new DPA. IT flags a new SSO integration. Legal flags the data residency questions. Procurement asks for a second-source bake-off. Six weeks become twelve weeks become next quarter become “let’s revisit this in the planning cycle.”
We’re not exaggerating. A content ops team at a Series B SaaS company we know sat on a Claude-powered editorial workflow for 14 weeks while three separate departments rotated through their review queues. The pilot eventually shipped — to a single user, on a personal account, never operationalised across the team.
What Claude Platform on AWS removes from that sequence:
- New vendor. Anthropic isn’t a new vendor on this path. AWS already is.
- New billing relationship. Usage flows through the AWS Marketplace and shows up in the same monthly invoice your finance team already approves.
- New auth integration. IAM is already wired into your SSO. Your marketing team doesn’t get a separate login.
- New audit logs. CloudTrail captures inference activity the same way it captures everything else. Your security team already monitors it.
- Data residency conversation. For teams already comfortable with their AWS region setup, this slots into the same boundary they’ve already approved.
What it doesn’t remove: the actual security review of what your team plans to do with claude on aws, the data classification work, and the question of whether your AWS region is acceptable. The platform launched in 17 regions; Mumbai isn’t one of them, which matters for some Indian SaaS customers.
What we’d actually do with it
The teams we work with that already run heavy AWS infrastructure — particularly SaaS companies with marketing data warehoused in Redshift or S3 — have three obvious wins.
Marketing analytics that operate where the data lives. If your event data, CRM exports, and product analytics already sit inside an AWS account, you can point Claude at them through Agent Skills and MCP connectors without an egress conversation. Multi-touch attribution audits, cohort behaviour analysis, pipeline forecasting — the things marketing analytics teams have wanted to automate but couldn’t because the data couldn’t leave the perimeter.
Content and creative workflows with auditability. The MCP connector lets Claude reach into your existing systems — CMS, asset library, Slack, Linear — and every call lands in CloudTrail. Marketing teams get the AI workflow; security teams get the audit trail they need to sign off on it. That trade has been the bottleneck for two years.
Agent Skills for repeatable marketing operations. This is the underrated piece. Agent Skills let you encode your operational playbooks — how your team writes ad copy, how you build audit reports, how you generate competitor briefs — into reusable structures that Claude pulls in automatically. You stop re-prompting the same context every week. The discipline this enforces is what makes ai marketing automation workflows survive past their pilot phase, which is what most marketing teams haven’t figured out yet.
Where the new trap sits
The procurement friction goes away. The decision friction doesn’t.
Two things to watch:
Bedrock vs Platform isn’t a small distinction. Teams already using “Claude on AWS” through Bedrock will hear “Claude Platform on AWS” and assume it’s the same product with new packaging. It isn’t. Bedrock is model access. Platform is the agent stack on top of the models. If you want Agent Skills or the MCP connector for your marketing workflows, you need Platform. If you just want to call the Messages API from a backend service, Bedrock still works fine. The procurement path is now the same; the capability surface isn’t.
You still need someone to drive it. Removing the procurement blocker doesn’t generate the workflow. The teams that get value from claude on aws in the next two quarters will be the ones already running marketing ops experiments on their own keys, now with somewhere serious to put them. The teams that haven’t started will use the AWS Marketplace listing as another reason to delay until “we have time to scope it properly.”
What this means for your Q3 planning
If your security or procurement team has previously rejected a Claude-based marketing tool, this is the moment to put it back on the list. Walk in with the AWS Marketplace listing, the IAM auth flow, and the CloudTrail integration. That’s three of the boxes their review template wants ticked, already ticked.
If you’re already running ai marketing aws experiments on personal keys: this is the moment to make them official. Pick the workflow with the cleanest data path — ad reporting, content audits, lead enrichment — and propose it as a workspace under your existing AWS account. The fight you’ve been putting off is now a 30-minute conversation, not a quarter.
If you’re building from scratch, start with something boring. A content compliance checker. A weekly competitor brief generator. A campaign-level Slack summary. The pilots that survive procurement aren’t the ambitious ones — they’re the ones with a clear input, a clear output, and an obvious owner.
This is the third platform announcement this year that quietly moves enterprise AI adoption forward by removing a non-technical blocker. We covered the Claude Connectors release and Amazon Quick Suite for marketing operations earlier this year. The pattern is consistent: the technology isn’t the bottleneck. The org chart is. The platforms that win this cycle are the ones that ship around it.
If you’re trying to figure out where your stack fits in, we run a free AI marketing audit for B2B SaaS teams — happy to walk through which workflows are worth piloting first.
Frequently asked questions
What is Claude Platform on AWS?
Claude Platform on AWS is Anthropic’s native platform — including Managed Agents, Agent Skills, the MCP connector, code execution, and the files API — accessed directly through an AWS account. It launched in general availability on May 11, 2026. The platform is operated by Anthropic, but authentication, billing, and audit logging all run through standard AWS services.
Is Claude Platform on AWS the same as Claude Bedrock?
No. Bedrock gives you API access to the Claude models. Claude Platform on AWS gives you the full Anthropic platform on top of those models — Agent Skills, the MCP connector, Managed Agents, web search, web fetch, code execution, and the files API. Most of those capabilities don’t exist on Bedrock today.
Which AWS regions support Claude Platform on AWS?
Seventeen regions at launch, including US East (N. Virginia, Ohio), US West (Oregon), Canada Central, São Paulo, Dublin, London, Frankfurt, Milan, Zurich, Paris, Stockholm, Tokyo, Seoul, Melbourne, Jakarta, and Sydney. Mumbai is not included at launch, which matters for teams with India data residency requirements.
Do I need a separate Anthropic account?
No. Authentication uses your existing AWS IAM credentials and billing flows through the AWS Marketplace on a consumption basis. Audit activity is captured in CloudTrail alongside the rest of your AWS services.
Should B2B SaaS marketing teams switch from Bedrock to Claude Platform on AWS?
Only if you need capabilities Bedrock doesn’t offer — Agent Skills, the MCP connector, Managed Agents, the advisor tool, or the files API. For straightforward model calls, Bedrock is still fine and processes data inside the AWS security boundary, which Platform on AWS does not.