Cloud services
Connect each cloud provider just once (Railway, AWS, Google Cloud and Azure) and choose which services are monitored and where they go in Infrastructure.
In Cloud services you connect each cloud provider just once. That same connection is used by monitoring, costs (Settings → FinOps integrations) and the SIEM (Settings → SIEM integrations): those sections don't ask for another key, they just choose the connection when they are turned on.
The page has one tab per provider:
Tab | What you do there |
|---|---|
Railway | You connect Railway and choose which services are monitored. Each chosen service goes in Infrastructure according to what it is: a backend or container as a server, a managed database in Databases. Anything you don't choose is not monitored and does not count toward the plan |
AWS | You connect AWS with a read-only identity and choose which virtual machines, databases, functions and load balancers are monitored, where in Infrastructure they go and how often their metrics are read |
Azure | You connect Azure with a read-only service principal and choose which virtual machines, databases (Azure SQL, PostgreSQL, MySQL), apps (App Service) and functions are monitored, per subscription |
Google Cloud | You connect Google Cloud with a read-only service account and choose which virtual machines (Compute Engine), databases (Cloud SQL), apps (Cloud Run) and functions are monitored, per project |
Cloudflare | You connect Cloudflare with a read-only API token and choose which zones, Pages projects and Workers are monitored, per account. A resource that hosts a web service you already monitor does not count toward the plan |
Coolify | You connect your Coolify instance with its address and a read-only API token and choose which applications, databases and services are monitored, per project: status, health and latest deployment |
The Railway tab shows how many connections it has and how many services are monitored.
The Settings → Monitoring → Cloud services menu appears if your plan includes cloud services. Connecting or removing a connection is up to administrators; choosing what is monitored, to operators and administrators. Everyone else sees the list of what is monitored.