Skip to main content
Cloud connections are a preview. They are off by default and the API, CLI and any future screen refuse every request until you turn on the runtime setting cloud.connections_enabled. A connection is a named record of one cloud account on your control plane. It holds non-secret settings (region, account or tenancy ID, compartment, role ARN, subscription ID) and a reference to a credential. It never holds the credential. Everything stays on your control plane: nothing is sent to a hosted service.

What works today

The real read-only checks for Oracle, AWS and Azure need each cloud’s client library. Adding those dependencies is a separate decision, so the providers are registered as not implemented until then.

Turn it on

The environment variable APP_CLOUD_CONNECTIONS_ENABLED only seeds the default. A stored value wins and applies without a restart.

Use it

Listing needs the read ability. Create, update, delete and test need root. Every change and test writes an audit entry holding the connection name, provider, team and the outcome class. Credential material and credential references are not written to the audit log.

Health classes

test returns one class and a fixed short reason. Provider output is never passed through.

API

GET, POST on /api/v1/settings/cloud-connections, PUT, DELETE on /api/v1/settings/cloud-connections/{name} and POST on /api/v1/settings/cloud-connections/{name}/test. While the setting is off every route answers 403 with a message naming it.
Last modified on November 12, 2026