You started with one AWS account. Then you added a staging account because deploying to production was too risky. Then a client asked you to manage their AWS environment. Now you have 3-5 accounts, and monitoring them means logging into each one separately to check dashboards, review GuardDuty findings, and scan billing summaries. It takes 30 minutes, you do it once a week (if you remember), and you know things are slipping through the cracks.
Enterprise multi-account monitoring solutions cost $5,000-20,000/year. Here's how to get meaningful visibility across your accounts for under $100/month.
The Problem with Per-Account Monitoring
Most AWS monitoring tools are account-scoped. CloudWatch metrics live in the account that generated them. GuardDuty findings appear in each account's console. Cost Explorer shows data for one account at a time (unless you're using consolidated billing and viewing from the management account). This means a security finding in your staging account is invisible when you're looking at production, and a billing anomaly in a client account goes unnoticed until the monthly invoice surprises you.
Option 1: AWS Organizations + Consolidated Views (Free-$50/month)
If you own all the accounts, AWS Organizations provides basic multi-account governance for free. Set up an organization with your primary account as the management account and invite the others as members. This gives you:
Consolidated billing: One invoice, one Cost Explorer view with per-account filtering. You can see total spend across all accounts and drill into individual accounts. This alone makes billing monitoring across accounts dramatically easier.
Delegated administrator for GuardDuty: Designate one account to receive GuardDuty findings from all member accounts. One dashboard for all security findings across all accounts.
Config aggregator: Aggregate compliance findings from all accounts into a single view. See which accounts have compliance gaps without checking each one individually.
Cost: Free for Organizations itself. GuardDuty costs apply per-account based on data volume. Config costs apply per-account per-rule. Typical total for 3-5 small accounts: $30-50/month for GuardDuty + Config across all accounts.
Limitation: This approach requires the other accounts to be part of your organization. If you're managing a client's account, they probably don't want to join your AWS Organization. And even with these aggregation features, you're still checking multiple dashboards — GuardDuty, Config, Cost Explorer, and SES metrics are all separate.
Option 2: Cross-Account IAM Roles + Scripts ($0 tooling cost, time investment)
Create a read-only IAM role in each account that trusts your primary account. Write scripts that assume each role in sequence and pull key metrics: active GuardDuty findings, Config compliance summary, current month's spend, SES bounce rate, and service quota utilization.
A simple Bash script iterating over account profiles and calling the relevant APIs can produce a daily summary email or Slack message. This is the cheapest approach in dollar terms but requires ongoing maintenance as you add accounts, services, and checks.
Cost: $0 in tooling, but it costs your time to build and maintain. Realistic time investment: 4-8 hours to build, 1-2 hours/month to maintain.
Option 3: Vigilare Multi-Account Dashboard ($29-199/month)
Vigilare's Solo plan ($29/month) supports multiple AWS accounts. Connect each account by deploying the same read-only Terraform module. Each account appears in your dashboard with its own risk score, billing trend, and security findings. The dashboard provides the unified multi-account view that you'd otherwise need to build yourself.
For freelancers and agencies managing client accounts, the Agency plan ($199/month) adds client-level isolation, per-client billing reports, and the ability to share specific views with clients without giving them access to other accounts.
What you get: A single dashboard showing all accounts with per-account risk scores, correlated alerts across all accounts, billing monitoring with 5-minute detection across all accounts, and one Slack channel with alerts from all accounts tagged by account name.
Cost: $29/month for up to 5 accounts (Solo), $199/month for up to 20 accounts (Agency).
The Recommended Stack by Account Count
2-3 accounts (all yours): AWS Organizations (free) + GuardDuty delegated admin ($20-30/month) + Vigilare Solo ($29/month). Total: ~$50-60/month. You get consolidated billing, centralized security findings, and a unified health dashboard.
3-5 accounts (mix of yours and clients'): Vigilare Solo or Agency ($29-199/month) with per-account Terraform module deployment. Organizations for your own accounts; cross-account roles for client accounts. Total: $29-199/month depending on plan.
5+ accounts: At this scale, the time savings of an automated tool outweigh the cost. Vigilare Agency ($199/month) or an enterprise CSPM if compliance requirements demand it.
Related Reading
Protect your AWS accounts before it's too late
Vigilare monitors your AWS accounts for suspension risks — billing anomalies, IAM issues, GuardDuty findings, and more — and alerts you before AWS takes action.
Written by Viktor B.
Co-founder & CEO