Topic lessonTopic: Bedrock inference, retrieval and operating decisions
Set approval and permission boundaries for Bedrock Agents
Separate reads, changes and approvals. Define permitted actions and resources and distinguish a completion message from evidence of execution.
Define read scope and hold conditions for a synthetic SQL Server runbook assistant.
The cases use fictional inputs.
What to predict
Separate reads, changes and approvals. Define permitted actions and resources and distinguish a completion message from evidence of execution.
- Request → AuthorizationAlign conditions
- Authorization → ActionCompare outcomes
- Action → AuditVerify the decision
- Request
- A permitted synthetic procedure is requested
- Authorization
- Request targets an unrelated store
- Action
- A read-only flow receives a database change request
- Audit
- Only text claims completion
Compare the cases
| Case | Conditions | Decision |
|---|---|---|
| an approved lookup | A permitted synthetic procedure is requested | Verify read access to the intended resource |
| a request outside scope | Request targets an unrelated store | Reject before execution and record scope |
| a proposed change | A read-only flow receives a database change request | Hold and route to the approved process |
| missing evidence | Only text claims completion | Verify actual execution from independent evidence |
Acceptance and limits
This design covers synthetic resource reads. Hand change requests to the owner’s approval process and audit actual accesses.
Define permitted actions and targets.
Exercise out-of-scope and change requests.
Reconcile the response and execution record.
Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Define permitted actions and targets.
- Exercise out-of-scope and change requests.
- Reconcile the response and execution record.
Check your understanding: Define read scope and hold conditions for a synthetic SQL Server runbook assistant.
This design covers synthetic resource reads. Hand change requests to the owner’s approval process and audit actual accesses.
Reconcile the response and execution record.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsSeparate reads, changes and approvals. Define permitted actions and resources and distinguish a completion message from evidence of execution.
Used in this lessonWhat to predict Acceptance and limits