1. sketch out the deployment - a few spaces, services with one or more units within them
2. describe the prerequisite steps to get that "consumable" by juju - i.e. EC2 CLI commands to create subnets within the VPC for the spaces
3. describe the juju CLI commands needed before deployment with spaces constaints
4. describe how to observe it worked (i.e. what addresses machines get in different spaces)

----------
region: eu-central-1
default-vpc: vpc-f8ea1191 (172.31.0.0/16)
default subnets: subnet-0fb97566 (172.31.16.0/20; default-1a); subnet-d27d91a9 (172.31.16.0/20; default-1b)
created "dmz" subnets (w/ auto-public-IP set): subnet-604dcd09 (172.31.64.0/22; dmz-1a); subnet-882d8cf3 (172.31.68.0/22; dmz-1b)
created "internal" subnets (w/o auto-public-IP set): subnet-5e4dcd37 (172.31.72.0/22; internal-1a); subnet-7c2c8d07 (172.31.76.0/22; internal-1b)

for i in default dmz internal; do juju space create $i; done

for i in subnet-0fb97566 subnet-d27d91a9; do juju subnet add $i default; done

for i in subnet-604dcd09 subnet-882d8cf3; do juju subnet add $i dmz; done

for i in subnet-5e4dcd37 subnet-7c2c8d07; do juju subnet add $i internal; done

juju deploy ubuntu u-default --constraints spaces=default

juju deploy ubuntu u-dmz --constraints spaces=dmz

juju deploy ubuntu u-internal --constraints spaces=internal

juju add-unit u-dmz

juju add-unit u-internal