Console Overview

The Stacktape Console is a web application for the organizations, projects and stages you deploy with Stacktape. It shows deployment activity, incidents, logs, metrics, traces, error tracking, security findings and AWS costs, and it manages members, alert channels, budgets, secrets, SSM parameters, AWS account connections and domains.

What the Console does

Projects represent your applications, typically one per Git repository. Each project can have multiple stages (isolated deployments such as production, staging or dev), each with its own resources. A stage is deployed from a Stacktape configuration that describes which resources to create.

From the Console you can:

The Console complements the Stacktape CLI. You deploy with stacktape deploy, and Git provider connections can deploy automatically from your repositories. Alarms, uptime checks and synthetic tests are defined in the Stacktape configuration and go live when the stack is deployed. The Activity page lists recorded CLI operations: deploys, deletes, scripts, bucket syncs and other commands.

Console navigation

The sidebar starts with Overview and Incidents, followed by five groups. Some items appear only when your role has the required permission; see Permission-gated navigation. Incidents, Error tracking, Posture, Vulnerabilities and Alarms show a count badge when there is something to look at.

GroupPagesWhat it covers
TopOverview, IncidentsDefault dashboard and the incident queue
OrganizationProjects, Runners, Activity, Members, Audit log, Single sign-on, CostsProjects and stages, the EC2 runners that run Git deploys and GitHub Actions jobs, CLI operation history, members and roles, the audit log, single sign-on and SCIM, cost tracking
ObservabilityLogs, Metrics, Traces, Uptime, Synthetics, Error trackingLogs, metrics, traces, uptime checks, synthetic tests, runtime errors
SecurityOverview, Posture, Vulnerabilities, Exposure, GuardrailsSecurity score per stack, configuration findings, vulnerable packages, what the internet can reach, guardrails
AlertingChannels, Sent alerts, Alarms, BudgetsAlert channels and their notification rules, sent alerts, alarm state, budgets and the alerts they sent
ConfigurationSecrets, SSM parameters, AWS accounts, DomainsSecrets, SSM parameters, AWS account connections, custom domains

The profile menu in the header opens Account (your account settings), API keys, Subscription plans, Billing, Third-party providers and Git connections.

The Overview route

The Overview page (/overview) is the Console's default route for the selected organization. Use the sidebar to open the detailed pages, such as Projects, Incidents, Costs or Error tracking.

Getting started

This walkthrough covers the path from first login to viewing a deployed stage.

  1. Sign in. The Console opens on the Overview page (/overview).
  2. Connect an AWS account. Open AWS accounts in the Configuration group and click Connect AWS account. Stacktape uses a cross-account IAM role, so you do not manage AWS credentials yourself. See Connecting your AWS account.
  3. Deploy a stage. Run stacktape deploy, or connect a Git provider from Git connections in the profile menu and set up GitOps for push-to-deploy.
  4. View your stage. Open Projects in the Organization group and select your project to see its stages and deployment activity.

Common tasks

Viewing deployment activity

Open Activity in the Organization group. The page lists Stacktape CLI operations across your organization, so you can see who ran deploys, deletes, scripts, bucket syncs and other recorded commands.

For each recorded operation, the CLI sends the command, the project, stage, region and AWS account, the Git branch, commit and repository URL, the Stacktape version, timing and the result. It also sends the flags that name the target and change how the command runs, such as --stage, --region, --config, --full, --auto-rollback, --no-cache, --target-version, --script-name, --resource-name and --bucket-id. Flags whose value is free-form input are never sent: --docker-args, script --env values, commands, SDK inputs, secret values and API keys stay on your machine or CI runner.

Managing secrets

Open Secrets in the Configuration group to manage sensitive values stored in AWS Secrets Manager. Secrets created here can be referenced in your Stacktape configuration. The page requires the secrets:view permission. See Secrets.

Managing SSM parameters

Open SSM parameters in the Configuration group to manage values stored in AWS Systems Manager Parameter Store. Use parameters for non-sensitive configuration your workloads need at runtime, such as feature flags or endpoint URLs. Click New parameter to add one. The page requires the ssm-params:view permission.

Setting up alarms

Alarms are defined in the Stacktape configuration, in the alarms list of a resource, and are created when the stack is deployed. The Alarms page in the Alerting group shows the current state of the CloudWatch alarms in your connected AWS accounts. See Alarms.

Alarm rules created in the Console earlier are legacy. They are listed under Legacy alarm rules on the Alarms page and keep applying to matching deployments until the stack's configuration defines its alarms. Run stacktape alarm export to move them into your configuration.

Tracking runtime errors

