l4 integrations

l4 integrations shows which cloud providers (AWS, GCP, Azure, Kubernetes) are connected to your organization. Providers has the provider_id each one goes by.

Global flags (--json, --jq, --template, --quiet, --token, --api) apply. See CLI overview. Exit codes follow the standard CLI exit conventions.

list

l4 integrations list

Returns one row per connected provider, its provider_id under ID and its provider_name under Name:

╭───┬────╮
│ID │Name│
├───┼────┤
│aws│AWS │
│gcp│GCP │
╰───┴────╯

A provider you expect and do not see has not been connected yet.

--json returns the same rows in a JSON envelope:

l4 integrations list --json

{
  "success": true,
  "data": [
    { "provider_id": "aws", "provider_name": "AWS" },
    { "provider_id": "gcp", "provider_name": "GCP" }
  ],
  "timestamp": "2026-04-27T11:00:00Z"
}

Examples

Read the provider_id values on their own, for scripting:

l4 integrations list --jq '.data[] | .provider_id'

Fail a pipeline when a provider is not connected:

l4 integrations list --jq '.data[] | select(.provider_id == "aws")' --quiet \
  || { echo "AWS integration missing"; exit 1; }

Related

• l4 costs: where a provider_id becomes --provider
• l4 recommendations: the other command scoped by provider
• Providers: the same list over the REST API and the SDKs
• Onboarding: how a provider gets connected in the first place
• Output formats: what --json, --jq and --quiet each emit