IAM policy grants Action "*" on Resource "*"
A policy statement with "Action": "*" and "Resource": "*" grants full control of the account. Attached to a role a workload uses, it makes that workload as powerful as an administrator.
Why it matters
If the identity is compromised, a wildcard policy means there's nothing to contain the attacker — least privilege is what limits the blast radius.
Wildcards creep in from copied examples and "just make it work" fixes, then never get tightened.
How to check for it
- Review customer-managed policies for statements with Action "*" and Resource "*" (or service-level wildcards like s3:*).
- IAM Access Analyzer's unused-access findings highlight permissions that are granted but never used.
How to fix it
- Replace wildcards with the specific actions and resource ARNs the workload actually calls.
- Use Access Analyzer to generate a least-privilege policy from CloudTrail activity, then attach that.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- How do I know which permissions to keep?
- IAM Access Analyzer can build a policy from the identity's recent CloudTrail activity, so you keep only what's been used.