Organizing files in a terraform codebase

Reading time: about 3 minutes

Organizing files in a terraform codebase

I started using terraform in about v0.8.3. At the time I thought “they’ll figure out how to organize my terraform codebase soon,” but they never have. This year v1.0 landed and you still cannot have folders in a terraform project, which is just bonkers to me.

devops_repo/terraform> find . -iname '*.tf' | wc -l

The terraform projects I manage often have hundreds of .tf files across dozens of “project domains” and at least a few AWS accounts. To reduce chaos and provide a safe infrastructure development environment, smaller discrete units of resources are broken apart from each other. Here is one file listing from a single environment, of a single application, for a single region:


Tenants of organization

Assuming a project otherwise has:

  1. Separate “states” for separate environments (Production, Staging, etc)
  2. Modules which represent groups of terraform resources which are versioned together (Webapp, VPC, etc)

An individual terraform project domain can easily become difficult to manage. Questions arise about where resources live on the disk, “Where is the configuration for the s3 bucket that holds user data?”

Here is my strategy:

  1. Terraform “meta” should be underscore prefixed:,
  2. File names should be prefixed with the technology at play: s3,ec2, etc.
  3. File names should represent the meaningful user-facing features the resources enable: uploads, etc.

Terraform “meta” files

Terraform “meta” files should be underscore prefixed. Upon upgrading from terraform < 0.13 with terraform 0.13upgrade, a “” file will be created for you. This practice leaves important terraform meta-configuration files scattered throughout an alphabetical file listing. Prefixing all meta-configuration files with an underscore hoists them to the top of an alphabetical file listing.

I tend to further break down the meta into:,, and Each of these tends to grow large enough that it’s easy to lose resources or configuration in the mess if they’re not separated out.

Technology prefixed filenames, and meaningful user-facing features

Simply naming a file will get you part of the way there in a small project. When you have two s3 buckets in an infrastructure, you’ll get lost quickly.

When a request comes in to modify the infrastructure, it’s usually stated in terms of the user-facing features it enables, e.g. “Task: allow users to upload files directly to S3.” As a result, a naming convention like should allow you to quickly locate the resources which need to be modified for an infrastructure update.

Date: 2021-Nov-11
Tags: terraform organizing aws
Previous: Managing services on macos with launchctl
Next: Rendering build details.json with Crystal