Issues view
ZapStack groups issues by fix type rather than listing them individually. If 12 EC2 instances are idle, you see one row (“12 Idle EC2 Instances”) not 12 separate entries. Each row shows the service icon, fix title, effort and category badges, a fixes-implemented counter (e.g. 4/12), and the remaining estimated monthly saving.Grouping
Use the Group by selector to reorganise the view:| Option | Description |
|---|---|
| Effort | Group by Easy / Medium / Hard (default) |
| AWS Account | Group by the account the resources belong to |
| Service | Group by AWS service (EC2, RDS, Lambda, etc.) |
Drilling in
Click any row to open the Fixes view for that check type. From there you can see every impacted resource, and click any resource row to open a detail panel at the bottom of the screen with resource information and evidence charts.
Key properties
Types
ZapStack categorises issues by the kind of change required:| Category | What it involves |
|---|---|
 Reconfigure | Change settings without replacing resources |
 Change architecture | Relaunch your resources with a different CPU architecture. |
 Rightsize | Adjust resource size to match actual usage. |
 Best practise | Implement AWS-recommended configurations. |
 Cleanup | Delete unused resources. |
 Reservation | Purchase reserved capacity for steady workloads. |
Effort
Issues are rated by the effort to fix them:| Level | Description |
|---|---|
 Easy | Quick changes with minimal risk. Can typically be done in minutes with no downtime. |
 Medium | Moderate complexity. May require planning, testing, or a maintenance window. |
 Hard | Complex changes requiring careful consideration, potential downtime, or architectural decisions. |
Status
| Status | What it means |
|---|---|
 Todo | Issue is open and needs to be addressed. |
 Done | You’ve resolved this issue on your infrastructure. |
 Hidden | Not shown in your Issues view. ZapStack will resurface it as Todo if it’s detected again. |
How the workflow works
Triaging new issues
When ZapStack finds a new cost-saving opportunity:Automatic status updates
ZapStack monitors your infrastructure and updates issue status automatically:| If this happens… | Status changes to… |
|---|---|
| A new issue is detected | Todo |
| ZapStack detects the issue is resolved | Hidden |
| A hidden issue is detected again | Todo |
Investigation
Each issue includes investigation data collected during scans, using CloudWatch metrics. Depending on the issue type, you may see metric charts showing resource utilization over time, the threshold values ZapStack uses to flag underutilization, and historical data showing the pattern over the analysis window. For an idle EC2 instance, you might see CPU utilization consistently below 5%, minimal network I/O, and a 14-day window confirming it’s not a temporary dip.If you see the resource is being used during specific periods, it may be worth investigating before taking action or hiding the issue.
Solutions
Each issue has one or more recommended solutions with step-by-step instructions. Every solution shows a title, category (Reconfigure, Rightsize, Cleanup, etc.), effort level, and estimated monthly saving. It also includes a description of the change, things to consider before implementing (dependencies, potential impacts), and instructions for multiple implementation methods.Implementation methods
AWS Console
AWS Console
Click-by-click steps with direct links to the resource in your AWS Console. Great for one-off changes or when you want to verify settings visually.
CLI
CLI
Ready-to-run AWS CLI commands you can copy and execute. Perfect for scripting or when you prefer working from the command line.
Terraform (coming soon)
Terraform (coming soon)
Infrastructure-as-code snippets for Terraform users. Ideal for managing changes through your existing IaC workflow.
Each method achieves the same outcome. Choose whichever fits your workflow.
Sync with third parties
Solutions include integrations to create follow-up tasks in your project management tools:| Tool | What it does |
|---|---|
 Jira | Create a Jira issue with the solution details pre-filled |
 Linear | Create a Linear issue linked to the ZapStack issue. |