[3uler]

The read-only hesitation seems overcautious. If you’re genuinely using it read-only, what’s the failure mode? The tool crashes or returns bad data - same risks as the AWS CLI or console.

The “middleware layer” concern doesn’t hold up. This is just a better interface for exploring AWS resources, same as k9s is for Kubernetes. If you trust k9s (which clearly works, given how widely it’s used), the same logic applies here.

If you’re enforcing infrastructure changes through IaC, having a visual way to explore your AWS resources makes sense. The AWS console is clunky for this.

[catlifeonmars]

> what’s the failure mode?

The tool misrepresents what is in AWS, and you make a decision based on the bad info.

FWIW I agree with you it doesn’t seem that bad, but this is what came to mind when I read GPs comment

[jama211]

Fair. Best use might be to double check on the proper UI before making any big decisions, and just use it as a general monitor

[3uler]

I mean sure… but to me that is as likely as the official ui misrepresenting the info.