Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Solution for all provisioning needs
What do you like best about the product?
It is great at what it does. Easily pluggable to existing workflows. The configurations have a learning curve but worth it. It is a polished product even when it has not been around for so long yet.
What do you dislike about the product?
It handles provisioning well but not good for configuration management and you need to implement something like ansible, chef in conjunction. They already have decent provisioning support so it becomes a bit difficult to pitch it to management to go for it.
What problems is the product solving and how is that benefiting you?
We are using Terraform for our cloud VM provisioning. It has brought us closer to our goal of becoming cloud-agnostic.
- Leave a Comment |
- Mark review as helpful
The best and most user friendly cloud automation tool
What do you like best about the product?
This is very easy to use and learn. I can't imagine the value it brings to Operations and deployment teams.
What do you dislike about the product?
During a failed TF run, the error detail is insufficient at certain circumstances to understand the reason. Hence, I was left clueless at times and got stuck not being able to fix my code.
What problems is the product solving and how is that benefiting you?
Automating cloud architectures for CI/CD
Recommendations to others considering the product:
Improve the debugging capabilities.
DevOps Ease with Terraform
What do you like best about the product?
The best aspect of terraform is HCL. The language makes things easy to read and present, allowing less knowledgeable employees to still follow along with easy. Additionally, the modular approach of terraform is easy to use, as one variable change in the root module will be displayed where I want.
What do you dislike about the product?
I dislike the ability to make one ELB module in the root module, for example, and reuse the ELB module in different places. Essentially, if there was a way to have multiple sources per module, my life would be much easier and this would help IMMENSELY with larger scale projects like the one I'm working on now.
What problems is the product solving and how is that benefiting you?
We had the problem of a disorganized and rather complicated approach to creating cloud formations/stacks on AWS. The benefits of modularization supersede our current approach and we love the ability to plan and see what will happen before anything actually occurs, along with keeping better control of our states.
Recommendations to others considering the product:
Take your time with understanding modules. It takes time to implement and fully understand.
Powerful tool with growing pains
What do you like best about the product?
Terraform provides an easy to use, declarative, cloud-agnostic way to manage your infrastructure. There is a lot of power in being able to describe how you want your infrastructure to look, and then allowing Terraform to create/modify/destroy as needed. The fact that you can use the same tool for all major cloud providers, most smaller ones, and even many tools and services in the cloud space, is helpful to keep you from having to learn more tools to work with each service.
What do you dislike about the product?
Terraform is a relatively young tool (as is the language, HCL, that is uses) and continues to see rapid changes. This can be hard to keep up with, and you might need to update templates from time to time to make use of newer versions (and the included fixes; there are still a fair amount of bugs but Hashicorp is quick to fix them, and it's getting more stable quickly). Fortunately, version 12 is coming out soon, which will bring a lot of breaking changes, but with it, many needed improvements, and a promise from Hashicorp to stabilize after that.
What problems is the product solving and how is that benefiting you?
Streamlining the creation and management of infrastructure. Allowing users to manage their infrastructure without having to learn the specific provider it's running on.
Recommendations to others considering the product:
Read through the documentation. While not as exhaustive as it needs to be, what it does cover is very helpful and outfits to use Terraform successfully. If you face issues, reach out to Hashicorp, especially on Github, as they are very responsive and helpful
Infrastructure as code done right.
What do you like best about the product?
I like how it's free, community driven and constantly developing. It's easy to find solutions to problems in thriving community. There are so many users.
What do you dislike about the product?
It's hard to say I dislike anything about Terraform. I just find it difficult to learn it all! There is so much documentation and so many possibilities.
What problems is the product solving and how is that benefiting you?
Automated infrastructure deployment and maintenance. Realized benefits such as developing code with a team safely and easily.
Recommendations to others considering the product:
Take a look at other IaC platforms, but this open source one is great and very flexible.
Perfect to programmably start multiple instances on your platform of choice.
What do you like best about the product?
There is a lot of modules that can handle almost everything. Also, it is really simple to learn.
What do you dislike about the product?
Some feature are missing (ex. : read env variables) and it can feel a little bit `hacky` (ex. : trying to do a `else if` equivalent).
What problems is the product solving and how is that benefiting you?
We use it to start a cluster on different providers. Terraform allow us to exdents and reduce the nodes number in 2 minutes.
Using Terraform for your AWS infrastructure
What do you like best about the product?
Terraform is a terrific implementation of the "Infra as code" concept. The modelling of entities and the relationships between them are clear and easy to conceptualize.
What do you dislike about the product?
Can be difficult to get the exact correct configuration sometimes. Lack of good code examples - Sometimes you really need to do extensive searches of Github in order to find the exact example that relates to you.
What problems is the product solving and how is that benefiting you?
Infra as code - Describe your entire infra in a versioned repository. Tear down and set up infra at the push of a button.
Recommendations to others considering the product:
If you are using AWS, and the API GW in particular, currently the biggest pitfall (and pet peeve of mine) is the fact that when you define an API GW resource, Terraform will not redeploy the affected stage. Also, it's crucial that you use a remote (not local) state so that all team members can work on the same state.
De-facto Infra as Code Tool
What do you like best about the product?
Mature-ish, large user base, easy to use, syntax good enough (e.g. not as verbose as Cloudformation), helpful-ish error messages.
What do you dislike about the product?
No easy roll-backs, not as good support as aws for other cloud providers, terraform state need to be dealt with extreme care as a corrupted state is a big hassle.
What problems is the product solving and how is that benefiting you?
Infrastructure as code, code deployments with Jenkins
Recommendations to others considering the product:
Don't have any other choice, but that's not to say this is a bad tool. It is good enough.
Architecture as code - done right
What do you like best about the product?
"Infrastructure" as code is a brilliant description of what Hashicorp have done with Terraform. The HCL syntax is incredibly easy to use, along with their intuitive and powerful CLI tool
What do you dislike about the product?
As long as Terraform is implemented correctly, there isn't much to dislike. There isn't great support for Terraform in a few CI tools, unfortunately.
What problems is the product solving and how is that benefiting you?
We're using terraform to bootstrap our future container infrastructure. But in the meantime we're deploying services onto pre-provisioned architecture.
showing 81 - 89