INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Define read scope and hold conditions for a synthetic SQL Server runbook assistant.

Prerequisite

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.

From conditions to the decision
From conditions to the decision1: Request — Align conditions — Authorization. 2: Authorization — Compare outcomes — Action. 3: Action — Verify the decision — Audit123RequestAuthorizationActionAuditFrom conditions to the decision1: Request — Align conditions — Authorization. 2: Authorization — Compare outcomes — Action. 3: Action — Verify the decision — Audit123RequestAuthorizationActionAudit
  1. Request → AuthorizationAlign conditions
  2. Authorization → ActionCompare outcomes
  3. 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

Synthetic observations
CaseConditionsDecision
an approved lookupA permitted synthetic procedure is requestedVerify read access to the intended resource
a request outside scopeRequest targets an unrelated storeReject before execution and record scope
a proposed changeA read-only flow receives a database change requestHold and route to the approved process
missing evidenceOnly text claims completionVerify 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.

Which decision applies to an approved lookup?
Read the answer and reason

Answer: Verify read access to the intended resource · an approved lookup: A permitted synthetic procedure is requested → Verify read access to the intended resource

Which decision applies to a request outside scope?
Read the answer and reason

Answer: Reject before execution and record scope · a request outside scope: Request targets an unrelated store → Reject before execution and record scope

Which decision applies to a proposed change?
Read the answer and reason

Answer: Hold and route to the approved process · a proposed change: A read-only flow receives a database change request → Hold and route to the approved process

Check, then explain in your own words

  1. Define permitted actions and targets.
  2. Exercise out-of-scope and change requests.
  3. 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.