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

# Containers & orchestration

> Run your existing Amazon ECS setup through AI Reserve: repoint the endpoint, swap the credential, keep every command, SDK call, and script exactly as it is.

AI Reserve serves the **Amazon ECS API** at `https://api.aireserve.com`. Point
the AWS SDK or CLI you already use at that endpoint, use your AI Reserve API
key as the access key, and every ECS operation you call today (clusters, task
definitions, services, tasks, ECS Exec, tags, settings) runs on infrastructure
AI Reserve provisions for you. Nothing about your code, your task definitions,
or your deploy scripts changes beyond the client configuration.

> **[Repoint Amazon ECS](/containers/ecs)**
>
> The four client settings, for the CLI, shared config, boto3, JavaScript, Go, Java, and Terraform.

> **[Get an API key](/getting-started/get-an-api-key)**
>
> One key works for ECS, inference, and GPU infrastructure.

## How it works

The same shape as our OpenAI- and Anthropic-compatible endpoints: your client
talks to AI Reserve exactly as it would talk to the provider, and AI Reserve
talks to the provider on your behalf.

| Your client sends | AI Reserve does | You get back |
| - | - | - |
| A normal ECS request, SigV4-signed with your AI Reserve key as the access key id | Authenticates the key, re-signs the untouched request with its AWS credentials, forwards it to the regional ECS endpoint | Amazon ECS's own response, byte for byte |
| Any operation in the ECS API, in any region | No operation list, no translation, no rewriting — if ECS accepts it, it works | Standard ECS pagination, waiters, and typed exceptions |

Because the response is AWS's, every SDK feature built on the wire keeps
working: `aws ecs wait services-stable`, boto3 paginators, the JavaScript
SDK's `waitUntilTasksRunning`, typed `ClusterNotFoundException` handling, and
the SDK's own retry policy.

## What is different from calling AWS directly

* **The infrastructure lives in AI Reserve's AWS account.** Cluster, service,
  and task ARNs carry our account id, and the companion resources a task
  definition references — task execution roles, VPC subnets, security groups,
  CloudWatch log groups, private registry credentials — are ones we provision
  for you during onboarding and hand you the identifiers for. Public container
  images work as-is.
* **One credential.** Your AI Reserve API key replaces the AWS access key; the
  AWS secret key is unused (any value). Rotating or pausing the key in the
  [portal](https://portal.aireserve.com/keys) takes effect on the next call.
* **Our gates apply before AWS sees the request.** API-key checks, your
  organization's IP and country policies, and rate limits answer in the AWS
  error envelope (`AccessDeniedException`, `ThrottlingException`) so your
  existing error handling already covers them.
* **ECS only.** The endpoint serves Amazon ECS. Point other AWS services at
  AWS as you do today.

> [!NOTE]
>
> Containers & orchestration is in early access. Talk to your account team before pointing production traffic at it —
> they will set up the roles, networks, and registry access your task definitions reference.


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