Skip to main content
Start with one service and a small set of operations your application actually uses. This makes it possible to verify compatibility before connecting a larger workload.

​
1. Check your service mapping

Find the origin service in the service reference under each cloud in the sidebar. Compare the backend choices and list the operations, request options and behaviors your application needs. Include less frequent operations: initial resource creation, policy changes, pagination, deletion and recovery after a timeout. A successful read or write alone is not a compatibility assessment.

​
2. Choose the deployment scope

For a focused integration, begin with one service adapter. For a workload using several origin services, configure a cloud adapter with the required mappings. The deployment guide explains the choices and who operates each component.

​
3. Prepare configuration and credentials

Record the target cloud and region, backend resources, storage and networking requirements, and the identity used to access the backend. Separately decide how application requests will be authenticated at the adapter endpoint. Setup accepts a complete configuration file or asks guided questions to generate one. Both routes converge on the same configuration. See configuration. Do not reuse production credentials in a first experiment. Use dedicated test resources and a scoped identity. Keep secrets out of configuration examples, issue reports and shared transcripts.

​
4. Define your first verification

Choose an operation with an observable outcome. For an object-store mapping, a useful test writes a small uniquely named object, reads it back, verifies its bytes and deletes only that test object. Verify the result through the origin API and confirm it reached the intended backend. Capture status, response headers and resource identifiers. Include one expected failure, such as a missing object, so you also understand the error path.

​
5. Expand deliberately

Run the local-testing checks, then repeat the relevant cases against the real target with test credentials. Measure your workload before and after any tuning changes. If a required mapping or operation is absent, contact Tensor9 with the origin service, target cloud and operation list. Do not infer support from a similar service name or a cloud logo.