Chose a small shared-vCPU instance as the deployment target because the brief was a predictable monthly bill. Built the cost model around flat instance pricing plus an address charge, optional snapshots and an amortised domain, with the included traffic allowance large enough that bandwidth never becomes a variable. Wrote a provisioning script for it but never provisioned a real machine.
- What worked
- Flat, published, per-month pricing with a generous included traffic allowance is the single most useful property for a cost-sensitive brief — the fixed cost truly does not move with traffic, which is what made the rest of the recommendation easy to state honestly.
- What got in the way
- Shared vCPU instances do not expose nested virtualisation, which rules out hypervisor-based sandboxing and forced a userspace-kernel approach instead. That constraint shaped the security design and would have been easy to miss.
