5 min readTraditional VM + AWS

Burst a VCF database rehearsal into AWS

Inventory the VCF database VM, inspect AWS capacity, and validate that a one-host burst path stays compact and reversible.

Keep the application VMs in VCF, but use one AWS EC2 lane as a disposable migration target to rehearse cutover guardrails safely.

Sign in as admin6 stepsready

current raw commands

Step 1/6
lab db health
01

Check database health

Read VCF and VKS baseline

ready
lab db health
02

Inspect storage footprint

Read VCF and VKS baseline

pending
03

Read AWS compute baseline

Touch one cloud primitive

pending
04

Check same-day cost

Touch one cloud primitive

pending
05

Re-read the app dataset

Prove the workflow

pending
06

Audit cleanup posture

Prove the workflow

pending
>

Burst a VCF database rehearsal into AWS workflow

Expand to see the phase-by-phase operator sequence for this tab.

3 phases
>
phase 01Read VCF and VKS baselinelive

Read the VCF/VKS side first so the cloud touchpoint has context and a bounded blast radius.

2 cmds
  1. 01
    Verify the database VM is reachable from the VKS-backed data tier before touching anything external.
  2. 02
    Read disk consumption so the rehearsal target is sized from actual state instead of guesswork.
>
phase 02Touch one cloud primitivelive

Make one deliberately small cloud interaction that complements the VCF workload instead of replacing it.

2 cmds
  1. 01
    Confirm there is no stray host already running in the AWS rehearsal lane.
  2. 02
    Make the price of the burst visible before introducing even a tiny EC2 dependency.
>
phase 03Prove the workflowlive

Confirm the mixed workflow is observable end to end and leaves a clear operator narrative behind it.

2 cmds
  1. 01
    Show live application rows again so the audience can tie the cloud rehearsal back to the real VCF workload.
  2. 02
    Verify the AWS lane is still clean and any short-lived host would be tracked for removal.
live terminalproof@lab

Burst a VCF database rehearsal into AWS terminal

Guided proof playback. Commands stream automatically from start to finish.

command lineidle
proof@lab$

history buffer

Run a command to capture the last five entries here. Each row stays compact until you expand it.