Cloud connections¶
Account → Cloud accounts is how Koltto authenticates to each cloud. Connections are credentials only. Every Costs and Resources page reads whatever those accounts have already refreshed.
Today you can add AWS and Oracle Cloud. Google Cloud and Azure are not available to connect. Azure is the next cloud we plan to add — see the roadmap.
Before you add one¶
- The company’s plan must include that cloud. If the form says the cloud is not on your plan, email support@koltto.com.
- Use a read-only principal named
KolttoReaders. Koltto does not need permission to create, start, stop, or delete resources. On AWS the CloudFormation stack creates that user; on Oracle Cloud you create the group and policy — see AWS and Oracle Cloud. - Give the account a name you will recognize (
prod-core,oci-tenancy).
After you add one¶
For AWS, a first inventory refresh starts when you save. For Oracle Cloud, inventory starts after you add Koltto’s public key to the OCI user and confirm it — see Oracle Cloud. Then:
- Run Cost (and Metrics if you want Opportunities) from Refresh data. New AWS CUR files and OCI cost reports can take up to 24 hours before the first rows exist.
- Open Overview.
You do not select a connection to view data. If a page looks empty, refresh — do not add duplicate keys.
You can add several accounts per cloud. Koltto attaches the right credentials per resource. One AWS CloudFormation stack covers one AWS account; see AWS if you have an organization with member accounts.
Access keys cannot be shown again. On AWS you can update the CUR bucket and prefix. To rotate keys, add a new account and remove the old one if you no longer need it.