Tips: AWS recommendations, exported to Jira, Trello or GitHub
Scan your accounts and regions for cost, security and reliability tips, fix some in one tap, snooze or dismiss them, and export them to Jira Cloud, Trello or GitHub Issues.
The Tips hub gathers every recommendation CloudConsole can work out for the accounts and regions you choose: money to save, security gaps and settings that will hurt later. Open it from Services → Tools → Tips, from the Tips line under Dashboards on Home (“N tips · Save $X/month” from your last scan), or from Account → Integrations → Tips.

What it scans
Pick the scope with the pill in the app bar: this account or several, one region or many. The app checks eight account-regions at a time on your phone, and pull to refresh or Rescan starts again. The last scan is kept on the phone, so the hub opens with it (Scanned 2 h ago).
- In each region: EC2 (stopped instances, IMDSv1), the waste finder (unattached volumes, idle Elastic IPs, old snapshots, quiet NAT gateways and more), Lambda functions on deprecated runtimes, RDS, CloudWatch Logs groups that never expire, KMS key rotation, VPC security groups open to the internet, missing flow logs and unused groups, EKS versions near the end of support, ElastiCache and OpenSearch.
- Once per account: IAM (root access keys or root without MFA, console users without MFA, access keys unused for 180 days or more; from the account summary or an existing credential report, which the scan never generates) and S3 (up to 20 buckets: public access, Block Public Access partly off, versioning without a lifecycle rule).
Each source has 20 seconds. One that is refused or slow is listed under the results as skipped, with the reason, and the rest still counts. ECR, ECS, EFS, EBS burst balance, MSK and Athena tips take too many calls to scan, so they appear only on those resources' own screens.
Reading the list
The summary shows the estimated monthly saving and the count by severity (Low, Medium, High, Critical) and category: Cost, Security, Reliability, Performance, Operations and Housekeeping. Savings are estimates at US list prices, shown in US dollars. Filter by category, severity, account, region, service or Has a one-tap fix; group by category, account or service; sort by most severe, biggest saving or newest; or search. Tap a tip to open the resource in the right account and region; the menu also has the AWS documentation for it.
Fix, snooze or dismiss
- One-tap fixes: Keep 30 days on a log group that never expires, and a lifecycle policy on an ECR repository (the policy JSON is shown first). A fix is a change, so it needs Pro and goes through your guardrails and the activity log.
- Snooze 7 days or Snooze 30 days hides a tip until then; Show N snoozed in the menu brings them back.
- Dismiss hides it for good on this phone, here and on the resource's own screen.
Long-press a tip to select several, then dismiss, snooze or export them together.
Export to Jira, Trello or GitHub
Add a destination under Export destinations (in the hub's menu, or Account → Integrations), tap Test connection, then choose where issues go:
- Jira Cloud: your site (such as
acme.atlassian.net), the email you sign in with and an API token (Open API tokens page takes you to your Atlassian account), then the project and issue type. Issues are written in Jira's own format (Atlassian Document Format), labelledcloudconsole, the category and the service, with the priority set from the severity if you turn that on. If the issue type has required fields the app can't fill, it names them before you export. - Trello: an API key and a token from Trello's Power-Up admin page (Open Power-Up admin), then the board and list for the cards.
- GitHub Issues: your connected GitHub account and a repository it can write to; issues are labelled
cloudconsoleand the category.
Select tips and tap Export (or Export all shown… in the menu). The app confirms first, typed with the project key, list or repository, and asks before exporting a tip that is already in that destination. Each issue says why the tip matters, the details, the account by name, how to fix it, and links to the resource in the app, the AWS console and AWS's documentation. Account IDs and resource ARNs are left out unless you turn on Include account ids for the destination.
Tracking what you exported
Exported tips show a chip such as Exported · OPS-101; tap it to open the issue. Sync status from Jira / GitHub in the menu checks each issue and shows Done in Jira (or GitHub) for the closed ones; Trello cards aren't synced. After a rescan, exported tips that no longer appear are counted as resolved.
Free ways to share
Copy as Markdown and Copy as CSV put the selected tips on the clipboard, Email… opens a message with them, and Post a digest to Slack sends a summary to Slack. These are free; exporting to Jira, Trello or GitHub and one-tap fixes need Pro. In the demo everything works on sample data, with a demo Jira site, Trello board and GitHub repository.
Privacy
The Jira 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 from your phone straight to Jira, Trello or GitHub; nothing passes through CloudConsole. Only the tips you export are sent, with the text shown above.
Questions
Can I send recommendations to Jira or Trello?
Yes, with Pro. Add Jira Cloud (site, email and API token) or Trello (API key and token) under Export destinations, select tips and tap Export. GitHub Issues works with your connected GitHub account.
Does the scan cost anything?
The scan uses ordinary read calls, most of them free. It doesn't call Cost Explorer or generate an IAM credential report.
Why is a tip missing from the hub but shown on a resource?
Some tips, such as ECR, ECS, EFS and MSK ones, need too many calls to scan across accounts, so they appear only on the resource's own screen.
Email [email protected] with what you tried and any message the app showed. Don’t send access keys or secrets. We reply within two working days.