The AWS CLI is on almost every developer's machine. Once you've built habits around commands like aws ec2 describe-instances, aws s3 cp, and eksctl create cluster, the idea of switching to different tooling for on-prem or edge deployments is genuinely painful. Most engineers assume there's no alternative, but with Spinifex there is. The CLI keeps working, and you just change the endpoint.
Why the CLI breaks in disconnected environments
The AWS CLI, every AWS SDK, and any Terraform provider wrapping them assume connectivity to amazonaws.com. In air-gapped environments such as secure facilities, disconnected field operations, and industrial sites with no public internet, that assumption is fatal. You lose not just the API but the entire ecosystem built on top of it, including Terraform plans, eksctl clusters, custom automation scripts, and CloudWatch integrations.
The typical workaround is maintaining a completely separate toolchain for on-prem: separate automation, separate monitoring, separate knowledge base. It's costly, it diverges from the cloud baseline over time, and it means engineers need to context-switch between two completely different operational models.
How Spinifex makes it work
