A municipal trail-register kiosk should let the kiosk role call one Amazon Bedrock model and nothing else — not list buckets, not change IAM, not open every foundation model in the account. Which control is that?
Select an answer to reveal the explanation.
Short Explanation
Think of a trail kiosk that should call one Bedrock model and nothing else. That is least-privilege IAM. Admin-on-everything, a dashboard, and temperature are not that lock.
Full Explanation
The municipal trail-register kiosk should call one Amazon Bedrock model and nothing else—not list buckets, not change IAM, and not open every foundation model in the account. That is least-privilege IAM on who can invoke the model. The kiosk role gets only the invoke permission required for its job, shrinking blast radius if the kiosk is compromised or misconfigured.
An admin-on-everything role fails because over-privilege turns a public trail kiosk into a path to account-wide damage; a kiosk does not need every foundation model or IAM mutation rights. A dashboard title fails because charts are visualization, not authorization policy. Raising temperature so unused models close themselves fails because temperature is a decoding parameter and does not revoke unused model access.
Exam caveat: least privilege must cover both the identity that invokes Bedrock and any downstream tools or data the agent can reach—model invoke alone is incomplete if the role can still read sensitive buckets. Operational check: attach a narrow policy allowing invoke only on the named model ARN, run IAM Access Analyzer or a policy simulator against the kiosk role, and confirm denied actions for ListBuckets, IAM changes, and other foundation models.