Question

A financial services company runs a multi-account AWS Organization. The central governance team must ensure that only two approved foundation models can be enabled in Amazon Bedrock across all member accounts, and that no developer or account administrator can request access to any other model — even if they hold broad IAM permissions within their own account. The solution must be enforced centrally and not rely on per-account IAM policy hygiene. Which approach best meets these governance requirements?

Accepted Answer

Attach a Service Control Policy (SCP) at the organizational unit level that denies bedrock:PutFoundationModelEntitlement and bedrock:CreateModelInvocationJob for any model except the two approved model ARNs

Answer

Create an identity-based IAM policy in each member account granting bedrock:InvokeModel only on the two approved model ARNs and rely on account admins to attach it to all principals

Answer

Enable Amazon Bedrock model access in the management account only and share the enabled models to member accounts via AWS Resource Access Manager (RAM)

Answer

Configure a Bedrock Guardrail with a denied topics policy that blocks prompts routed to unapproved models and apply it account-wide