Login

SDKs & Terraform overview

Last updated: June 5, 2026

American Cloud ships official, typed SDKs for the three languages most infrastructure code is written in, plus an official Terraform provider for declarative infrastructure as code. All of them derive from the same OpenAPI document that drives the platform API, so they cover the public surface — virtual machines, networking, storage, Kubernetes, DNS, and more — with the same shapes the API actually speaks.

ToolPackageInstall
TypeScript / JavaScript@americancloud/sdk (npm)npm install @americancloud/sdk
Gogithub.com/American-Cloud/americancloud-sdk-gogo get github.com/American-Cloud/americancloud-sdk-go@latest
Pythonamericancloud (PyPI)pip install americancloud
TerraformAmerican-Cloud/americancloud (Terraform Registry)required_providers block — see the quickstart

Each language page covers installation, authentication, and working first calls. For the complete operation-by-operation reference, use the API documentation — every endpoint there maps directly to an SDK method.

Authentication

All three SDKs authenticate the same way: an API key pair passed to the client at construction. Create and manage keys at console.americancloud.com/api-keys.

  • The client secret is shown once at creation — store it securely (an environment variable or secrets manager, never your repo). If it's lost, revoke the key and create a new one.
  • Keys are scoped at creation: read-only keys can call GET endpoints only; read-write keys have full access to resource management. Start integrations with a read-only key and upgrade when you're ready to create resources.

Versioning: the SDK version is the API version

The SDKs are versioned in lockstep with the platform API: SDK 1.3.0 is generated from API 1.3.0. The version you pin tells you exactly which API contract you're coding against — there's no separate compatibility matrix to consult. Pin exact versions and upgrade deliberately; each SDK's changelog describes what changed in the API surface between releases.

Supply-chain posture

The npm and PyPI packages are published via Trusted Publishing (OIDC) — no long-lived tokens — and npm releases carry provenance attestations, cryptographic proof the package was built from the public repository. The Go module is consumed straight from the public GitHub repo via the Go module proxy. Source for all three lives under github.com/American-Cloud.

SDK, Terraform, or MCP?

Three ways in, by how you work:

  • SDKs — you're writing software (services, CI jobs, internal tooling) that manages American Cloud resources imperatively.
  • Terraform — you want infrastructure declared in versioned files, with plan and apply as the change-control loop. The provider is built on the Go SDK, so it inherits the same contract.
  • MCP server — you want an AI assistant to manage infrastructure conversationally (itself built on the TypeScript SDK); the Deploy with AI recipes show what it can do.

Next steps