Tools for your AWS account
Tools that look across your account: Cost by resource, the waste finder, VPC IP usage, Find an IP, Open by ARN, Schedules, Service quotas, an S3 bucket audit and an IAM access audit.
Open Services → Tools (the three you use most are listed on the Services tab; All tools shows the rest). Every tool only reads, so they all work on the free plan and in the demo. Where a tool suggests a fix, the button is the app's usual action, with the same Pro check, confirmation and activity log as anywhere else.







Cost by resource and Waste finder
Cost by resource ranks EC2, RDS, EBS, NAT gateways, load balancers, Lambda and Fargate by estimated monthly cost (see See what each resource costs). The Waste finder lists resources that cost money for nothing (see Find waste).
VPC IP usage
Each VPC with its subnets: CIDR block, Availability Zone, free addresses (AWS's AvailableIpAddressCount) against the usable size (the block minus the 5 addresses AWS keeps in every subnet), and a bar. Subnets at 80% or more are flagged: a full subnet stops new instances, Lambda network interfaces and Fargate tasks from launching there.
It also finds CIDR blocks that overlap between VPCs, in this region or, with All regions or All accounts, across them. For each overlap it says whether it matters today: both VPCs attached to the same transit gateway (a route can only point at one of them), a peering connection, or not connected yet (you won't be able to peer them).
Find an IP
Enter an IPv4 or IPv6 address. The app searches network interfaces (private, public and IPv6 addresses), Elastic IPs and NAT gateways, and names the owner: an EC2 instance, NAT gateway, load balancer, Lambda function, ECS task, VPC endpoint or an idle Elastic IP, with a button to open it. With a wider scope it searches every region or account, and switches to the right one when you open a result.
If nothing in the account uses the address, it checks AWS's published IP ranges (ip-ranges.json, from cloudconsole.dev, kept for a day) and says which AWS service and region the range belongs to, or that it isn't AWS address space at all. The address itself is never sent anywhere.
Open by ARN
Paste or scan an ARN from a log line, alarm, CloudTrail event or policy. It's checked with the same parser as the ARN parser, then opened on the matching screen (a hand-built one, or the read-only catalogue screen), switching account and region first if you've connected that account. When it can't open something, such as an assumed-role session or an ARN with wildcards, it says why.
Schedules
EventBridge rules with a schedule expression (on every event bus) and EventBridge Scheduler schedules, on one timeline for the next 24 hours or 7 days, in your phone's time zone, with each job's targets. Expressions are worked out exactly as AWS does, by the same rules as the cron builder: rules in UTC, schedules in their own time zone (including L, W, # and daylight saving changes), flexible time windows shown as "within N min". Frequent jobs are folded into one row per day, and disabled schedules are listed separately.
Service quotas
The quotas that cause outages when they're reached: On-Demand and Spot vCPUs by family, Elastic IPs, VPCs, NAT gateways per Availability Zone, network interfaces, Lambda concurrent executions, Fargate vCPUs, EBS storage, Application Load Balancers and CloudFormation stacks. Usage comes from CloudWatch AWS/Usage metrics where AWS publishes one; for Elastic IPs, VPCs, NAT gateways and load balancers the app counts them itself. Quotas at 80% or more are flagged. Request increase sends a quota increase request (Pro).
S3 bucket audit
Every bucket, read in its own region: Block Public Access (the bucket's and the account's), whether its bucket policy makes it public, versioning, default encryption, lifecycle rules and server access logging, with counts at the top and filters. The fixes are the S3 screen's own Block all public access and Turn on versioning (Pro).
IAM access audit
Active access keys older than 90 days, keys not used for 90 days or never used (once they're 90 days old), console users without MFA, and whether the root user has MFA or access keys. Deactivate is the IAM screen's own action (Pro, typed confirmation, and it can be reactivated).
Permissions
Every read here is in the AWS managed ReadOnlyAccess policy and in the CloudConsole read-only policy (Recommended permissions). If you use ViewOnlyAccess, add the extras listed there: it leaves out Scheduler, Service Quotas, most S3 bucket settings and iam:GetAccessKeyLastUsed. If one call is denied, the rest of the tool still works and says what's missing.
| Tool | IAM actions | In ReadOnlyAccess |
|---|---|---|
| VPC IP usage | ec2:DescribeVpcs, ec2:DescribeSubnets, ec2:DescribeVpcPeeringConnections, ec2:DescribeTransitGatewayVpcAttachments | Yes |
| Find an IP | ec2:DescribeNetworkInterfaces, ec2:DescribeAddresses, ec2:DescribeNatGateways, ec2:DescribeInstances, elasticloadbalancing:DescribeLoadBalancers | Yes |
| Schedules | events:ListEventBuses, events:ListRules, events:ListTargetsByRule, scheduler:ListSchedules, scheduler:GetSchedule | Yes |
| Service quotas | servicequotas:ListServiceQuotas, servicequotas:GetServiceQuota, cloudwatch:GetMetricData (plus the EC2 and ELB reads above for counted quotas) | Yes |
| S3 bucket audit | s3:ListAllMyBuckets, s3:GetBucketLocation, s3:GetBucketPublicAccessBlock, s3:GetBucketPolicyStatus, s3:GetBucketVersioning, s3:GetEncryptionConfiguration, s3:GetLifecycleConfiguration, s3:GetBucketLogging, s3:GetAccountPublicAccessBlock | Yes |
| IAM access audit | iam:GetAccountSummary, iam:ListUsers, iam:GetLoginProfile, iam:ListMFADevices, iam:ListAccessKeys, iam:GetAccessKeyLastUsed | Yes |
| Fixes (Pro) | servicequotas:RequestServiceQuotaIncrease, s3:PutBucketPublicAccessBlock, s3:PutBucketVersioning, iam:UpdateAccessKey | No (these are changes) |
Questions
Do the tools cost anything?
They are free in the app, including on the free plan. AWS bills CloudWatch GetMetricData requests beyond its free tier; Service quotas makes one request each time it loads.
Why does a subnet show fewer usable addresses than its size?
AWS reserves 5 addresses in every subnet: the network address, the VPC router, DNS, one for future use and the broadcast address. A /24 has 256 addresses and 251 usable.
Why is an address in AWS ranges but not found in my account?
It belongs to another AWS customer or to AWS itself, or to a resource your role can’t list. ip-ranges.json says which service and region a range is used by, not which account.
Email [email protected] with what you tried and any message the app showed. Don’t send access keys or secrets. We reply within two working days.