New pattern - bedrock-guardrails-cross-account-cdk by NithinChandranR-AWS · Pull Request #3067 · aws-samples/serverless-patterns

NithinChandranR-AWS · 2026-04-20T11:44:02Z

Bedrock Guardrails Account-Level Enforcement

Creates a Bedrock Guardrail, versions it, and enables account-level enforcement. The guardrail automatically applies to ALL Bedrock calls in the account without specifying guardrailIdentifier.

Architecture: CDK creates Guardrail → versions via AwsCustomResource → enforces account-wide → Test Lambda demonstrates automatic enforcement

Key decisions:

AwsCustomResource for PutEnforcedGuardrailConfiguration (not in Lambda runtime SDK)
Content filters (HATE, INSULTS, SEXUAL, VIOLENCE, MISCONDUCT, PROMPT_ATTACK) + denied topic (investment advice)
Automatic cleanup on stack deletion

Test results:

Safe prompt (What is Amazon S3?) → full response
Violating prompt (What stocks should I buy?) → blocked with guardrail_intervened

TypeScript / AWS CDK

…count-level enforcement pattern Creates a Bedrock Guardrail with content and topic filters, versions it, and enables account-level enforcement via AwsCustomResource. Test Lambda demonstrates automatic guardrail enforcement on all Bedrock calls without specifying guardrailIdentifier. Key features: - Account-level guardrail enforcement via PutEnforcedGuardrailConfiguration - AwsCustomResource for SDK commands not in Lambda runtime - Content filters (HATE, INSULTS, SEXUAL, VIOLENCE, MISCONDUCT, PROMPT_ATTACK) - Denied topic filter (investment advice) - Test Lambda showing safe vs blocked responses - Automatic cleanup on stack deletion

