Reference

AWS IAM access model reference: federation, roles, MFA, least privilege, and Access Analyzer.

This is a working summary of the IAM model HelionFall assumes for modern AWS estates: federated human access, temporary credentials, role-based workload identity, MFA, and continuous permission review.

Search IAMOpen Security Domain
Core Model

What “good” usually looks like.

  • Human users authenticate through federation with temporary credentials.
  • Workloads use roles instead of embedded long-lived keys.
  • MFA protects human access and high-risk operations.
  • Least privilege is refined over time rather than assumed from broad managed policies.
  • Access Analyzer and regular reviews validate whether permissions remain justified.
Use This Page When

Identity design or cleanup work needs a quick compass.

  • Reviewing whether long-lived keys still exist where they should not.
  • Planning workload migration to roles.
  • Checking whether policy scope is broader than intended.
  • Building a better access review process across accounts.