Guides

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. First install the Tensor9 CLI and authenticate with T9_API_KEY. This operator credential is not sent by the tools or SDKs in these guides.

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 one adapter locally

The example below uses AWS S3 as the origin API and Google Cloud Storage as the backend. A specific guide can use another directed pair from the service catalog.

Install or update the Tensor9 CLI

Install the customer CLI with Homebrew, then confirm the binary is available:

brew tap tensor9ine/tensor9
brew trust tensor9ine/tensor9
brew install tensor9
tensor9 --version

If tensor9 is already installed, run brew upgrade tensor9 instead of the install command.

Authenticate with Tensor9

A Tensor9 API key is required. Use the key issued during onboarding, or email [email protected] to request one for your organization. Do not share your account or key with another customer or organization.If your secret manager has already supplied T9_API_KEY, skip the prompt. Otherwise, enter your key at a hidden prompt in the terminal where you will run tensor9:

Bash
Zsh

set +x
IFS= read -r -s -p 'Tensor9 API key: ' T9_API_KEY
printf '\n'
export T9_API_KEY

set +x
IFS= read -r -s 'T9_API_KEY?Tensor9 API key: '
printf '\n'
export T9_API_KEY

Check that the variable is set without printing it, then verify your Tensor9 identity:

: "${T9_API_KEY:?Set T9_API_KEY before continuing}"
tensor9 whoami

Confirm that the reported identity belongs to the intended customer account. Do not continue if authentication fails or the account is wrong. Keep shell tracing disabled while using the key. Do not paste the key into commands, shell profiles, source files, screenshots or support messages.See Install and Authenticate for the planned license lifecycle, entitlements and credential boundaries.

Inspect the S3 to Google Cloud Storage mapping

Ask Tensor9 to describe the exact directed service mapping used by this guide:

tensor9 explain \
  -origin aws::1.0.0::s3 \
  -target google::1.0.0::gcs \
  -fmt Human

Read the supported S3 operations and Google Cloud Storage limitations before starting the process. The mapping is directional: this command describes S3 requests adapted to Google Cloud Storage, not the reverse direction.

Prepare Google Cloud access

Authenticate with Google Cloud using its standard Application Default Credentials chain. The adapter uses that identity when it calls Google Cloud Storage.Use a dedicated test project and narrowly scoped credentials. Do not put credentials in the command line, source code, or screenshots.

Start the S3 service adapter

Run the S3 to Google Cloud Storage adapter as a foreground process:

tensor9 adapt svc run \
  --origin aws::1.0.0::s3 \
  --backend google::1.0.0::gcs

Leave this terminal open. This is the current foreground launcher, not the pending Docker launcher for local development mode. It calls your actual target-cloud services; it is separate from the in-memory emulator. Acquisition and license renewal require Tensor9 authentication. Keep the endpoint local to your test.

Copy the listening endpoint

When the command reports its listening endpoint, copy that exact value into a second terminal:

export T9_CLOUD_ADAPTER_ENDPOINT="<endpoint printed by tensor9>"

Keep the endpoint local to the test unless you have deliberately configured network access and authentication for another machine.

Run one bounded S3 request

Continue with this page’s client or tool instructions. Point only S3 at T9_CLOUD_ADAPTER_ENDPOINT, then perform one operation whose Google Cloud Storage effect you can verify independently.Check both sides: read the S3-shaped response and inspect the native object or bucket in Google Cloud Storage. A successful client response alone does not prove that the target state is correct.

Stop the local adapter

Return to the first terminal and press Control-C. Confirm the process exits before deleting the test object or bucket with Google Cloud’s native client.If the request failed, preserve the request ID, adapter endpoint, S3 operation name, Google Cloud request ID, and any x-t9-explain-* receipt headers before stopping the process.

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:

Configure the tool’s endpoint and credentials.
Run a read-only smoke test.
Create one uniquely named test resource.
Verify the origin-shaped response and target-cloud state.
Exercise one expected failure before expanding the workload.
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.

Tensor9 Cloud Adapter

How It Works

Getting Started

Configuration

Deployment

Support

Amazon Web Services

Google Cloud

Microsoft Azure

Making Trade-offs

Tuning

Debugging

Testing

Reference

Guides

Start one adapter locally

Start here

AWS CLI

AWS SDKs

Terraform/OpenTofu

Pulumi

How to read these guides

Guides

Command-line and SDK clients

Infrastructure and orchestration

Automation and governance

​Start one adapter locally

​Start here

AWS CLI

AWS SDKs

Terraform/OpenTofu

Pulumi

​How to read these guides

​Guides

​Command-line and SDK clients

​Infrastructure and orchestration

​Automation and governance

Start one adapter locally

Start here

How to read these guides

Guides

Command-line and SDK clients

Infrastructure and orchestration

Automation and governance