Integrations

AWS

AWS environments often scatter operational signals across services and accounts. The integration goal is to pull enough of that shape into the shared CTK model that reasoning and replay stay coherent.

Cloud runtime contextProvider-aware evidenceCross-surface coherence

Back To Docs Hub

Page Focus

AWS integration brings cloud runtime and service-context signals into the CTK model so evidence and topology remain cloud-aware.

Cloud runtime context

AWS contributes service-level and runtime observations that help Reason attach operational truth to the right scope.

Provider-aware evidence

Cloud evidence needs explicit source context so operators know which observations came from provider-managed surfaces.

Cross-surface coherence

The integration is most valuable when cloud signals can still participate in the same contradiction and replay model as local ones.

Questions This Page Answers

How does AWS evidence enter the shared model?

Why should provider-originated signals remain explicit?

How do teams keep cloud visibility coherent with the rest of the workspace?

Move across the shared CTK documentation model.

Reason Evidence

/docs/reason/evidence

Lens Signals

/docs/lens/signals

Reference

/docs/reference