Terradozer

Abstract

1. Introduction

terradozer Terraform destroy using the state only - no .tf files needed

Terradozer takes a Terraform state file as input and destroys all resources it finds in it - without needing any .tf files. This works currently only for resources of the Terraform AWS Provider. If you need support for any other provider, let me know, and I will try to help.

Allow terradozer pointing directly to a state file stored in S3, i.e., terradozer s3://path/to/terraform.tfstate

2. Objective

Terraform destroy without configuration files

This project demonstrates how Go, AWS, Terraform can be applied to a real-world Blockchain & Cloud Computing problem.

3. Key Features / Modules

• Nothing will be deleted without your confirmation. Terradozer always lists all resources first and then waits for
• Using the -force flag (dangerous!), terradozer can run in an automated fashion without human interaction and approval,
• Planned, if you want me to implement this, please upvote:
• Planned, if you want me to implement this, please upvote:

4. Technology Stack

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• Go 1.20 or later
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/jckuester/terradozer.git
cd terradozer

# install it into ./bin/
curl -sSfL https://raw.githubusercontent.com/jckuester/terradozer/master/install.sh | sh -s v0.1.2

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add a CI/CD pipeline with GitHub Actions
• Deploy to a public test network or cloud free tier
• Add monitoring and cost alerts

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Why does this problem need a blockchain or cloud-native design?
2. Explain the smart contract / infrastructure components and how they interact.
3. How are gas costs or cloud costs kept under control?
4. How is the system secured (keys, IAM, access control)?
5. How would the solution scale to many more users?

9. Source Code & License

This project is developed by jckuester and published on GitHub under the MIT License. Please follow the license terms and credit the original author when you use or modify this code.