---
title: "Discussion on \"Terraform Said My Whole Stack Was Deleted. It Was Looking at the Wrong AWS Account.\" | Hashnode"
description: "Discussion on \"Terraform Said My Whole Stack Was Deleted. It Was Looking at the Wrong AWS Account.\". What building an AI-assisted drift review taught me about the one thing `terraform plan` can't check for you."
url: "https://hashnode.com/posts/terraform-plan-wrong-aws-account/6ab5170aa89857a6d606c553"
---

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

Discussion

# [Terraform Said My Whole Stack Was Deleted. It Was Looking at the Wrong AWS Account.](https://gbadedata.hashnode.dev/terraform-plan-wrong-aws-account?utm_source=hashnode&utm_medium=feed)

What building an AI-assisted drift review taught me about the one thing \`terraform plan\` can't check for you.

Sep 24 · 7 min read · gbadedata.hashnode.dev  
Read the article

-   [#terraform](https://hashnode.com/tag/terraform)
-   [#aws](https://hashnode.com/tag/aws)
-   [#devops](https://hashnode.com/tag/devops)
-   [#claude-code](https://hashnode.com/tag/claude-code)
-   [#ai](https://hashnode.com/tag/ai)

## Written by

[Oluwagbade Odimayo](https://hashnode.com/@gbade-oj)

@gbade-oj · London, UK

  
[View profile](https://hashnode.com/@gbade-oj)

DevOps || Data Engineering || Data Science

## Responses 1

Markdown supported · ⌘↵ to post

[Brian · AI News](https://hashnode.com/@brianainews)

[Sep 25](https://hashnode.com/posts/terraform-plan-wrong-aws-account/6ab5170aa89857a6d606c553/comment/6ab5c34ac0a0c0f206a7af21)

Plan output that validates but fails at apply usually hides a provider drift. I pin provider versions and diff the real plan against the agent plan before any apply.
