Komiser dashboard only shows hosted AWS account; newly added accounts remain “Scanning” indefinitely

[sowmya1112]

Describe the bug
I have Komiser deployed in AWS ECS (hosted in Account A). The dashboard correctly lists all resources from Account A, but when I add a second AWS account (e.g. pos-test) using its access key/secret, the UI shows it as “Scanning” and it never completes—remaining stuck in that state for days, with no resources appearing.

To Reproduce
Steps to reproduce the behavior:
1.Deploy Komiser (v____) to AWS ECS in Account A using the official tailwarden/komiser image.
2.Navigate to Cloud Accounts → Add AWS Account.
3.Enter Access Key ID and Secret Access Key for Account B (pos-test).
4.Click Save.
5.Observe the new account’s status in the list—“Scanning” (spinner)—and wait.
6.Observe the new account’s status in the list—“Scanning” (spinner)—and wait.
7.No resources ever appear under Explorer or Inventory for that account.

Expected behavior
After a few minutes, Komiser should finish syncing and list all resources from the newly added AWS account alongside those from the hosted account.

Screenshots

[github-actions]

Hey, thank you for opening your first Issue! 🙂 While a Tailwarden team member takes a look at your issue we would like to invite you to join our official Discord server, where you can interact directly with other contributors and Tailwarden team members. Link here: https://discord.tailwarden.com