Skip to main content
KibaCloud
Log in

FAQ

The questionspeople ask first.

Short answers, with a link to the long version where there is one.

01

Security

What access do you get to my AWS account?
A read-only IAM role in your account, created by a template you run. We never store credentials.The full policy, action by action
Is that AWS's ReadOnlyAccess policy?
No — a narrower one, limited to the calls we actually make.
Can I cut off access?
Any time. Delete the stack and we are locked out immediately.How revocation works
What do you store?
Resource metadata — names, IDs, types, regions, tags. Never the data inside them.What we store, and where it lives

02

What it does

How often does it scan?
Daily, every region, automatically. New accounts scan the moment you connect them.
Does it show costs?
No. We tell you what exists and what looks forgotten — your cost tooling prices it.
What does it cover?
Compute, data stores, messaging, and the networking that costs money.Every resource type it tracks
Why is a resource I deleted still listed?
Deleted resources sit in Recently Deleted for 72 hours before they are dropped, so a failed scan never makes a live resource vanish.
Can I hide a finding that does not apply?
Dismiss it — it stays dismissed.

03

Accounts and billing

What happens when the trial ends?
Nothing is charged — there is no card on file. Scanning stops, your accounts stay connected, and collected data is kept 30 days.Plans and prices
How many AWS accounts can I connect?
Depends on your plan.What each plan includes
Can my team share a workspace?
Yes — invite them. Connecting accounts and dismissing findings are admin-only.

Not answered here?

The security page is the long form: the policy in full, what we keep, and how you take access back.

Read the security page

Ask us directly

Anything this page does not cover, mail us.

support@kibacloud.io