> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pulumi Guide

> Use a Pulumi AWS provider through Cloud Adapter with explicit endpoint and lifecycle verification.

Pulumi uses cloud provider plugins that call cloud APIs. With an AWS-origin Cloud Adapter, use an explicit AWS provider instance and attach it to every resource in the test. This keeps endpoint selection visible and prevents resources from falling back to the default AWS provider.

## Start a local adapter

Use one service mapping before testing a larger Pulumi program. This guide's bounded fixture uses S3 backed by Google Cloud Storage:

**1. Install or update the Tensor9 CLI**

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

```bash theme={null}
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.

**2. Authenticate with Tensor9**

To create a Tensor9 account and download an API key yourself, follow [Get a Tensor9 API key](https://docs.tensor9.com/byoc/getting-started/api-key.md).

A Tensor9 API key is required. Use the key issued during onboarding, or email [hello@tensor9.com](mailto:hello@tensor9.com) 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`:

> [tab] Bash
>
> ```bash theme={null}
> set +x
> IFS= read -r -s -p 'Tensor9 API key: ' T9_API_KEY
> printf '\n'
> export T9_API_KEY
> ```

> [tab] Zsh
>
> ```zsh theme={null}
> 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:

```bash theme={null}
: "${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. While `T9_API_KEY` is set, `tensor9` commands in this terminal use the key instead of any controller profile, so use a separate terminal for this work and run `unset T9_API_KEY` when you finish. 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](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/install-and-authenticate.md) for the planned license lifecycle, entitlements and credential boundaries.

**3. Inspect the S3 to Google Cloud Storage mapping**

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

```bash theme={null}
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.

**4. 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.

**5. Start the S3 service adapter**

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

```bash theme={null}
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](https://docs.tensor9.com/cloud-adapter-early-access/deployment/single-binary.md). 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.

**6. Copy the listening endpoint**

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

```bash theme={null}
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.

**7. 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.

**8. 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.

## Prerequisites

* Pulumi CLI 3.x and `@pulumi/aws` `6.83.0` for the exact configuration below;
* an installed AWS-origin adapter endpoint;
* an existing test bucket and isolated object prefix;
* an origin-side AWS identity;
* a disposable Pulumi stack.

The example uses S3. Confirm the selected target in [S3 service coverage](https://docs.tensor9.com/cloud-adapter-early-access/service-catalog/aws/databases-storage/s3.md).

## Create an explicit provider

```ts theme={null}
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const config = new pulumi.Config();
const endpoint = config.require("adapterEndpoint");
const bucket = config.require("testBucket");

const adapter = new aws.Provider("cloud-adapter", {
  region: "us-east-1",
  endpoints: [{ s3: endpoint }],
  s3UsePathStyle: true,
  skipCredentialsValidation: true,
  skipMetadataApiCheck: true,
  skipRegionValidation: true,
  skipRequestingAccountId: true,
});

const object = new aws.s3.BucketObjectv2("smoke", {
  bucket,
  key: "pulumi/cloud-adapter-smoke.txt",
  content: "hello through Cloud Adapter\n",
  contentType: "text/plain",
}, { provider: adapter });

export const etag = object.etag;
```

Pin the package in `package.json` as `"@pulumi/aws": "6.83.0"`. The four startup switches keep this bounded S3 fixture from calling EC2 metadata, region validation, or AWS STS outside the configured adapter route. They do not weaken Cloud Adapter authentication. Reassess the provider call graph before changing versions or adding resource types.

## Preview and apply

```bash theme={null}
pulumi stack init cloud-adapter-smoke
pulumi config set adapterEndpoint "$T9_CLOUD_ADAPTER_ENDPOINT"
pulumi config set testBucket adapter-smoke-test
export AWS_PROFILE="adapter-test"
export AWS_REQUEST_CHECKSUM_CALCULATION="WHEN_REQUIRED"
pulumi preview --diff
pulumi up --yes
```

After `pulumi up`, read the object through the origin API and inspect it in the native target service. Confirm bytes, content type, translated name, and request identifiers.

## Refresh deliberately

```bash theme={null}
pulumi refresh --preview-only --diff
pulumi refresh --yes
pulumi preview --diff
```

Refresh proves that the provider can read the object and reconcile provider-visible defaults. A create that succeeds followed by a refresh diff usually points to fidelity, normalization, or identifier translation rather than a Pulumi state-backend problem.

## Clean up

```bash theme={null}
pulumi destroy --yes
pulumi stack rm --yes
```

Verify deletion through both the origin API and target service. The Pulumi stack state, Pulumi secrets provider, Cloud Adapter configuration, and target object data are separate stores with separate retention policies.

## Important boundaries

* `pulumi preview` and `refresh` execute read calls; they are not offline operations.
* Provider initialization may call discovery APIs beyond the resource's service.
* Attaching the explicit provider to one resource does not automatically attach it to every child component.
* State is not a data migration engine.
* A successful object test does not certify bucket policies, lifecycle rules, notifications, retention, or signed URLs.

When a provider operation fails, reproduce its AWS call with the [AWS CLI guide](https://docs.tensor9.com/cloud-adapter-early-access/guides/aws-cli.md), preserve response metadata, and compare the operation with the service profile.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.