Prompt
Why are manual changes in AWS not showing up in Terraform?
Latest observation
Nov 7, 2026
OpenAI APIWeb search: off
Because Terraform only knows about what’s in its state file and what’s in your configuration files.
Common reasons manual AWS changes don’t show up:
-
Terraform doesn’t automatically watch AWS for changes
- If you change something manually in the AWS Console, Terraform won’t notice until you run:
terraform plan - Even then, it only compares AWS to Terraform state/config.
- If you change something manually in the AWS Console, Terraform won’t notice until you run:
-
The state file may be stale
- Terraform state records what it last created/applied.
- If someone changed the resource manually, the state may still say the old value.
- A
planshould detect drift, but only for managed resources and supported attributes.
-
The resource may not be managed by Terraform
- If the AWS resource was created manually and never imported, Terraform has no record of it.
- You’d need to import it:
terraform import <resource_address> <aws_resource_id>
-
The attribute may be ignored or not tracked
- Some fields are computed, ignored via
lifecycle { ignore_changes = [...] }, or not exposed well by the provider. - In those cases, changes may not appear in plans.
- Some fields are computed, ignored via
-
You may be looking at the wrong workspace/state/backend
- Different Terraform workspaces, different state files, or the wrong AWS account/region can make it look like changes aren’t reflected.
What to do:
- Run:
terraform plan - If needed, refresh state:
or older workflows:terraform apply -refresh-onlyterraform refresh - Check for
ignore_changes - Verify you’re using the correct workspace/state/account/region
- Import manually created resources if they should be managed by Terraform
If you want, I can help you debug a specific AWS resource and Terraform setup.