Getting started with Cloudbrief
Sign up → connect an AWS account → first daily report. Should take about 10 minutes.
1. Create your account
Go to app.kashilabs.ai/signup (opens in a new tab) and sign up with your work email. See Accounts & teams for the org-grouping rules.
After signup you'll land on the Cloudbrief dashboard, which is empty until you connect an AWS account.
2. Enable Cloudbrief for your organisation (probably no-op)
Cloudbrief is enabled by default for every new organisation, so this step is usually a no-op. If you don't see Cloudbrief in the product switcher (top-left logo dropdown), your platform admin needs to toggle it on at Workspace → Platform admin → your org → Product access.
3. Connect an AWS account
Cloudbrief → AWS accounts → "Add account".
The form asks for:
- A nickname (free text — "Production", "Customer A", etc.)
- The 12-digit AWS account ID
- The AWS region(s) you want to analyse
- An email recipient list for the daily report (one address per line)
Then click "I'll set up the IAM role next" — you'll get a CloudFormation template you can run in your AWS console. See Connecting an AWS account for the full walkthrough.
After the role is created, paste the role ARN back into the form and hit "Connect". We immediately test the connection by listing your S3 buckets via STS:AssumeRole — if you see "Connected ✓", you're done with setup.
4. Run your first analysis
By default the daily analysis runs at 09:00 IST (03:30 UTC). To trigger one immediately:
Cloudbrief → Reports → "Run analysis now" → pick the AWS account → submit. Takes 30–90 seconds depending on how much data the period has.
When it finishes, the report shows up in the Reports list with severity and finding count. Click it to read the synthesised narrative.
5. (Optional) Set up incident hunting
Cloudbrief → Incidents → "Hunt for the last 30 days" scans the period for ALB anomaly windows. Each candidate gets a severity score; click any to deep-dive with a one-shot investigation that pulls the matching CloudTrail events + access logs and writes a root-cause narrative.
6. Check your spend
Workspace → Usage shows your per-account AI cost broken down by month + lifetime. The detector layer skips the LLM on quiet days, so most accounts run in the low single dollars per month.
You're done
The daily analysis will run automatically tomorrow morning IST. Email recipients on the account will receive the report; the same report is also viewable in the Reports tab indefinitely.
Next reads:
- Reports & investigations — what the daily report contains, how to read root-cause chains.
- Troubleshooting — what to do when an analysis fails or the IAM connection breaks.