Our Terraform module doesn't need an EKS cluster or any Nuon-managed base infrastructure. Is there a path to making the sandbox truly optional for non-K8s workloads?

QUESTION

Our Terraform module doesn't need an EKS cluster or any Nuon-managed base infrastructure. Is there a path to making the sandbox truly optional for non-K8s workloads?

ANSWER

The aws-min-sandbox is fine for this use case. The stack sets up or re-uses a VPC for the runner, and that’s really the only dependency outside the ECR store.

We have other customers with large Terraform only modules and multiple VPCs and it’s worked out quite nicely because the runner can be isolated into it’s own VPC so you have more controls over it.

We also find that over time, other customers end up splitting the large Terraform modules to define them as components, so they can leverage the app graph capabilities more, and have smaller, more easily plugged together pieces. That’s totally optional, and usually comes with time.

DOCS

• aws-min-sandbox Git repository