iblai-api-infrastructurelisted

# iblai-api-infrastructure How the ibl.ai platform is **deployed and self-hosted** on infrastructure you control: the AWS topology, the tooling that provisions it, the SSO wiring for the edX LMS, and the agent-sandbox (claw) gateway servers that back live agent chat. Unlike the other `iblai-api-*` skills, this one is **not** a REST reference — it doesn't call `api.iblai.app`, and it needs no `IBLAI_ORG` / `IBLAI_API_KEY`. It documents server provisioning, `ssh` / CLI / Terraform / Ansible workflows, and provider consoles. Access to the ibl.ai Docker images and platform codebase requires a license — see [ibl.ai/contact](https://ibl.ai/contact). ## When to use - **Standing up the platform** on your own AWS account (or an existing server / bare metal) — start with [`references/infra-cli.md`](references/infra-cli.md), and see [`references/aws-architecture.md`](references/aws-architecture.md) for the resulting topology. - **Launching or rebuilding staging environments** from pre-baked AMIs via CI — [`references/ami-pipeline.md`](references/ami-pipeline.md). - **Adding Single Sign-On** (Google, Microsoft/Entra, Apple, or a generic OIDC provider) to the Open edX LMS — [`references/edx-sso.md`](references/edx-sso.md). - **Deploying an agent-sandbox gateway** (OpenClaw on a VPS/Hetzner, or NVIDIA NemoClaw) and connecting it to the platform — [`references/claw-servers.md`](references/claw-servers.md). For the **API side** — registering a claw instance, storing its devi