# Spinifex Documentation > Spinifex is an open-source infrastructure platform that brings the core AWS services — EC2, VPC, EBS, S3, IAM, STS, IMDS, ECS and EKS — to bare-metal, edge and on-premise hardware. You drive it with the ordinary AWS CLI, SDKs and Terraform/OpenTofu against a local endpoint, so existing AWS workloads and IaC move across largely unchanged. Every entry below is dated with the last change to its source document, newest across the whole site being 2026-09-15. The full text of every document, in one file, is at https://docs.mulgadc.com/llms-full.txt To point a coding agent at an existing Spinifex cluster, see https://docs.mulgadc.com/agent-setup/prompt.md ## Installation Updated: 2026-09-14 - [Single-Node Install](https://docs.mulgadc.com/docs/install) (updated 2026-08-19): Install Spinifex on one Ubuntu or Debian server with the binary installer and get an AWS-compatible EC2, S3, and VPC stack running on your own hardware. - [Multi-Node Install](https://docs.mulgadc.com/docs/install-multi-node) (updated 2026-09-14): Deploy Spinifex across three or more servers to form an availability zone with clustered OVN, replicated object storage, and automatic cluster formation. - [Source Install](https://docs.mulgadc.com/docs/install-source) (updated 2026-08-19): Build Spinifex from source on Ubuntu or Debian for development, custom builds, or contributing changes, then install and run the resulting binaries locally. - [Air-Gapped Install](https://docs.mulgadc.com/docs/install-airgapped) (updated 2026-08-21): Deploy Spinifex in environments without internet connectivity. Covers using a pre-built release tarball, mirrored APT packages, and locally-staged cloud images. - [Bootable USB Install](https://docs.mulgadc.com/docs/install-usb) (updated 2026-08-21): Install Spinifex on bare-metal x86 hardware by flashing the Spinifex ISO to a USB drive, booting the target server from it, and wiping the disk you select. ## Administration Updated: 2026-09-10 - [Setting Up Your Cluster](https://docs.mulgadc.com/docs/setting-up-your-cluster) (updated 2026-09-10): Import an AMI, create an SSH key pair and a VPC with a public subnet, then launch your first EC2 instance and connect to it on a fresh Spinifex cluster. - [Spinifex Admin CLI](https://docs.mulgadc.com/docs/spinifex-admin-cli) (updated 2026-08-21): Complete reference for spx, the Spinifex admin CLI: initialise a cluster, manage accounts and nodes, drive the VM lifecycle, and start or stop services. - [Updating Spinifex](https://docs.mulgadc.com/docs/update) (updated 2026-09-10): Upgrade an existing Spinifex install with the same installer used to deploy it, or take the manual path to review configuration migrations before applying them. ## Compute and Networking Updated: 2026-09-10 - [VPC Networking](https://docs.mulgadc.com/docs/vpc-networking) (updated 2026-09-10): How Spinifex implements AWS-compatible VPC networking on bare metal with OVN: public and private subnets, security groups, route tables, and Elastic IPs. - [Launching Instances](https://docs.mulgadc.com/docs/launching-instances) (updated 2026-08-19): Launch, manage, and connect to EC2-compatible virtual machines on Spinifex, with cloud-init, SSH key injection, VPC networking, and AWS lifecycle operations. - [Placement Groups](https://docs.mulgadc.com/docs/placement-groups) (updated 2026-08-19): Create and manage spread and cluster placement groups to control how Spinifex places EC2 instances across physical hosts for fault isolation or low latency. - [GPU Passthrough](https://docs.mulgadc.com/docs/gpu-passthrough) (updated 2026-08-19): Configure VFIO GPU passthrough on a Spinifex node to bind NVIDIA or AMD GPUs to guest VMs and expose GPU-enabled EC2 instance types to your workloads. ## Identity and Access Updated: 2026-09-14 - [IAM Users, Policies, and Access Keys](https://docs.mulgadc.com/docs/iam-users-and-policies) (updated 2026-09-14): Create AWS IAM users, issue and rotate access keys, and write and attach JSON policies that control exactly what each user can do in a Spinifex account. - [IAM Groups for Shared User Permissions](https://docs.mulgadc.com/docs/iam-groups) (updated 2026-09-14): Organise AWS IAM users into groups, manage membership, and attach managed or inline policies once for the whole team instead of granting them user by user. - [IAM Roles and Instance Profiles for EC2](https://docs.mulgadc.com/docs/iam-roles-and-instance-profiles) (updated 2026-09-14): Create AWS IAM roles with trust policies, wrap them in instance profiles, and launch EC2 instances that receive credentials with no static access keys at all. - [STS Temporary Credentials and AssumeRole](https://docs.mulgadc.com/docs/sts) (updated 2026-09-14): Use AWS STS to issue temporary credentials: assume an IAM role, request a session token, or federate Kubernetes workloads with OIDC web identity on Spinifex. - [IMDS: Instance Metadata Service (IMDSv2)](https://docs.mulgadc.com/docs/imds) (updated 2026-09-14): Query AWS instance metadata, read user data, and fetch short-lived IAM role credentials from inside a guest VM using IMDSv2 session tokens on Spinifex. ## Containers Updated: 2026-09-14 - [EKS (Managed Kubernetes)](https://docs.mulgadc.com/docs/eks) (updated 2026-09-14): Provision an AWS-compatible EKS control plane and managed node group on Spinifex, wire up the VPC, IAM, and security groups, then deploy your first workload. - [ECS (Elastic Container Service)](https://docs.mulgadc.com/docs/ecs) (updated 2026-08-19): Create an ECS cluster on Spinifex, register a task definition, boot container instances, run tasks, and front a service with an Application Load Balancer. - [ECR (Container Registry)](https://docs.mulgadc.com/docs/ecr) (updated 2026-08-19): Store and serve container images from Spinifex's AWS-compatible ECR: create a repository, authenticate Docker, push and pull images, and let EKS workers pull. ## Migration Updated: 2026-08-19 - [Moving an AWS Workload to Mulga](https://docs.mulgadc.com/docs/moving-aws-workload) (updated 2026-08-19): Move existing AWS workloads onto Spinifex using compatible APIs, SDKs, and Terraform across EC2, VPC, EBS, S3, IAM, STS, ELBv2, ACM, ECR, ECS, and EKS. - [Hybrid Sync](https://docs.mulgadc.com/docs/hybrid-sync) (updated 2026-08-19): Synchronise data bidirectionally between Spinifex and AWS when connectivity allows, so local infrastructure stays usable at intermittently connected sites. ## Terraform Workbooks Updated: 2026-09-14 - [Bastion with Private Subnet](https://docs.mulgadc.com/docs/bastion-private-subnet) (updated 2026-08-19): Deploy a VPC with public and private subnets on Spinifex, then use a bastion host as the only route to an isolated EC2 instance that has no internet access. - [S3-Backed Web App](https://docs.mulgadc.com/docs/s3-webapp) (updated 2026-08-19): Deploy a Flask file-sharing app on EC2 backed by S3 (Predastore) with Terraform, using an IAM instance profile and short-lived STS credentials from IMDS. - [Nginx Web Server (Load Balanced)](https://docs.mulgadc.com/docs/nginx-alb) (updated 2026-08-19): Deploy a VPC with two private EC2 instances running Nginx behind an internet-facing Application Load Balancer on Spinifex, using Terraform or OpenTofu. - [Nginx Web Server](https://docs.mulgadc.com/docs/nginx-webserver) (updated 2026-08-19): Provision a VPC, public subnet, internet gateway, route table, security group, and an EC2 instance that installs and starts Nginx from cloud-init user-data. - [EKS Quickstart](https://docs.mulgadc.com/docs/eks-quickstart) (updated 2026-08-21): Stand up a minimal managed Kubernetes cluster with Terraform: a VPC, IAM roles, an EKS cluster, a worker node group, an ECR repository, and a demo web app. - [EKS HTTPS Ingress (LBC + ACM)](https://docs.mulgadc.com/docs/eks-https-ingress) (updated 2026-08-21): Serve a demo app over HTTPS on EKS using the AWS Load Balancer Controller addon and an ACM certificate, with an internet-facing ALB built from an Ingress. - [GitOps on EKS (Argo CD + EBS-CSI)](https://docs.mulgadc.com/docs/eks-gitops-argocd) (updated 2026-08-21): Deliver an app to EKS with GitOps: the Argo CD addon syncs it from git, an EBS-CSI PersistentVolume holds its state, and HTTPS is served via LBC and ACM. - [ECS Quickstart](https://docs.mulgadc.com/docs/ecs-quickstart) (updated 2026-08-19): Stand up a full AWS-compatible ECS stack with Terraform: a VPC, IAM roles, a cluster, a task definition, container instances, and a load-balanced service. - [RDS Quickstart (PostgreSQL)](https://docs.mulgadc.com/docs/rds-quickstart) (updated 2026-09-14): Stand up a managed PostgreSQL database on Spinifex with Terraform: a VPC, DB subnet group, parameter group, aws_db_instance, and a client VM that runs psql. ## Security and Compliance Updated: 2026-09-04 - [Flaw Remediation Policy](https://docs.mulgadc.com/docs/flaw-remediation-policy) (updated 2026-08-21): CVSS-tiered SLAs for identifying, reporting, and correcting software flaws in Spinifex and its direct dependencies, for maintainers and CMMC Level 1 operators. - [Malware Protection](https://docs.mulgadc.com/docs/malware-protection) (updated 2026-08-19): Operator guide to host-based malware protection and file integrity monitoring on the Linux hosts running Spinifex services, aligned to CMMC Level 1 needs. - [Media Sanitization and Disposal](https://docs.mulgadc.com/docs/media-sanitization) (updated 2026-08-21): Operator guide to sanitizing and disposing of storage media used by Spinifex nodes, covering system disks, Viperblock and Predastore volumes, and key tokens. - [External Connection Inventory](https://docs.mulgadc.com/docs/network-connections) (updated 2026-09-04): Operator inventory of every inbound listener and outbound connection on Spinifex nodes, with ports, protocols, and purpose, for documented CMMC Level 1 sites. - [Physical Security Operator Guide](https://docs.mulgadc.com/docs/physical-security-guide) (updated 2026-08-21): Operator guide to physical access controls, visitor handling, access logging, and access-device management at sites hosting Spinifex nodes and network gear. ## Coverage Updated: 2026-09-15 - [AWS API Coverage](https://docs.mulgadc.com/coverage) (updated 2026-09-15): The AWS API operations Spinifex serves, generated from its gateway dispatch tables and the pinned AWS SDK service models on each build, service by service. - [EC2 API Coverage](https://docs.mulgadc.com/coverage/ec2) (updated 2026-09-15): The Amazon EC2 API operations Spinifex implements, covering instances, EBS volumes, VPC networking, tags, security groups and the rest of the compute surface. - [IAM API Coverage](https://docs.mulgadc.com/coverage/iam) (updated 2026-09-15): The AWS IAM API operations Spinifex implements, covering users, roles, policies, groups, instance profiles and the access keys that authenticate them. - [S3 API Coverage](https://docs.mulgadc.com/coverage/s3) (updated 2026-09-15): The Amazon S3 API operations Predastore serves on the platform's S3 endpoint, covering buckets, objects, multipart uploads and the policies that guard them. - [EKS API Coverage](https://docs.mulgadc.com/coverage/eks) (updated 2026-09-15): The Amazon EKS API operations Spinifex implements, covering clusters, nodegroups, add-ons, access entries and the identity providers they authenticate. - [ECS API Coverage](https://docs.mulgadc.com/coverage/ecs) (updated 2026-09-15): The Amazon ECS API operations Spinifex implements, covering clusters, services, tasks, container instances and the task definitions they are launched from. - [ECR API Coverage](https://docs.mulgadc.com/coverage/ecr) (updated 2026-09-15): The Amazon ECR API operations Spinifex implements, alongside the OCI distribution endpoint that carries the image layers for every repository it serves. - [ELBv2 API Coverage](https://docs.mulgadc.com/coverage/elbv2) (updated 2026-09-15): The Elastic Load Balancing v2 API operations Spinifex implements, for both the Application and Network Load Balancers it serves, listeners and target groups. - [RDS API Coverage](https://docs.mulgadc.com/coverage/rds) (updated 2026-09-15): The Amazon RDS API operations Spinifex implements, for the managed PostgreSQL and MariaDB engines it offers, covering instances, snapshots and parameters. - [ACM API Coverage](https://docs.mulgadc.com/coverage/acm) (updated 2026-09-15): The AWS Certificate Manager API operations Spinifex implements, generated from the gateway dispatch tables and the pinned AWS service model on each build. - [STS API Coverage](https://docs.mulgadc.com/coverage/sts) (updated 2026-09-15): The AWS STS API operations Spinifex implements, covering role assumption, session tokens and web identity federation (IRSA), with those it does not offer. ## Hardware Updated: 2026-09-14 ### Supermicro - [Multi-Tenant AI on Supermicro H14 with AMD MI350X](https://docs.mulgadc.com/hardware/supermicro/smci-h14) (updated 2026-09-14): Provision isolated GPU VMs for simultaneous AI workloads on a Supermicro H14 bare-metal node with AMD MI350X GPUs, using Spinifex's EC2-compatible API. - [Mixed AI Workloads on a Single H200 Chassis: Guest-Managed MIG](https://docs.mulgadc.com/hardware/supermicro/smci-mig) (updated 2026-09-14): Install Spinifex from source, configure host-local networking, attach Predastore storage, and run four concurrent AI workloads across guest-managed MIG slices. - [Spinifex EKS AI Platform on Dual RTX Pro 6000 Baremetal](https://docs.mulgadc.com/hardware/supermicro/rtx-pro-6000) (updated 2026-09-14): Deploy a GPU-accelerated AI inference platform — an OpenAI-compatible LLM API and a real-time CV stream — on Kubernetes on bare metal with standard AWS tooling. - [Arcee Trinity 400B FP8 on AMD MI350X with Spinifex](https://docs.mulgadc.com/hardware/supermicro/arcee-trinity-mi350x) (updated 2026-09-14): Provision, load, and benchmark arcee-ai/Trinity-Large-Preview-FP8 across two AMD MI350X GPUs on a Supermicro H14 node using Spinifex's EC2-compatible API. ### Cisco UCS - [Cisco UCS: AWS-compatible cloud at the edge](https://docs.mulgadc.com/hardware/cisco/platform-benchmark) (updated 2026-09-14): Place EC2 instances, EBS volumes, S3 object storage and Kubernetes workloads on a resilient three-node Cisco UCS cluster, using familiar AWS APIs and tooling. - [Spinifex Vision Pipeline on Cisco UCS](https://docs.mulgadc.com/hardware/cisco/vision-pipeline) (updated 2026-09-14): A YOLO11m detection and Qwen2-VL captioning pipeline streaming from a shared Predastore bucket across two EC2 instances, with Intel AMX and NVIDIA L4 compared. - [vLLM Serving on Cisco UCS: Intel AMX vs NVIDIA L4](https://docs.mulgadc.com/hardware/cisco/llm-serving) (updated 2026-09-14): Qwen2.5-7B-Instruct served with vLLM on a Cisco UCS Spinifex cluster, comparing Intel AMX-accelerated CPU serving with NVIDIA L4 GPU serving under concurrency. ### OnLogic - [Single-Node Spinifex on OnLogic HX401](https://docs.mulgadc.com/hardware/onlogic/hx401) (updated 2026-09-14): EC2, EBS and S3 on a single fanless OnLogic HX401 — the full Spinifex service set on a passive-cooled industrial node for factory and remote edge deployments.