Infrastructure Configured
December 17, 2019

Infrastructure Configured

Ronak Shah | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Terraform

Our AWS environment is defined through Terraform configuration scripts for the entire engineering organization. We manage our AWS environment using Terraform configuration files stored in our GitHub. We format the configuration files, run the plan command to review changes (additions, drops, and changes) when compared to production and then apply the changes if everything looks good!

Pros

  • Permissions.
  • Review plan before deployment.

Cons

  • Explaining what needs to be used for what for novice AWS users.
  • Very finicky with formatting. Should include formatting implicitly.
  • Prevents mistakes compared to deploying directly on live environment.
  • Configuration changes are reviewed before changes are made (using Git of course).
I haven't had to use it, since peers in my organization and help pages have been adequate whenever help is needed.

Do you think HashiCorp Terraform delivers good value for the price?

Not sure

Are you happy with HashiCorp Terraform's feature set?

Yes

Did HashiCorp Terraform live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of HashiCorp Terraform go as expected?

I wasn't involved with the implementation phase

Would you buy HashiCorp Terraform again?

Yes

I would say Terraform should be used within even a single-user environment as it prevents costly mistakes if you review plan outputs. I would strongly recommend everyone managing their cloud environment to lock up the ability to make changes through the console and only allow changes to be deployed through configuration stored in the files.

Comments

More Reviews of HashiCorp Terraform

  1. Home
  2. Configuration Management Tools
  3. HashiCorp Terraform Reviews
  4. User Review of HashiCorp Terraform