Cloud Infrastructure Deprecation and Cost Optimization Directive

Role: Head of Cloud FinOps & Infrastructure Architecture specializing in high-throughput cloud cost rationalization.

Context

• Target Execution Quarter: {{target_quarter}}
• Run-Rate Spend Variance: {{cloud_spend_overrun}}
• Target Clusters and Idle Workloads: {{underutilized_clusters}}
• Mandatory Decommissioning Cutoff: {{migration_deadline}}
• Engineering Teams in Scope: {{affected_engineering_squads}}
• Squad-Level Budget Cut Target: {{budget_reduction_target}}

Task

Draft a firm, actionable engineering-wide operational email directing squad leads to decommission underutilized infrastructure, right-size compute allocations, and achieve hard cost targets before the cutoff date.

Method

1. Frame {{cloud_spend_overrun}} in the context of organizational unit economics and infrastructure scaling efficiency.
2. Specify exact technical criteria for what classifies workloads in {{underutilized_clusters}} as dead or over-provisioned.
3. Detail the mandated percentage reduction specified in {{budget_reduction_target}} broken down by squad responsibility.
4. Define step-by-step migration, snapshotting, and teardown guardrails to prevent inadvertent data loss.
5. Establish automated shutdown protocols that will trigger if {{migration_deadline}} passes without compliance.
6. Detail exception approval criteria requiring VP-level architectural sign-off.
7. Provide concrete Terraform/Kubernetes audit commands to help squads identify idle compute instantly.

Constraints

• MUST set unequivocal technical standards for orphan workloads, idle RDS instances, and dangling volumes.
• MUST NOT compromise high-availability or disaster recovery standards for production tier services.
• MUST use clear, prescriptive language with unambiguous dates and targets.
• Email length must not exceed 450 words excluding sample command snippets.

Output format

• Subject line: ACTION REQUIRED: {{target_quarter}} Infrastructure Optimization & {{budget_reduction_target}} Deprecation Mandate
• Strategic Objective & Financial Context (2-3 sentences)
• Target Scope & Impacted Squads (bulleted table)
• Required Engineering Actions & Runbooks (step-by-step instructions)
• Enforcement Policy & Hard Deadlines (strict timeline breakdown)
• Self-Service Audit Commands (code snippet section)

Self-review

• Are {{target_quarter}}, {{cloud_spend_overrun}}, {{underutilized_clusters}}, {{migration_deadline}}, {{affected_engineering_squads}}, and {{budget_reduction_target}} clearly addressed?
• Is the tone authoritative yet operationally supportive?
• Are the technical instructions realistic for senior software engineers to execute rapidly?