AWS Control is a built-in Crew app that puts your connected AWS accounts on one surface. It ships disabled by default. Enable it from Apps > Library before use.
AWS Control covers four areas: reviewing account health, browsing and managing files in a private S3 drive, running cloud backups, and checking billing costs. Every paid service asks for your confirmation before its first use per account, and every change is on the record.
AWS Control opens on Overview. It shows connected accounts, key health, drive use, month-to-date spend, share links, and the backup schedule. Use the rail to open Files, Artifact library, Backup, or Share links. Each pane has its own URL, so you can return to the same view directly.
Open AWS Control and connect an account. Crew uses the AWS profile registry that the deploy engine maintains. Each connected account shows a health indicator (ok, degraded, or unknown) based on whether its configured profiles resolve to a live identity.
To remove an account, open that account's row overflow menu and choose Remove from AWS Control. This removes only the local registry entry and its consent grants. It does not modify accounts, resources, or data in AWS.
The Drive view is a private, versioned, owner-only S3 bucket scoped to your account. It is not a general S3 browser. The bucket is created only after you confirm it, and is hardened at creation with block public access, AES-256 server-side encryption, bucket owner enforced, and versioning enabled.
The Drive bucket hosts three sections on separate key prefixes:
drive/ prefix). Open images, video, audio, PDFs, and text in a preview dialog without downloading them. Search by file name or path across Files, choose Rename from an item's menu, drag to move items, drop files to upload, and delete with an inline confirmation.artifacts/ prefix). Reports, outputs, and files you have saved or published there.backup/ prefix); see the Backup section below.Share links always expire. Nothing is public unless you explicitly create a share.
The Backup view manages cloud snapshots of your Crew install.
Two backup kinds are supported:
backup/snapshots/ prefixbackup/sessions/Click Back up now in the Backup view. The backup continues if you navigate away from the page; return to Backup to see its current status.
A restore downloads the archive to the /restore/ directory on the gateway host and gives you the local path. It does not hot-swap live state directly. To apply the restore, run kirocrew restore with the downloaded path:
kirocrew restore ~/.kiro/crew/restore/<snapshot-file>.tar.gz
This follows the same replace or merge restore flow as a local snapshot. See Snapshot and restore for the full reference, including Replace-mode recovery.
A nightly backup toggle is available per account. The nightly loop runs in the background and is authorized by the toggle you set.
The Bill view shows month-to-date spend and a projected total for the current month, grouped by AWS service. Data comes from Cost Explorer and is cached daily (CE data lags approximately 24 hours). The cache age is shown alongside the figures.
The projection is local arithmetic extrapolating month-to-date over the full month. No AWS Budgets resources are created.
Every action in AWS Control follows these principles:
| Problem | Fix |
|---|---|
| App not visible in sidebar | Enable it from Apps > Library |
| Account shows degraded health | Check whether the AWS profile still resolves to a live identity; re-authenticate with aws sso login or aws configure as appropriate |
| Bill view shows no data | Confirm Cost Explorer is enabled for the account in the AWS Console |
| Drive shows no bucket | The bucket is created only after you confirm it on the Drive page |
| Restore command not found | Download the archive from the Backup view first, then pass the local path to kirocrew restore |
AWS Control