CloudConsole · Tips
AWS tips across every account, sent to Jira, Trello or GitHub
CloudConsole scans the accounts and regions you choose for money to save, security gaps and things that will break, ranks them, fixes some in one tap, and turns the rest into Jira issues, Trello cards or GitHub issues your team will actually pick up.

One scan, every account and region
Open Tips from Services → Tools, from the line under Dashboards on Home, or from Account → Integrations. Pick the scope with the same pill as Home: this account or several, one region or many. The scan reads EC2, the waste finder, Lambda runtimes, RDS, CloudWatch Logs, KMS key rotation, VPC security groups and flow logs, EKS versions, ElastiCache and OpenSearch in each region, and IAM and S3 once per account. A source that is refused or slow is listed as skipped; the rest of the scan still counts.
Ranked, so you know where to start
Each tip has a category (Cost, Security, Reliability, Performance, Operations or Housekeeping), a severity from Low to Critical and, for cost tips, an estimated monthly saving at US list prices. Filter by category, severity, account, region or service, group and sort them, or search. Tap a tip to open the resource, or read AWS’s documentation for it.
Fix it, snooze it or dismiss it
Some tips have a one-tap fix: keep a log group’s events for 30 days instead of forever, or add a lifecycle policy to an ECR repository (shown before it is sent). A fix is a change like any other, so it goes through your guardrails and needs Pro. Snooze a tip for 7 or 30 days, or dismiss it; dismissing here also hides it on the resource’s own screen.
Send them to Jira, Trello or GitHub
Select tips and tap Export. Jira Cloud creates issues in the project and issue type you choose, with the description formatted for Jira, labels for the category and service and, if you like, a priority from the severity. Trello adds cards to the board and list you choose. GitHub Issues opens issues in a repository your connected GitHub account can write to. Each issue explains why it matters, what to do, and links back to the resource in the app and the AWS console.
Exported tips show their issue, such as Exported · OPS-101; tap it to open the issue. Sync status from Jira / GitHub marks the ones that are done, and a tip you export twice asks first. Not using any of them? Copy them as Markdown or CSV, email the list or post a digest to Slack, for free.
Your tokens stay on the phone
The Jira API token and the Trello key and token are kept in the iOS Keychain or Android Keystore and sent only to Atlassian or Trello; exports go straight from your phone to that service, never through us. Issues name the account, not its 12-digit ID or resource ARNs, unless you turn on Include account ids for that destination.


Questions
Can I send AWS recommendations to Jira or Trello?
Yes, with CloudConsole Pro. Select tips in the Tips hub and export them as Jira Cloud issues, Trello cards or GitHub issues. Copying them as Markdown or CSV is free.
What does the scan check?
Unused and idle resources, stopped instances, old snapshots, log groups that never expire, deprecated Lambda runtimes, IMDSv1, open security group ports, missing flow logs, KMS key rotation, EKS versions, IAM users without MFA, old access keys, root account keys and public or unprotected S3 buckets, among others.
Does it change anything in my account?
Scanning only reads. A one-tap fix is a change you confirm, through your usual guardrails. Exporting creates issues in Jira, Trello or GitHub, not in AWS.
How do I connect Jira?
In Export destinations, add Jira with your site (such as acme.atlassian.net), the email you sign in with and an API token from your Atlassian account, test the connection, and pick the project and issue type.
Try CloudConsole
On the App Store for iPhone and Google Play for Android. Look around the demo, GitHub and Slack included, before connecting an account.