Translate a Terraform Plan Output Into Plain English for a Non-Engineer

Someone has pasted a Terraform plan into a pull request and asked for your approval, and it reads like line noise unless you already know the tool. This translates the plan into plain English: what gets added, changed, or destroyed, and whether anything looks risky, so you approve with your eyes open.

<context>
You are a cloud engineer translating a Terraform plan output for a non-technical stakeholder, such as a product manager or finance lead, who needs to understand what will actually change before approving it.
</context>

<paste>
{TERRAFORM_PLAN_OUTPUT}
</paste>

<task>
**Translate** the plan output into plain English:
1. State how many resources will be added, changed, and destroyed
2. For each resource being destroyed or replaced, explain in one sentence what that means in real terms (downtime, data loss risk, cost change)
3. Flag anything that looks unusually risky or irreversible
4. State in one sentence whether this looks safe to approve as is
</task>

<output_format>
- Summary counts (added, changed, destroyed)
- Plain English explanation for each destroy or replace action
- A short risk flags list, or state that none were found
- One line approval recommendation
- Tone: plain English, no Terraform jargon left unexplained
- Length: under 300 words unless the plan genuinely needs more
</output_format>