IdleLens

Security

How access works

You create an IAM role in your AWS account using our CloudFormation template. The role includes an External ID condition — a unique per-workspace value that prevents the confused-deputy problem — so even someone who discovers your role ARN cannot have IdleLens assume it without that value.

IdleLens assumes the role only during scans. It never stores your AWS credentials or the assumed-role session tokens. The role can be deleted from your AWS console at any time to revoke access instantly.

Exact permissions

The IAM policy is scoped to read-only Describe, List, Get, and CloudWatch actions. No Delete*, Stop*, Terminate*, Update*, Put*, or Create* actions appear in the policy — enforced by the policy itself, not just by convention.

What IdleLens stores

  • Your AWS account ID and connected region list
  • Resource IDs and metadata needed to describe findings (instance IDs, volume IDs, ARNs)
  • Resource tags, used to identify protected or exempted resources
  • CloudWatch metric evidence backing each finding
  • Estimated monthly cost per finding (list-price, ±15% accuracy)
  • Scan history and finding status (open / snoozed / resolved)

What IdleLens never stores

  • Application data, source code, or database contents
  • Secrets, credentials, or API keys
  • S3 object contents or EBS volume data
  • Customer workload traffic or application logs
  • AWS assumed-role session tokens (used transiently during scan only)

Data retention

Scan results and findings are retained for 90 days. To request earlier deletion of your workspace data, email support@idlelens.com.

Responsible disclosure

Found a security issue? Email support@idlelens.com directly. We respond within one business day during the pilot phase.