Skip to main content
Cloud Adapter implements a supported origin cloud API at the application boundary. That means many tools can work through it without a Tensor9-specific provider: configure the tool to use the adapter endpoint, then verify the operations and resource behavior your workflow needs.
Tool compatibility is directional and service-specific. A tool can use an origin adapter when its services and operations appear in the service catalog under that cloud.

​
Start here

AWS CLI

Prove an origin API request through the adapter with the smallest possible toolchain.

AWS SDKs

Configure a language SDK without rewriting its service calls.

Terraform/OpenTofu

Use adapted cloud APIs from infrastructure as code.

Pulumi

Deploy programs that use an origin-cloud provider API.

​
How to read these guides

Every guide follows the same loop:
  1. Configure the tool’s endpoint and credentials.
  2. Run a read-only smoke test.
  3. Create one uniquely named test resource.
  4. Verify the origin-shaped response and target-cloud state.
  5. Exercise one expected failure before expanding the workload.
  6. Use tuning, debugging and local testing to investigate differences.
Do not infer support from a tool’s provider name. The adapter’s service reference is authoritative.

​
Guides

​
Command-line and SDK clients

​
Infrastructure and orchestration

​
Automation and governance