Cloud Adapter Overview

​

Who Cloud Adapter is for

• Software vendors expanding into new marketplaces. Reach customers in additional cloud marketplaces by running your product in those environments, while keeping its existing cloud integrations.
• Software vendors reducing infrastructure costs. Move your product to a lower-cost cloud or choose a more cost-effective backend for individual services, while retaining your existing SDKs, CLI commands and Terraform configurations.
• Enterprises using multiple clouds to control costs. Choose the cloud and backend that offer the best economics for each workload. Keep the APIs your applications already use across those environments, so each cloud choice does not require a separate application integration.
• Vendors deploying into customer environments. Offer the same product in a customer’s chosen cloud or on-prem environment, including deployments driven by data-location requirements.

​

How it works

1. Choose what to emulate and where to run it. Select the cloud APIs your software uses and the backend services that will provide them in the new environment.
2. Point your existing tools at Cloud Adapter. Configure the adapter endpoint in your SDK, CLI or Terraform provider, along with the application credentials.
3. Run your software. Cloud Adapter translates supported API calls to the selected backend and returns responses in the format your application expects.

​

Request and response architecture

​

Use a standard SDK

import os

import boto3
from botocore.config import Config

s3 = boto3.client(
    "s3",
    endpoint_url=os.environ["T9_CLOUD_ADAPTER_ENDPOINT"],
    config=Config(s3={"addressing_style": "path"}),
)

with open("./report.pdf", "rb") as body:
    s3.put_object(Bucket="media", Key="report.pdf", Body=body)

​

Examples with the AWS CLI

​

Store an object in Google Cloud Storage using S3

aws s3api put-object --bucket media --key report.pdf --body ./report.pdf \
  --endpoint-url "$T9_CLOUD_ADAPTER_ENDPOINT"

​

Read an Azure Cosmos DB item using DynamoDB

aws dynamodb get-item --table-name orders \
  --key '{"customerId":{"S":"C-42"},"orderId":{"S":"O-1042"}}' \
  --endpoint-url "$T9_CLOUD_ADAPTER_ENDPOINT"

​

Use Terraform or OpenTofu

provider "aws" {
  region = "us-east-1"

  endpoints {
    s3 = var.adapter_endpoint
  }

  s3_use_path_style = true

  # Keep provider startup on the configured S3 route. These switches avoid
  # metadata, region, credential-validation, and account-discovery calls.
  skip_credentials_validation = true
  skip_metadata_api_check     = true
  skip_region_validation      = true
  skip_requesting_account_id  = true
}

​

Get started with Cloud Adapter

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

​

Connect locally for development and testing

tensor9 adapt cloud connect \
  --dir "$HOME/tensor9/dev-adapter" --forward

eval "$(tensor9 adapt cloud connect \
  --dir "$HOME/tensor9/dev-adapter" --env)"
aws sts get-caller-identity

​

Choose your next step