A data account operates S3, IAM roles, and KMS keys.
Find resources that a different account could access unintentionally.
Which authorization approach is most appropriate?
Use IAM Access Analyzer to analyze external access and validate resource policies, then review findings with owners.
Detailed explanation
Names do not reveal resource-policy sharing.
Names do not reveal resource-policy sharing.
Usage history does not show all currently allowed access.
Usage history does not show all currently allowed access.
The analyzer reveals policy-based reachability even before a resource is used.
The analyzer reveals policy-based reachability even before a resource is used.
Deletion loses data instead of correcting the policy.
Deletion loses data instead of correcting the policy.
Check official documentation
Compare the following points with the official documentation.
AWS IAM Access Analyzer external access、policy validationの公式説明を確認する。
What to confirm
実際の利用ログと、ポリシー上可能な外部アクセスの違いを説明できる。
Key points
- Access Analyzer
- External access
- Policy validation
- Unintended sharing
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Allowed versus used
CloudTrail shows use; Access Analyzer shows policy-based reachability.
Finding management
Assign owners, expiry dates, and exception reasons for accepted findings.