No more typing reviews! Try our Samantha, our new voice AI agent.

Gruntwork AWS Terraform Module Libraries & Reference Architecture vs Jenkins on CentOS 10 comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Gruntwork AWS Terraform Mod...
Ranking in AWS Marketplace
54th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Jenkins on CentOS 10
Ranking in AWS Marketplace
449th
Average Rating
8.6
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Manas Kashyap - PeerSpot reviewer
Senior Dev Ops Engineer at 11 East Capital
Infrastructure as code has boosted multi-account deployments but needs less tool lock-in
The best features of Gruntwork AWS Terraform Module Libraries & Reference Architecture are that they offer production-grade option modules that are available for everything I can think of, such as VPC, EKS, RDS, ALB, NLB, or any Lambda functions, as well as the Terragrunt-first architecture, which emphasizes that DRY configs are there, remote states, and multiple account deployment can be used with that. It also maintains security best practices, including default IAM, least privileged right access, secure networking, logging, auditability, and CIS controlled network. Gruntwork AWS Terraform Module Libraries & Reference Architecture has positively impacted my organization, as previously things were done manually, but now we have everything in place. All the Terraform configurations are in the form of infrastructure as code that's available. I find Gruntwork AWS Terraform Module Libraries & Reference Architecture very good for easier management, as our whole infrastructure is there in the form of code. There are fewer chances of error because everything is in a formal structure, infrastructure as code, which can be reviewed by other people as well. The production speed and the deployment speed are quite high; if anything comes up, we don't need to go and check it. We can just write a module inside it, and it will create that thing using the other modules that are there.
Lucas Dantas - PeerSpot reviewer
Fullstack Developer at Not Provided
Automation has accelerated deployments and standardizes pipelines while reducing operational errors
To improve Jenkins on CentOS 10, there are some challenges we ran into, especially when we first started using it. We missed clearer documentation, both for Jenkins as code and for some environment configurations. As a result, a lot of configurations were learned manually through tests with the team. We also missed more stable plugin updates. We had many problems with incompatibility between plugin versions in Jenkins on CentOS 10. What makes those situations challenging is that we had problems starting and restarting the Jenkins on CentOS 10 application when we needed to reuse plugins from the previous version. Once we updated some plugins to the required version, others became incompatible with the current version. It became a cycle where we had to update Jenkins on CentOS 10, the versions of the plugins we used, and the versions of the plugins they depended on, which made configuration and startup quite difficult in some cases.
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
921,523 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
27%
Comms Service Provider
9%
Manufacturing Company
7%
Outsourcing Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise2
Large Enterprise8
 

Questions from the Community

What is your experience regarding pricing and costs for Gruntwork AWS Terraform Module Libraries & Reference Architecture?
My experience with pricing, setup cost, and licensing is that everything is very straightforward and easy to understand.
What needs improvement with Gruntwork AWS Terraform Module Libraries & Reference Architecture?
Gruntwork AWS Terraform Module Libraries & Reference Architecture can be improved in that the module update process is somewhat of a pain point. As modules evolve, upgrading existing environmen...
What is your primary use case for Gruntwork AWS Terraform Module Libraries & Reference Architecture?
The main use case for Gruntwork AWS Terraform Module Libraries & Reference Architecture is to standardize how our AWS infrastructure is provisioned using Terraform. As our engineering team star...
What needs improvement with Jenkins on CentOS 10?
Jenkins on CentOS 10 is somewhat dated when compared to other pipelines. I would suggest improving the build performance and using distributed agents instead of running every build on the controlle...
What is your primary use case for Jenkins on CentOS 10?
For Jenkins on CentOS 10, we are mostly using it as a CI/CD pipeline to deploy our traditional applications on our healthcare platform.
What advice do you have for others considering Jenkins on CentOS 10?
I would rate Jenkins on CentOS 10 overall as an eight on a scale of one to ten. From my perspective, Jenkins on CentOS 10 has both advantages and disadvantages. Based on that consideration, I chose...
 

Comparisons

No data available
No data available
 

Overview

Find out what your peers are saying about Gruntwork AWS Terraform Module Libraries & Reference Architecture vs. Jenkins on CentOS 10 and other solutions. Updated: October 2026.
921,523 professionals have used our research since 2012.