Skip to main content
Cloud connections are useful when you want to analyze deployed state instead of only template files.

​
Why it matters

Connections can accelerate inventory and change discovery, but require correct permissions and scoping.

​
Quick example

Run a connection sync after setup, then validate discovered resources in your project view.
Expected output: Newly discovered resources appear in your connected workspace after sync completes.

​
Step-by-step instructions

  1. Start with one limited-scope connection.
  2. Validate metadata and visibility.
  3. Run a sync operation.
  4. Query the connection for sanity checks.
  5. Expand scope only after baseline success.

​
Code examples

# Example validation after sync
cloudeval ask "Summarize newly discovered resources" --project <project_id>

​
Expected output

  • Connection setup completes successfully.
  • Sync runs and updates resource visibility.
  • Analysis reflects connected inventory.

​
Common mistakes

  • Over-scoping permissions on first setup.
  • Running sync before credential verification.
  • Treating provider parity as guaranteed.

​
Tips / best practices

  • Use IaC-first onboarding, then layer connection sync.
  • Keep a connection checklist for permissions and regions.
  • Review Feature Availability before broad rollout.
Last modified on March 5, 2026