PierreBeucher / cloud-sandbox-manager

Manage sandbox AWS resources (EC2, DNS...) for training and workshop sessions using Pulumi and Ansible

Cloud Sandbox

Cloud Sandbox deploys sandbox EC2 instances on AWS. I personally used them for training sessions (Docker, Ansible, etc.) but they can be used for pretty much anything.

Sandboxes provides various tooling and services by default:

• Reachable via human-friendly domain names such as alice.training.crafteo.io
• code-server available on port 8080 (with in-browser terminal)
• Direct SSH access on port 22
• Tooling: Docker, Docker Compose, Git, etc.
• Kubernetes cluster with k3s (all instances form a single cluster)

graph TD
    HZ[Route53 Hosted Zone<br>training.crafteo.io]
    
    DNSA[DNS Record<br>alice.training.crafteo.io]
    DNSB[DNS Record<br>bob.training.crafteo.io]
    
    EC2A[EC2 instance]
    EC2B[EC2 instance]

    HZ-.-DNSA
    HZ-.-DNSB

    DNSA-->EC2A
    DNSB-->EC2B

Infra is deployed with Pulumi and each instance is provisioned by NixOS

Deploy Sandbox instances

Requirements

• Nix (provides development shell with Ansible, Pulumi and other dependencies)
• AWS account with permission on Route53 and EC2
• An existing Route53 Hosted Zone for sandbox domain name, such as training.crafteo.io

Deploy

Start a Nix shell with all required dependencies:

nix develop

Deploy sandbox:

# Set your sandbox name
export SANDBOX_NAME=crafteo

# Copy Pulumi template and adapt to your needs
cp pulumi/sandox/Pulumi.template.yaml pulumi/sandox/Pulumi.$SANDBOX_NAME.yaml

# Deploy sandbox environment with Pulumi and Ansible
# Prompts for sandbox environment to use
make up

# Or run a specific deployment step
make pulumi     # Deploy Pulumi infra
make inventory  # Generate Ansible inventory from Pulumi output
make playbook   # Run additional Ansible config (very short)

Tests

Run tests:

# Basic test
make test

# k3s test (needs k3sEnabled: true)
make test-k3s

Undeploy

Destroy Pulumi stack

make down