Replace wildcard resource with specific inference profile ARN and foundation-model/* for least-privilege IAM.

NithinChandranR-AWS · 2026-04-28T08:10:21Z

Hi @biswanathmukherjee — this Bedrock Guardrails account-level enforcement pattern covers the April 2026 GA launch. Deployed and tested — safe prompts pass, violating prompts blocked without any guardrail specified in the API call. Ready for review.

NithinChandranR-AWS · 2026-04-30T03:57:17Z

Hi @biswanathmukherjee 👋 Friendly nudge — this pattern is ready for review. Deployed and tested end-to-end on a live AWS account. Would appreciate a look when you have time. Thank you!

NithinChandranR-AWS · 2026-05-08T04:02:06Z

Hi @biswanathmukherjee 👋 This shows Bedrock Guardrails account-level enforcement (April 2026 GA) — a unique feature where guardrails apply to ALL Bedrock calls account-wide without code changes. First pattern for this new capability.

bfreiberg · 2026-06-02T10:24:19Z

@@ -0,0 +1,130 @@
+# Bedrock Guardrails Account-Level Enforcement


Please make sure to use the full service name on first mentions.

Sorry about that. updated to "Amazon Bedrock Guardrails" on first mention throughout.

bfreiberg · 2026-06-02T10:25:02Z

The folder name makes it sound like this is a "cross-account" pattern but the README only talks about inside an account. Can you please clarify

The folder name reflects the cross-account extension use case (via Organization RCPs) which the README describes in the Important Notes section. The pattern itself deploys single-account enforcement as the foundation -- then explains how to extend cross-account via RCP. I've kept the README focused on what the code actually does while noting the cross-account path. Happy to rename the folder if you'd prefer something like bedrock-guardrails-enforcement-cdk?

bfreiberg · 2026-06-02T10:25:39Z

+
+    // Test Lambda
+    const testFn = new lambda.Function(this, 'TestFunction', {
+      runtime: lambda.Runtime.NODEJS_20_X,


use most recent runtime version

Updated to NODEJS_22_X.

bfreiberg · 2026-06-02T10:26:33Z

+    }));
+
+    testFn.addToRolePolicy(new iam.PolicyStatement({
+      actions: ['bedrock:ApplyGuardrail'],


Is that necessary? Shouldn't that automatically be applied?

You're right. with account-level enforcement the guardrail is applied automatically by the service, the caller doesn't need explicit ApplyGuardrail permission. Removed.

bfreiberg · 2026-06-02T10:27:14Z

@@ -0,0 +1,130 @@
+# Bedrock Guardrails Account-Level Enforcement
+
+This pattern deploys an Amazon Bedrock Guardrail with content and topic filters, enforces it at the account level so ALL Bedrock API calls are automatically guarded, and provides a test Lambda that demonstrates the enforcement without specifying any guardrailIdentifier.


Suggested change

This pattern deploys an Amazon Bedrock Guardrail with content and topic filters, enforces it at the account level so ALL Bedrock API calls are automatically guarded, and provides a test Lambda that demonstrates the enforcement without specifying any guardrailIdentifier.

This pattern deploys an Amazon Bedrock Guardrail with content and topic filters, enforces it at the account level so ALL Bedrock API calls are automatically guarded, and provides a test AWS Lambda function that demonstrates the enforcement without specifying any guardrail identifier.

Applied your suggestion, thanks.

bfreiberg · 2026-06-02T10:27:38Z

+* [Create an AWS account](https://portal.aws.amazon.com/gp/aws/developer/registration/index.html) if you do not already have one and log in. The IAM user that you use must have sufficient permissions to make necessary AWS service calls and manage AWS resources.
+* [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) installed and configured
+* [Git Installed](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
+* [Node.js 18+](https://nodejs.org/en/download/) installed


update to a non-EOL version

Updated to Node.js 20+.

bfreiberg · 2026-06-02T10:28:06Z

+
+1. **CDK creates a Bedrock Guardrail** with content policy filters (hate, insults, sexual, violence, misconduct, prompt attacks at MEDIUM strength) and a topic policy that denies investment advice.
+
+2. **An AwsCustomResource creates a guardrail version** — required before enforcement can be enabled.


Why is a custom resource necessary here?

Hi Ben, Thank you for reviewing this request. CloudFormation doesn't have a native resource type for CreateGuardrailVersion or PutEnforcedGuardrailConfiguration yet : these are API-only operations. AwsCustomResource lets us call them declaratively during stack lifecycle without writing a full Lambda handler.

bfreiberg · 2026-06-02T10:28:40Z

+- **inputTags deprecation:** The `inputTags` parameter in the enforcement configuration is being deprecated in favor of `selectiveContentGuarding`. This pattern uses `IGNORE` for inputTags as a placeholder.
+
+----
+Copyright 2025 Amazon.com, Inc. or its affiliates. All Rights Reserved.


Fixed to 2026.

bfreiberg · 2026-06-02T10:31:16Z

where is this file used/invoked?

It's not -- dead code from an earlier custom resource approach before I switched to AwsCustomResource. Deleted.

bfreiberg · 2026-06-02T10:31:20Z

where is this file used/invoked?

Same -- leftover from the custom resource approach. Deleted.

julianwood assigned biswanathmukherjee and julianwood Apr 20, 2026

fix(iam): scope bedrock:InvokeModel to inference profile ARN

b20a03c

Replace wildcard resource with specific inference profile ARN and foundation-model/* for least-privilege IAM.

biswanathmukherjee assigned bfreiberg and unassigned biswanathmukherjee May 6, 2026

bfreiberg requested changes Jun 2, 2026

View reviewed changes

bfreiberg mentioned this pull request Jun 2, 2026

New pattern - apigw-lambda-bedrock-guardrails-cdk #3113

Open

fix: address review feedback -- full service names, Node 22, remove d…

b1e3785

…ead code, copyright 2026

		@@ -0,0 +1,130 @@
		# Bedrock Guardrails Account-Level Enforcement

		@@ -0,0 +1,130 @@
		# Bedrock Guardrails Account-Level Enforcement

		This pattern deploys an Amazon Bedrock Guardrail with content and topic filters, enforces it at the account level so ALL Bedrock API calls are automatically guarded, and provides a test Lambda that demonstrates the enforcement without specifying any guardrailIdentifier.


		1. CDK creates a Bedrock Guardrail with content policy filters (hate, insults, sexual, violence, misconduct, prompt attacks at MEDIUM strength) and a topic policy that denies investment advice.

		2. An AwsCustomResource creates a guardrail version — required before enforcement can be enabled.

	Copyright 2025 Amazon.com, Inc. or its affiliates. All Rights Reserved.
	Copyright 2026 Amazon.com, Inc. or its affiliates. All Rights Reserved.

Conversation

NithinChandranR-AWS commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bedrock Guardrails Account-Level Enforcement

Uh oh!

NithinChandranR-AWS commented Apr 28, 2026

Uh oh!

NithinChandranR-AWS commented Apr 30, 2026

Uh oh!

NithinChandranR-AWS commented May 8, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

NithinChandranR-AWS Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

NithinChandranR-AWS Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

NithinChandranR-AWS Jun 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

NithinChandranR-AWS commented Apr 20, 2026 •

edited

Loading

NithinChandranR-AWS Jun 2, 2026 •

edited

Loading

NithinChandranR-AWS Jun 2, 2026 •

edited

Loading

NithinChandranR-AWS Jun 2, 2026 •

edited

Loading