AWS bedrock documentation change
Summary
Added JSON code block formatting markers to multiple policy examples
Security assessment
The changes format existing security policy examples but do not introduce new security content or address vulnerabilities. They improve documentation structure for security configurations.
Diff
diff --git a/bedrock/latest/userguide/agents-permissions.md b/bedrock/latest/userguide/agents-permissions.md index 140271910..1c7f6a5cf 100644 --- a//bedrock/latest/userguide/agents-permissions.md +++ b//bedrock/latest/userguide/agents-permissions.md @@ -62,0 +63,6 @@ As a best practice for security purposes, replace the `*` with specific agent ID +JSON + + +**** + + @@ -175,0 +183,6 @@ If you associate a [Provisioned Throughput](./prov-throughput.html) with an alia +JSON + + +**** + + @@ -197,0 +212,6 @@ If you enable [multi-agent collaboration](./agents-multi-agent-collaboration.htm +JSON + + +**** + + @@ -219,0 +241,6 @@ If you associate a [guardrail](./guardrails.html) with your agent, attach the fo +JSON + + +**** + + @@ -238,0 +267,6 @@ If you enable [Enable code interpretation in Amazon Bedrock](./agents-enable-cod +JSON + + +**** + + @@ -263,0 +299,6 @@ Follow the steps at [Using resource-based policies for Lambda](https://docs.aws. +JSON + + +**** + +