Registry / Claude via AWS Bedrock
Claude via AWS Bedrock
Anthropic's Claude models served through Amazon Bedrock, AWS's managed foundation-model service. Vendor-trust and data-handling posture is AWS's (SOC/ISO scope, AWS BAA, GDPR DPA, Bedrock retention controls); EU AI Act provider obligations (GPAI Code of Practice, Art 53) sit with Anthropic as the model developer.
Watch-outs 4
The cells where this offering is not a clean public yes. This is what to check before you sign.
- SOC 2 Type II: Yes, sales-gated SOC 2 Type II report exists but is behind an access‑request gate
- HIPAA BAA: Yes, sales-gated BAA is obtained via AWS Artifact; coverage applies when Bedrock (including Claude) is used as a HIPAA‑eligible service.
- Retention / ZDR: Partial ZDR availability requires contacting the AWS account manager / Anthropic account rep for per-account, per-model approval; no console UI at launch.
- Art. 53 summary: Yes, sales-gated access requires request‑access form
Anthropic’s Trust Center lists a SOC 2 Type II report and requires a request form to view it, confirming the report is available but not public.
To access sensitive documents, please click the "request access" button at the top of the page and complete the request form.
trust.anthropic.com is Anthropic's own authoritative trust portal and shows ISO 27001 marked ✅ in its scope table; per the ISO 42001 precedent, Anthropic's own certification covers the Claude model on any platform including AWS Bedrock, so yes_public is correct.
ISO 27001 | ✅
Anthropic’s own public announcement confirms ISO/IEC 42001 certification for its AI management system, which covers Claude on any platform including AWS Bedrock.
We are excited to announce that Anthropic has achieved accredited certification under the new ISO/IEC 42001:2023 standard for our AI management system.
AWS Artifact is a publicly accessible self‑service portal that provides on‑demand access to compliance reports for AWS services and ISVs, covering Claude offered via Bedrock.
Save time with on‑demand access to AWS and Independent Software Vendor (ISV) compliance reports in a self‑service portal.
AWS offers a BAA through its Artifact portal and lists Amazon Bedrock as a HIPAA‑eligible service, so a HIPAA BAA can be signed for Claude via Bedrock, but access is gated behind the sales/account process.
Yes. AWS has a standard Business Associate Addendum (BAA) we present to customers for signature. ... To review, accept, and manage the status of the BAA for your account, sign in to AWS Artifact in the AWS Management Console.
The AWS DPA on AWS's own domain is public, incorporates SCCs, and its §6.1 confirms a published subprocessor list, satisfying yes_public for the Bedrock platform's DPA.
Custom... The AWS website (currently posted at https://aws.amazon.com/compliance/sub-processors/) lists Sub-processors that are currently engaged by AWS.
The AWS Bedrock FAQ publicly states that customer content, including API data, is not used to train or improve the underlying models, covering Claude via Bedrock.
With Amazon Bedrock, your content is not used to improve the base models and is not shared with any model providers.
Retention is publicly documented and self-serve configurable, but ZDR access for Claude models is gated behind AWS/Anthropic account representative approval, fitting partial per the rubric.
Zero data retention (ZDR) access is evaluated on a per-account, per-model basis in coordination with the model provider. ... ZDR eligibility for Claude models is managed by Anthropic. Contact your Anthropic account representative for support.
AWS Bedrock model card explicitly states the EU geo inference ID keeps data within EU regions, confirming data can be pinned to an EU region.
"EU geo(`eu.anthropic.claude-sonnet-5`): Keeps data within EU regions."
Anthropic is listed among the public signatories of the GPAI Code of Practice on the European Commission site.
Anthropic
Anthropic lists a Claude Sonnet 5 Training Data Summary but gated behind a request‑access form, meeting the definition of yes_sales_gated.
To access sensitive documents, please click the "request access" button at the top of the page and complete the request form.
Spotted an error? Submit a correction with evidence, corrections with a primary source are folded in and credited in the changelog.