Getting Started

Getting Started

This article will guide you through setup.

📝 Step 1: Sign-up

Sign-up on to setup your AWS Accounts and preferred configuration.

  • Free forever for a single AWS Account
  • No credit card is required
  • Cancel anytime
  • ReadOnly permissions

➕ Step 2: Add AWS Accounts

  1. Login to app
  2. Add each of your AWS Accounts and desired notification configuration (Email, Slack, Microsoft Teams)

Add AWS account

Then deploy the associated read-only IAM Role using the provided link to CloudFormation console:

Deploy read-only IAM Role

Repeat this operation, on every AWS account that you want to attach to your subscription.

If you have multiple AWS Accounts, prefer the usage of AWS CloudFormation StackSets, it will allow you to deploy the IAM Role to all your AWS Accounts with a single deployment.

✅ [Optional] Step 3: Add Exception tag to legitimate AWS assets

To prevent alert fatigue and irrelevant reports, it may be necessary to add legitimate assets to the exception list. Typically, this can be accomplished by setting a tag on an existing legitimate AWS assets.

To simplify the process, you can utilize an existing AWS tag that has already been deployed to your legitimate assets. The Key of this tag is part of the unusd configuration (Exception Tag), in the advanced menu. The default tag key is unusd.

Recent Articles

AWS Horror stories

The scariest thing to me about AWS is that I might accidentally bankrupt myself while I learn to use it.

How manage the security?

The security measures employed by and our data handling practices are detailed in this page.

What are the expected savings?

Let’s take some concrete examples of what could save on your AWS bills.