AWS Java SDK Guide

Cloud Adapter preserves the AWS service model at the application boundary. Your Java code keeps using AWS request and response types; the client factory selects the adapter endpoint. This example uses AWS SDK for Java 2.x and S3. Check S3 service coverage for the target environment and operations your application uses.

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

The AWS-standard S3 environment variable applies to every S3 client created by a supported SDK in this process:

export AWS_ENDPOINT_URL_S3="$T9_CLOUD_ADAPTER_ENDPOINT"

Build the client normally and omit endpointOverride:

import software.amazon.awssdk.auth.credentials.ProfileCredentialsProvider;
import software.amazon.awssdk.regions.Region;
import software.amazon.awssdk.services.s3.S3Client;

S3Client s3 = S3Client.builder()
    .region(Region.US_EAST_1)
    .credentialsProvider(ProfileCredentialsProvider.create("adapter-test"))
    .forcePathStyle(true)
    .build();

Set it on one client

Keep endpoint selection in one factory rather than scattering it through business logic.

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

import java.net.URI;
import software.amazon.awssdk.auth.credentials.ProfileCredentialsProvider;
import software.amazon.awssdk.regions.Region;
import software.amazon.awssdk.services.s3.S3Client;

URI endpoint = URI.create(System.getenv("T9_CLOUD_ADAPTER_ENDPOINT"));

S3Client s3 = S3Client.builder()
    .endpointOverride(endpoint)
    .region(Region.US_EAST_1)
    .credentialsProvider(ProfileCredentialsProvider.create("adapter-test"))
    .forcePathStyle(true)
    .build();

endpointOverride changes where the AWS request is sent. It does not change the service model, add unsupported operations, or provide credentials to the target service. Backend credentials stay in the service adapter configuration. An explicit client override takes precedence over AWS_ENDPOINT_URL_S3. Choose one approach for a client factory so configuration remains easy to audit. For SDK 1.x, use AmazonS3ClientBuilder with an endpoint configuration and path-style access. Do not mix 1.x and 2.x configuration examples in the same client factory.

Verify a lifecycle

Use a unique key and a small payload:

import java.nio.charset.StandardCharsets;
import java.util.Arrays;
import software.amazon.awssdk.core.ResponseBytes;
import software.amazon.awssdk.core.sync.RequestBody;
import software.amazon.awssdk.services.s3.model.GetObjectRequest;
import software.amazon.awssdk.services.s3.model.GetObjectResponse;

String bucket = System.getenv("TEST_BUCKET");
String key = "java/" + System.currentTimeMillis() + "-hello.txt";
byte[] expected = "hello through Cloud Adapter\n".getBytes(StandardCharsets.UTF_8);

s3.putObject(builder -> builder.bucket(bucket).key(key).contentType("text/plain"),
    RequestBody.fromBytes(expected));
s3.headObject(builder -> builder.bucket(bucket).key(key));

ResponseBytes<GetObjectResponse> downloaded = s3.getObjectAsBytes(
    GetObjectRequest.builder().bucket(bucket).key(key).build());
if (!Arrays.equals(expected, downloaded.asByteArray())) {
    throw new IllegalStateException("Downloaded object differs from uploaded bytes");
}

s3.deleteObject(builder -> builder.bucket(bucket).key(key));

Verify the object in the target service after putObject, not only through the adapter. That catches name, region, metadata, and identity mistakes that an origin-shaped response alone may hide.

Preserve failure evidence

Catch service and transport failures separately:

import software.amazon.awssdk.core.exception.SdkClientException;
import software.amazon.awssdk.services.s3.model.S3Exception;

try {
    s3.headObject(builder -> builder.bucket(bucket).key("missing-key"));
} catch (S3Exception error) {
    System.err.printf("status=%d requestId=%s code=%s%n",
        error.statusCode(), error.requestId(), error.awsErrorDetails().errorCode());
} catch (SdkClientException error) {
    System.err.println("No service response: " + error.getMessage());
}

Do not automatically retry a timed-out mutation until you have checked target state and the operation’s idempotency. Retain the SDK request ID and Cloud Adapter diagnostic headers in structured logs, while excluding credentials and payload bodies.

Explain one SDK request

For a difficult request, add a signed per-request x-t9-explain control and retain the returned report ID. ExecuteAndExplain performs the operation and preserves the ordinary SDK response; explicit Explain does not perform it and returns a diagnostic document that needs explanation-aware handling. The complete Explaining SDK Requests guide shows:

the Java 2.x request override, applied before SigV4 signing;
the exact mode and format values;
success, service-error and no-response handling;
report retrieval without replaying the original operation;
report-owner acknowledgment and out-of-band evidence sharing.

Do not use x-t9-explain: true for a dry run: that shorthand selects ExecuteAndExplain in Human format.

Production client checklist

Make endpoint, origin region, and credential provider explicit.
Bound connection, request, and retry timeouts for the target path.
Reuse the client; do not create one per request.
Test the exact paginator, waiter, conditional request, and multipart features the application uses.
Keep AWS-origin credentials separate from the adapter’s target-cloud identity.
Run an expected not-found or validation error to verify error translation.

For a deeper failure, preserve the SDK request ID and follow Debugging Your Adapters.

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 Java 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

Preserve failure evidence

Explain one SDK request

Production client checklist

​Start a local adapter

​Choose how to set the endpoint

​Set it for the process

​Set it on one client

​Verify a lifecycle

​Preserve failure evidence

​Explain one SDK request

​Production client checklist

Start a local adapter

Choose how to set the endpoint

Set it for the process

Set it on one client

Verify a lifecycle

Preserve failure evidence

Explain one SDK request

Production client checklist