Starting a Scan
From the Dashboard
- Navigate to your ZapStack dashboard
- Select the AWS account(s) you want to scan
- Click Run Analysis
- Monitor progress in real-time
Scheduled Scans
Configure automated scans to run on a schedule:- Go to Settings > Schedules
- Click Create Schedule
- Select accounts and frequency
- Save the schedule
Scan Options
Region Selection
By default, ZapStack scans all enabled regions. To limit regions:- Go to Settings > AWS Accounts
- Select the account
- Click Configure Regions
- Enable/disable specific regions
Check Selection
Enable or disable specific checks:- Go to Settings > Checks
- Toggle individual checks on/off
- Changes apply to future scans
Understanding Results
Finding States
| State | Description |
|---|---|
| Open | New finding, not yet addressed |
| Acknowledged | Finding reviewed, planned for action |
| Resolved | Finding addressed, will be verified on next scan |
| Ignored | Finding dismissed, won’t appear in future scans |
Severity Levels
| Severity | Typical Monthly Impact |
|---|---|
| High | $100+ potential savings |
| Medium | $25-100 potential savings |
| Low | Less than $25 potential savings |
Exporting Results
Export findings for reporting or integration:CSV Export
- View scan results
- Click Export > CSV
- Download the file
API Access
Use the API to programmatically access findings:Scan History
View previous scan results:- Go to Scans in the sidebar
- Select a previous scan
- Compare findings over time
Troubleshooting
Scan Stuck
If a scan appears stuck:- Check the IAM role permissions
- Verify network connectivity to AWS
- Contact support if the issue persists
Missing Resources
If expected resources don’t appear:- Verify the region is enabled for scanning
- Check IAM permissions include the service
- Ensure resources have appropriate tags (if filtering by tags)
Partial Results
If only some checks complete:- Review the scan log for errors
- Check for API throttling (common in large accounts)
- Consider scanning fewer regions simultaneously