---
title: "Discussion on \"Terraform Plan Says Destroy and Recreate. What Now?\" | Hashnode"
description: "Discussion on \"Terraform Plan Says Destroy and Recreate. What Now?\". By Devang Pandya · Cloud Tech by Devang · Cloud • DevOps • AI — Made Simple\n\"Terraform plan shows a resource will be destroyed and recreated. What now?\" This is one of my favourite Terraform interview"
url: "https://hashnode.com/posts/terraform-plan-says-destroy-and-recreate-what-now/6af155ea633a03c5378bdbb9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Terraform Plan Says Destroy and Recreate. What Now?](https://cloudtechbydevang.hashnode.dev/terraform-plan-says-destroy-and-recreate-what-now?utm_source=hashnode&utm_medium=feed)

By Devang Pandya · Cloud Tech by Devang · Cloud • DevOps • AI — Made Simple "Terraform plan shows a resource will be destroyed and recreated. What now?" This is one of my favourite Terraform interview

4d ago · 4 min read · cloudtechbydevang.hashnode.dev  
Read the article

-   [#iac](https://hashnode.com/tag/iac)
-   [#devops](https://hashnode.com/tag/devops)
-   [#terraform](https://hashnode.com/tag/terraform)

## Written by

[Devang Pandya](https://hashnode.com/@cloudtechbydevang)

@cloudtechbydevang · Pune, India

  
[View profile](https://hashnode.com/@cloudtechbydevang)

Cloud | DevOps | AI made simple · 14+ yrs on AWS, GCP & Kubernetes

I help engineers learn cloud, DevOps, SRE and AI in simple English, crack interviews and follow clear roadmaps. 14+ years building and running platforms on AWS, GCP, Kubernetes and Terraform. One topic a day.

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[3d ago](https://hashnode.com/posts/terraform-plan-says-destroy-and-recreate-what-now/6af155ea633a03c5378bdbb9/comment/6af22556a1bd141a01e3a7dd)

The point about a data source returning a new latest AMI quietly triggering a replacement really stood out — that is the kind of surprise that does not show up in the change you actually made. I also liked the distinction between using ignore\_changes for something another system legitimately manages versus using it to silence a plan you do not understand. Do you have a rule of thumb for when a replacement on a stateful resource is worth handling with a migration plan instead of accepting the recreate and scheduling downtime?