AWS .NET SDK Guide

This example uses AWSSDK.S3. Your code keeps using IAmazonS3; the client configuration directs requests to Cloud Adapter.

Start a local adapter

This guide’s bounded example uses S3 backed by Google Cloud Storage:

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.

Choose how to set the endpoint

Set it for the process

export AWS_ENDPOINT_URL_S3="$T9_CLOUD_ADAPTER_ENDPOINT"

AWS SDK for .NET reads the service-specific setting when ServiceURL is not assigned:

using System;
using Amazon.Runtime;
using Amazon.S3;

var credentials = new StoredProfileAWSCredentials("adapter-test");
var config = new AmazonS3Config
{
    AuthenticationRegion = "us-east-1",
    ForcePathStyle = true,
    Timeout = TimeSpan.FromSeconds(30),
    MaxErrorRetry = 2,
};
IAmazonS3 s3 = new AmazonS3Client(credentials, config);

Set it on one client

: "${T9_CLOUD_ADAPTER_ENDPOINT:?start the local adapter and copy its endpoint first}"

using System;
using Amazon;
using Amazon.Runtime;
using Amazon.S3;

var credentials = new StoredProfileAWSCredentials("adapter-test");
var config = new AmazonS3Config
{
    ServiceURL = Environment.GetEnvironmentVariable("T9_CLOUD_ADAPTER_ENDPOINT"),
    AuthenticationRegion = "us-east-1",
    ForcePathStyle = true,
    Timeout = TimeSpan.FromSeconds(30),
    MaxErrorRetry = 2,
};

IAmazonS3 s3 = new AmazonS3Client(credentials, config);

ServiceURL selects the adapter endpoint. AuthenticationRegion keeps AWS signing behavior explicit. The adapter’s target-cloud identity remains in service adapter configuration, not in the .NET process. An explicit ServiceURL takes precedence over AWS_ENDPOINT_URL_S3.

Verify a lifecycle

using System;
using System.IO;
using Amazon.S3.Model;
using System.Text;

var bucket = Environment.GetEnvironmentVariable("TEST_BUCKET")!;
var key = $"dotnet/{DateTimeOffset.UtcNow.ToUnixTimeMilliseconds()}-hello.txt";
var expected = "hello through Cloud Adapter\n";

var put = await s3.PutObjectAsync(new PutObjectRequest
{
    BucketName = bucket,
    Key = key,
    ContentBody = expected,
    ContentType = "text/plain",
});

var head = await s3.GetObjectMetadataAsync(bucket, key);
using var get = await s3.GetObjectAsync(bucket, key);
using var reader = new StreamReader(get.ResponseStream, Encoding.UTF8);
var actual = await reader.ReadToEndAsync();
if (actual != expected) throw new InvalidOperationException("Downloaded bytes differ");

await s3.DeleteObjectAsync(bucket, key);

Inspect the native target object after the put. Record put.ResponseMetadata.RequestId, put.HttpStatusCode, the target object name, and the adapter version with your test evidence.

Handle errors

try
{
    await s3.GetObjectMetadataAsync(bucket, "missing-key");
}
catch (AmazonS3Exception error)
{
    Console.Error.WriteLine(new
    {
        error.ErrorCode,
        error.StatusCode,
        error.RequestId,
        error.Message,
    });
}
catch (AmazonServiceException error)
{
    Console.Error.WriteLine($"Service failure: {error.Message}");
}

Network and cancellation failures may have no service response. Do not treat missing response metadata as a translated AWS error. After a timeout on a mutation, inspect target state before retrying.

Production checklist

Reuse IAmazonS3; do not construct a client per request.
Pass cancellation tokens from the application boundary.
Test the exact retry, paginator, multipart, and conditional behaviors you use.
Keep origin credentials and backend credentials separate.
Do not log signed headers, request bodies, or secret values.
Compare operations with S3 target coverage.

Use Debugging Your Adapters when the SDK response and native target state disagree.

Tensor9 Cloud Adapter

How It Works

Getting Started

Configuration

Deployment

Support

Amazon Web Services

Google Cloud

Microsoft Azure

Making Trade-offs

Tuning

Debugging

Testing

Guides

Reference

AWS .NET SDK Guide

Start a local adapter

Choose how to set the endpoint

Set it for the process

Set it on one client

Verify a lifecycle

Handle errors

Production checklist

​Start a local adapter

​Choose how to set the endpoint

​Set it for the process

​Set it on one client

​Verify a lifecycle

​Handle errors

​Production checklist

Start a local adapter

Choose how to set the endpoint

Set it for the process

Set it on one client

Verify a lifecycle

Handle errors

Production checklist