Operators need to read objects in one specific S3 bucket.
They must not access other buckets or perform delete operations.
Which design is most appropriate?
Grant a policy limited to the required bucket and read actions so the operator receives least privilege.
Detailed explanation
This exposes the data to the public and removes access control.
This exposes the data to the public and removes access control.
This allows unnecessary services and delete operations and violates least privilege.
This allows unnecessary services and delete operations and violates least privilege.
Limiting both resources and actions minimizes the permissions granted.
Limiting both resources and actions minimizes the permissions granted.
Shared keys make individual auditing and safe rotation difficult.
Shared keys make individual auditing and safe rotation difficult.
Check official documentation
Compare the following points with the official documentation.
IAM policy least privilegeの公式説明を確認する。
What to confirm
対象リソースと操作を絞ったポリシーを設計できる。
Key points
- IAM policy
- Least privilege
- S3 read access
Notes
- Environment: AWS公式IAMドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Scope
A narrowly scoped policy is safer than a broad administrator policy.
Auditability
Individual identities and non-shared credentials preserve accountability.