The Error tracking page in the Observability group is an error inbox for your deployed workloads. Stacktape reads runtime errors from your logs and groups repeated occurrences into one entry per distinct error and resource. Error tracking is on for every stage by default; a stack turns it off or limits it to some stages with deploymentConfig.errorTracking. The page requires the issues:view permission. See Error tracking.

Inviting members

Open Members in the Organization group and click Invite member. Each member has a role that determines what they can view and change. The page requires the members:view permission. See Team and access control.

Setting budgets

Open Budgets in the Alerting group and click New budget. Each budget monitors one connected AWS account for the calendar month. Stacktape creates the AWS budget when you save it and removes it when you delete the budget. The Alerts sent section on the same page lists the budget alerts that were sent. See Budgets.

Configuring alert channels and notification rules

Channels are the destinations where alerts are delivered, such as a Slack channel, an email address or a webhook. Open Channels in the Alerting group and click New alert channel. The new channel's page opens; click New rule there to choose which events (for example a failed deployment, an opened incident or a changed secret) it receives. Adding rules requires the org:manage-notifications permission. Sent alerts lists every alert that was sent and its delivery status per channel.

Permission-gated navigation

The Console uses role-based access control. Sidebar items are hidden when your role lacks the required permission:

Navigation itemRequired permission
Incidentsincidents:view
Membersmembers:view
Audit logaudit-log:view (Owners and Admins)
Single sign-onsso:manage (Owners only)
Costsorg:view-billing
Error trackingissues:view
Security group (Overview, Posture, Vulnerabilities, Exposure, Guardrails)security:view
Alarmsorg:manage-alarms
Budgetsorg:manage-budgets
Secretssecrets:view
SSM parametersssm-params:view
Domainsdomains:manage

Overview, Projects, Runners, Activity, Logs, Metrics, Traces, Uptime, Synthetics, Channels, Sent alerts and AWS accounts are not filtered by permission in the sidebar. Every role that sees the Security group can read Guardrails; only owners and admins (org:manage-guardrails) can change them.

If a sidebar item is missing, your role may not include the required permission. Ask your organization's owner or admin to adjust your access. See Team and access control for role details.

Troubleshooting

Cost data is not appearing

Cost reports are generated daily from AWS Cost and Usage Reports and may take up to a day to appear. If the Costs page shows no data, check that you have a connected AWS account and allow up to 24 hours for data to arrive.

An alarm does not exist in AWS

Alarms are created when the stack is deployed. After you add an alarm to a resource's alarms list, run stacktape deploy for the target stage. Legacy Console alarm rules also take effect only on the next deployment of each matching stage.

The Error tracking page is empty despite errors in logs

A stack reports errors only after it has been deployed with Stacktape v4, because the log subscriptions are added during deployment. Click Settings on the Error tracking page to open Error tracking settings: it shows whether error tracking is on for the organization and lists each deployed stack with whether its last deployment wired error tracking. Also check that the stack's deploymentConfig.errorTracking does not turn it off for that stage, and that the resource does not use logging.logClass: infrequent-access. See Error tracking.

Some sidebar items are permission-gated. If you don't see an item (for example, Costs or Alarms), your role may not include the required permission. See the permission-gated navigation table or ask your organization admin.

Console Overview FAQ

Do I need the Console to use Stacktape?

No. API keys let you authenticate with Stacktape from the CLI or CI/CD pipelines, and stacktape deploy does the deploying. The Console adds member access, cost visibility, incidents, error tracking, security findings, budgets and guardrails on top. Most teams use both: the CLI (directly or through GitOps) for deploying, and the Console for visibility and operational control.

Does Stacktape deploy into my own AWS account?

Yes. Stacktape uses a cross-account IAM role to manage resources in your AWS account, so you never hand over long-lived AWS credentials. Connect more accounts from AWS accounts in the Configuration group. See Connecting your AWS account for the required role.

Where do I configure alarms?

In the Stacktape configuration, in the alarms list of each resource. The alarms are created when the stack is deployed. The Console's Alarms page shows their state. Alarm rules created in the Console earlier are listed under Legacy alarm rules; export them into your configuration with stacktape alarm export.

How does Stacktape track AWS costs, and why is the Costs page empty?

The Costs page breaks down AWS costs by project and stage, generated daily from AWS Cost and Usage Reports. New data can take up to a day to appear, so an empty page usually means a recently connected AWS account or reports that haven't arrived yet. See Managing costs for budgets and optimization tips.

Why is a sidebar item missing for me?

The Console uses role-based access control, and several sidebar items are permission-gated. For example, Members requires members:view, Costs requires org:view-billing, and Alarms and Budgets require the matching org:manage-* permission. If an item is missing, ask your organization's owner or admin to adjust your role. See Team and access control.