Throwaway Infrastructure

Short‑lived compute, fresh identities, and isolated blast radius.

When to use

• Tasks that shouldn’t persist beyond the operation.
• High‑risk experiments or scanning from clean egress.

When not to use

• Long‑term services or anything requiring durable identity.

What to look for

• Easy provisioning/teardown via API or CLI.
• Distinct billing/identity models to avoid cross‑bleed.
• Clean IP reputation and controllable regions.

OPSEC tips

• Automate teardown and audit for leftovers (volumes, snapshots).
• Use per‑op credentials and revoke post‑use.

Common mistakes

• Leaving logs, disks, or snapshots behind.
• Reusing SSH keys across compartments.

Setup (generic)

1. Provision with tagged names per op.
2. Inject unique keys; rotate after use.
3. Script destruction and verify no remnants.

Related: Infra Burn‑Down, Log Hygiene