Orphaned cloud resources and their cost — a weekly report

Once a week the scenario scans the cloud via awsLambda, finds idle disks, snapshots and addresses, calculates their cost and sends a report to Telegram, Keap and Azure Cosmos DB.

  • Forgotten resources are found automatically, weekly
  • You see the exact money they cost
  • The report lands in Telegram and Keap
  • History builds up in Azure Cosmos DB for the trend
AWS Lambda
Set it up for yourselfScriptera

How it works

To move data from Telegram to Keap automatically, use a ready-made scenario — no manual exports.

  1. Starts when: Weekly Scan Trigger1
  2. Then: Initialize Config
  3. Then: Set Region Variables
  4. Then: Scan unattached EBS Volumes
  5. Then: Process EBS Volumes
  6. Then: Aggregate All Resources
  7. Then: Calculate Summary Stats
  8. Check: If Resources Found
  9. If yes: Generate HTML Report
  10. Then: Send Email Report
  11. If yes: Send Slack Alert
  12. If yes: Generate CSV Export
  13. Then: Log to Google Sheets (Found)
  14. If no: None Found Slack Message
  15. If no: Clean Scan CSV Export
  16. Then: Append or update row in sheet
  17. Then: Scan EBS Snapshots
  18. Then: Process Snapshots
  19. Then: Scan Elastic IPs
  20. Then: Process Elastic IPs

You can launch this Telegram + Keap integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios