Governance guide

How to govern Operation in AWS Bedrock

A step-by-step guide to governing Operation in AWS Bedrock with Rencore: detect, review by owner and severity, and remediate with an audit trail.

Definition

Governing Operation in AWS Bedrock means finding where it goes wrong, reviewing the findings by owner and severity, and remediating with an audit trail. Rencore covers this concern for AWS Bedrock with the pre-built controls below, so it becomes a repeatable check rather than a one-off cleanup. The steps that follow apply the same detect, review, remediate loop to Operation.

Steps

  1. Inventory AWS Bedrock

    Connect AWS Bedrock and let Rencore build a continuous inventory of its resources, owners, and configuration, so governance starts from what exists rather than a stale export.

  2. Detect with policies

    Turn on the pre-built policies that cover Operation in AWS Bedrock to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.

  3. Review by owner and severity

    Use the AWS Bedrock reports to review findings by owner, category, and severity, and to share them with stakeholders who do not have a seat in the platform.

  4. Remediate and automate

    Apply automations to fix findings at scale, route sensitive changes through approvals, and keep every action reversible and logged for the audit trail.

AWS Bedrock controls for Operation

Grounded in the Rencore catalog. See the full AWS Bedrock catalog on the AWS Bedrock connector page.

  • Agent is live and callable

    Agents in PREPARED state are callable, raising the likelihood that any weakness is exploited

    Severity: Medium
  • Flow is live and invocable

    Flows in Prepared state are invocable, raising the likelihood that any weakness is exploited

    Severity: Medium
  • AWS Bedrock Agent in failed state

    Detects agents with FAILED or NOT_PREPARED status

    Severity: High
  • AWS Bedrock Flow in failed state

    Detects flows with Failed status

    Severity: High
  • AWS Bedrock Knowledge Base in failed state

    Detects knowledge bases with FAILED status

    Severity: Medium
  • AWS Bedrock Agent action group disabled

    Detects agent action groups that are currently disabled

    Severity: Medium
  • AWS Bedrock Agent using disabled knowledge base

    Detects agent knowledge base associations with disabled state

    Severity: High
  • AWS Bedrock KB data source unavailable

    Detects knowledge base data sources in DELETING or DELETE_UNSUCCESSFUL state

    Severity: High
  • AWS Bedrock model customization job failed

    Detects model customization jobs with Failed status

    Severity: High
  • AWS Bedrock model evaluation job failed

    Detects model evaluation jobs with Failed status

    Severity: Medium
  • KB Data Sources by Status

    Shows the distribution of knowledge base data sources by status

  • Customization Jobs by Status

    Shows the distribution of model customization jobs by status

  • Agent Action Groups by State

    Shows the number of action groups grouped by enabled/disabled state

  • Delete AWS Bedrock Agent

    Automatically deletes an AWS Bedrock agent after approval

Explore the full AWS Bedrock governance catalog | All guides

Trusted by

MAPALBAMVille de LuxembourgWACKERGRUNDFOSAMGENOsramLufthansaThyssenKruppSunrisePattern