What's new?

• The AWS > Bedrock > Guardrail > Settings control now reports one row per setting, showing whether each is OK, in Alarm or skipped, with the guardrail's current value and the value your policy expects. Settings you have not configured are listed as skipped.

Bug fixes

• Enforce: Configured no longer clears parts of a guardrail's configuration that none of your sub-policies manage, such as the actions and enablement flags AWS keeps on content filters, denied topics and PII entities. Those are now left as they are, and the control no longer treats them as a mismatch, so a guardrail that already matches your policies stays OK instead of being re-enforced on every cycle.