Docs > Platform Observability > Getting Started with Cloud Integrations

Getting Started with Cloud Integrations

Overview

This guide introduces AppStatus Cloud Integrations and covers:

A catalogue of cloud providers, databases, queues and runtimes
Each entry maps to a real ingest path
Read-only access — nothing requires write permission
Connect one at a time and verify before adding the next
Ownership recorded per connection

What are Cloud Integrations in AppStatus?

The catalogue lists the sources AppStatus can pull from or receive data from. Connecting one starts its data flowing into the same views as everything else, rather than into a separate silo you have to remember to check.

Every integration is read-only by design. If a connection form asks for credentials, grant the narrowest read scope the provider offers — nothing in the catalogue needs permission to change anything in your account.

Key capabilities:

Cloud provider connections for AWS, Azure and GCP
Database, queue, runtime and platform-service sources
Per-integration setup steps with a verification check
Region and account selection per connection
Connection ownership recorded for later review

What you will see

What connected integrations look like

app.appstatus.ioSample data

Integration	Scope	Regions	Last sync	Status
AWS — production	Read-only	eu-central-1, us-east-1	4 min ago	Connected
PostgreSQL — orders	Read-only	eu-central-1	1 min ago	Connected
Kafka — events	Read-only	eu-central-1	2 min ago	Connected
GCP — analytics	Read-only	europe-west4	—	Needs attention

Scroll the table sideways to see every column.

Remove connections for accounts you no longer run — stale sources produce misleading gaps.

Troubleshooting

A connection shows "needs attention"

Usually an expired or rotated credential, or a permission that was narrowed on the provider side. Re-authorise the connection and confirm the read scope still covers what it needs.

Data appears for one region only

Regions are selected per connection. Add the missing regions to the existing connection rather than creating a second one for the same account.

The provider reports rate limiting

Lower the poll interval for that connection. Frequent polling across many accounts is the usual cause, and the default interval is chosen to stay inside typical provider limits.

Operational Guidance

Connect one integration at a time and verify it before adding the next.
Rotate connection credentials on the same schedule as the rest of your cloud access.
Remove connections for accounts you no longer run — stale sources produce misleading gaps.

Step-by-Step Setup

Connect one integration, verify its data arrived, then connect the next. Doing them in a batch makes a single misconfiguration hard to find later.

Before you start

Admin access to the provider account you are connecting

1
Find the source in the catalogue
Browse the catalogue and pick the source you want. Each entry lists what data it brings in and which views that data appears in.
WhereCloud Integrations → Catalogue
2
Grant read-only access
Follow the connection steps and grant the narrowest read scope the provider offers. Nothing in the catalogue needs permission to change anything in your account.
WhereCloud Integrations → Add connection
Tip
If a form seems to ask for write access, stop and check — it should not be necessary.
3
Select regions and accounts
Choose which regions and accounts to poll. Start with production and add others once the first connection looks right.
WhereConnection settings
4
Verify before adding the next
Confirm data appears in the view the integration feeds before connecting anything else. One at a time is slower and much easier to debug.
WhereThe relevant observability view
5
Record who owns it
Note the owning team for each connection so credentials get rotated with the rest of your cloud access rather than quietly expiring.
WhereConnection settings → Owner

Configuration Options

Every option you can set, what each choice means, and what to pick. Use this as a reference while you fill in the form.

Connection settings

Field	Options	What it does	Recommended
Access scope	Read-only	What the connection may read.	Read-only, always. The narrowest scope the provider allows.
Regions / accounts	Provider-specific	Which parts of the provider are polled.	Production first; expand once verified.
Poll interval	Minutes	How often the source is queried.	Default. Frequent polling across many accounts hits provider limits.

Feature Reference

Every feature, where to find it in the app, and what it does. Use this when you know what you want to do but not where it lives.

Feature	Where in app	Description
Catalogue	Cloud Integrations → Catalogue	Cloud providers, databases, queues, runtimes and platform services.
Per-integration setup	Catalogue → entry	Connection steps with a verification check.
Connection health	Cloud Integrations	Last sync and status per connection.
Ownership	Connection settings	Who to ask when a credential expires.

Next Steps

Continue building your monitoring stack:

Cloud Cost

Spend data arrives once accounts connect.

Infrastructure

Pair provider data with agent telemetry.

Ingest Keys

For sources that push instead of being polled.