AWS bedrock documentation change
Summary
Added three new workflow types (GENERATE_POLICY_SCENARIOS, RESOLVE_POLICY_AMBIGUITIES, ITERATIVELY_REFINE_POLICY) with detailed documentation about their purposes, inputs, and use cases.
Security assessment
The new workflows enhance policy validation capabilities (scenario generation, ambiguity resolution, refinement) which directly support security policy creation and maintenance. This qualifies as adding security documentation since it details features for improving policy accuracy and reliability.
Diff
diff --git a/bedrock/latest/userguide/kiro-cli-automated-reasoning-policy.md b/bedrock/latest/userguide/kiro-cli-automated-reasoning-policy.md index 475edd0e8..61ced785d 100644 --- a//bedrock/latest/userguide/kiro-cli-automated-reasoning-policy.md +++ b//bedrock/latest/userguide/kiro-cli-automated-reasoning-policy.md @@ -208,0 +209,3 @@ Copy the following content and save it in a Markdown file in your project folder + - GENERATE_POLICY_SCENARIOS Workflow + - RESOLVE_POLICY_AMBIGUITIES Workflow + - ITERATIVELY_REFINE_POLICY Workflow @@ -261 +264 @@ Copy the following content and save it in a Markdown file in your project folder - - `start-automated-reasoning-policy-build-workflow` - Start build process. Valid `--build-workflow-type` values: `INGEST_CONTENT`, `REFINE_POLICY`, `IMPORT_POLICY`, `GENERATE_FIDELITY_REPORT`. Supports optional `--client-request-token` (idempotency token, passed as header). + - `start-automated-reasoning-policy-build-workflow` - Start build process. Valid `--build-workflow-type` values: `INGEST_CONTENT`, `REFINE_POLICY`, `IMPORT_POLICY`, `GENERATE_FIDELITY_REPORT`, `GENERATE_POLICY_SCENARIOS`, `RESOLVE_POLICY_AMBIGUITIES`, `ITERATIVELY_REFINE_POLICY`. Supports optional `--client-request-token` (idempotency token, passed as header). @@ -291,0 +295,3 @@ Copy the following content and save it in a Markdown file in your project folder + 5. **GENERATE_POLICY_SCENARIOS** - Generate test scenarios from policy rules + 6. **RESOLVE_POLICY_AMBIGUITIES** - Resolve translation ambiguities in variable descriptions and type definitions + 7. **ITERATIVELY_REFINE_POLICY** - Refine a policy using source documents and optional natural language feedback @@ -341,0 +348,19 @@ Copy the following content and save it in a Markdown file in your project folder + ### GENERATE_POLICY_SCENARIOS Workflow + - **Purpose**: Generate test scenarios from policy rules to validate rule correctness + - **Input**: Policy definition only + - **Use Cases**: Generating test scenarios for review, identifying rule issues + - **Content Structure**: No `workflowContent` required — only `policyDefinition` + - **Post-Workflow**: Use `GetAutomatedReasoningPolicyNextScenario` to fetch generated scenarios one at a time + + ### RESOLVE_POLICY_AMBIGUITIES Workflow + - **Purpose**: Automatically resolve translation ambiguities in variable descriptions and type definitions + - **Input**: Policy definition only + - **Use Cases**: Fixing TRANSLATION_AMBIGUOUS test results, improving variable descriptions for clearer translation + - **Content Structure**: No `workflowContent` required — only `policyDefinition` + + ### ITERATIVELY_REFINE_POLICY Workflow + - **Purpose**: Refine an existing policy using a source document and optional natural language feedback + - **Input**: Policy definition + source document + optional feedback + - **Use Cases**: Updating a policy when the source document changes, guiding refinement with specific instructions + - **Content Structure**: `workflowContent.iterativeRefinementContent.documents[]` + optional `workflowContent.iterativeRefinementContent.feedback` +