A break-glass human administrator needs console access in an emergency, while an EC2 fleet needs permissions to read objects from a specific S3 bucket. How should those identities typically be modeled?
Select an answer to reveal the explanation.
Short Explanation
People who occasionally need a console login map cleanly to IAM users (especially break-glass). Servers should not get long-lived user keys stuffed on disk — attach an instance role so EC2 picks up temporary credentials automatically.
Full Explanation
IAM users represent people (or long-lived human identities) when needed; IAM roles are preferred for AWS resources such as EC2 instances so applications obtain temporary credentials from the instance profile. Roles avoid embedding long-term keys on instances. Root should remain unused for both patterns in daily operations.