Amazon Bedrock Guardrails supports cross-account safeguards with centralized control and management | Amazon Web Services (opens in new tab)
Amazon Bedrock Guardrails now supports cross-account safeguards, allowing organizations to centrally enforce safety controls across AWS accounts and organizational units. Administrators can apply immutable, versioned guardrails to all Bedrock model invocations while still allowing account- or application-specific policies. The capability is generally available across commercial and GovCloud Regions where Bedrock Guardrails is supported. ## Centralized Organization- and Account-Level Enforcement - **Organization-level enforcement** uses an Amazon Bedrock policy created in the AWS Organizations management account. - Policies can attach a specified guardrail and version to: - The organization root - Organizational units - Individual AWS accounts - The selected guardrail is automatically applied to Bedrock inference requests across targeted member entities. - Different policies and guardrails can be assigned to different accounts or organizational units. - **Account-level enforcement** applies a configured guardrail to all Bedrock inference API calls within one account and Region. ## Configuring Guardrail Coverage - Guardrails must use a specific version so their configuration remains immutable and cannot be changed by member accounts. - Administrators can choose whether enforcement: - Includes or excludes specific Bedrock models - Covers all or only selected system and user prompt content - **Comprehensive** mode guards all content, regardless of caller-provided tags. - **Selective** mode relies on callers to identify content requiring protection, reducing processing for pre-validated inputs. ## Testing and Verification - Account-level enforcement can be configured in the Amazon Bedrock Guardrails console. - Enforcement can be tested with: - `InvokeModel` - `InvokeModelWithResponseStream` - `Converse` - `ConverseStream` - Responses include guardrail assessment details and identify the enforced guardrail. - Member accounts can verify organization-level enforcement in the Bedrock console. ## Important Considerations - Organizations must meet prerequisites such as configuring resource-based policies for guardrails. - Incorrect or invalid guardrail ARNs can cause policy violations, prevent safeguards from being enforced, and block model inference. - Automated Reasoning checks are not supported. - Charges apply for each enforced guardrail based on its configured safeguards. ## Availability Cross-account safeguards are generally available in all commercial and GovCloud AWS Regions where Amazon Bedrock Guardrails is available. Organizations can enable the feature through the Amazon Bedrock and AWS Organizations consoles. Overall, the capability gives security teams a centralized way to enforce responsible AI requirements while reducing the need to audit guardrail settings independently in every account and application.