CloudConsole · Security
Security model
A phone that can change production should be held to a higher standard than a laptop. Here is how CloudConsole is built.

Credentials stay on your phone
SSO tokens, session credentials and access keys are stored in the iOS Keychain or Android Keystore and protected by your device passcode. They are never sent to CloudConcur.
No server in the middle
The app signs requests itself and sends them straight to AWS endpoints over HTTPS. We don't run a proxy, and we never see your resources, logs or bills.
Guardrails for production
Each account has a confirmation level: off, tap to confirm, type the resource name (the default), or type and then Face ID or fingerprint. Destructive changes always need at least a typed confirmation, and any account can be made read-only.
Permission-aware
CloudConsole only does what your IAM policies allow. If AWS refuses an action, nothing changes and the app tells you which permission was missing.
Activity history
Every change you make is recorded on the device, with what was changed, when, in which account and region, and whether it worked. It is in addition to your CloudTrail logs.
Alerts without a server
Optional alarm alerts are checked by the app itself in the background, straight from your phone to CloudWatch. Nothing about your alarms is sent to us and nothing is deployed in your account.
Try CloudConsole
On the App Store for iPhone and Google Play for Android. There's a demo mode if you'd rather look around before connecting an account.