Registry / Llama via AWS Bedrock
Llama via AWS Bedrock
Meta's Llama 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 Meta as the model developer. Meta is absent from the EC's GPAI Code of Practice signatory list, and current-generation Llama models on Bedrock are served in US geography only.
Watch-outs 5
The cells where this offering is not a clean public yes. This is what to check before you sign.
- SOC 2 Type II: Partial SOC 2 Type II covers the Bedrock platform, not Llama the third-party model individually.
- ISO 27001: Partial AWS's ISO 27001 covers the Bedrock platform but excludes Bedrock Marketplace and does not extend to the third-party Llama model itself.
- ISO 42001: Partial AWS's ISO/IEC 42001 certificate covers Amazon Bedrock as a platform service; Meta (Llama's developer) has no published ISO/IEC 42001 certificate, so Llama itself is not individually in scope.
- HIPAA BAA: Yes, sales-gated requires entering into an AWS BAA via sales/account process
- GPAI Code: No, verified Verified the EC's authoritative signatory list; Meta (developer of Llama) is absent from the complete, confirmed list, justifying no_verified per the GPAI rule.
AWS's own SOC in-scope page confirms Bedrock (platform) is in SOC 2 scope, but the certification covers the serving platform, not the third-party Llama model, so partial is correct per the platform-vs-model rule.
Amazon Bedrock [excludes Amazon Bedrock Marketplace] ✓
Verified on AWS's own ISO-certified page that Amazon Bedrock is in ISO 27001 scope with an express exclusion of the Bedrock Marketplace, and per the platform-vs-model rule the platform certificate does not certify the third-party Llama model, supporting partial.
Amazon Bedrock [excludes amazon Bedrock Marketplace]
The AWS blog confirms the platform's own accredited ISO/IEC 42001 certification covering Bedrock, but no public certificate exists for the model developer Meta, so per the platform-vs-model rule the value is partial, not yes_public.
Amazon Web Services (AWS) is excited to be the first major cloud service provider to announce ISO/IEC 42001 accredited certification for AI services, covering: Amazon Bedrock, Amazon Q Business, Amazon Textract, and Amazon Transcribe.
AWS Artifact is a publicly accessible self‑service compliance portal maintained by AWS, satisfying the requirement.
Save time with on-demand access to AWS and Independent Software Vendor (ISV) compliance reports in a self-service portal.
AWS lists Amazon Bedrock as a HIPAA‑eligible service and explicitly requires a signed AWS Business Associate Agreement before use.
Amazon Bedrock ... (listed among HIPAA Eligible Services) ... NOTE: If you are a Covered Entity or Business Associate ... you agree not to use these HIPAA Eligible Services ... without first entering into an AWS business associate agreement.
AWS provides a publicly available Data Processing Addendum that incorporates the EU SCCs and maintains an openly accessible sub‑processor list, covering all AWS services including Bedrock.
The SCCs are part of the AWS Service Terms, are incorporated by reference into the AWS DPA, and apply automatically ...
The AWS Bedrock FAQ publicly states that customer content is not used to improve base models, confirming a default no‑training commitment for Llama on Bedrock.
With Amazon Bedrock, your content is not used to improve the base models and is not shared with any model providers.
AWS Bedrock documentation publicly describes data‑retention settings and notes that zero‑data‑retention mode exists, though eligibility is evaluated per account and model.
Zero data retention (ZDR) access ... ZDR access is evaluated on a per-account, per-model basis in coordination with the model provider.
The recorded quote is present on the authoritative AWS docs page, but the value 'partial' understates the evidence: the page documents a self-serve In-Region option that "keeps requests within a single Region" and shows it is available for eu-central-1, eu-west-1, and eu-west-3, meaning data can be
Amazon Bedrock offers three inference options: **In-Region** keeps requests within a single Region for strict compliance... Region | In-Region | Geo | Global — eu-central-1 (Frankfurt) | ✅ | ✅ | ✅ — eu-west-1 (Ireland) | ✅ | ✅ | ✅ — eu-west-3 (Paris) | ✅ | ✅ | ✅
Verified the EC's authoritative signatory list; Meta (developer of Llama) is absent from the complete, confirmed list, justifying no_verified per the GPAI rule.
## Signatories of the code of practice - AI Studio Delta - Aleph Alpha - Almawave - Amazon - Anthropic - Black Forest Labs - Bria AI - Cohere - Domyn - Dweve - Fastweb - IBM - LINAGORA - Microsoft - Mistral AI - Open Hippo - OpenAI - Pleias - ServiceNow - WRITER
The row is "Llama via AWS Bedrock" — a serving-platform row — and the rubric states art53_summary is a DEVELOPER obligation making serving-platform rows not_applicable; additionally the cited transparency page covers only the separate Art 53(1)(d) transparency obligation, not the 53(1)(c) training-c
EU AI Act Transparency Reports. These reports are published by Meta Platforms Ireland Limited pursuant to Article 53(1)(d) of Regulation (EU) 2024/1689 (AI Act).
Spotted an error? Submit a correction with evidence, corrections with a primary source are folded in and credited in the changelog.