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

Gruntwork AWS Terraform Module Libraries & Reference Architecture vs RedHat 9 with support by ProComputers 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
RedHat 9 with support by Pr...
Ranking in AWS Marketplace
643rd
Average Rating
9.0
Number of Reviews
13
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.
Gustavo Soares - PeerSpot reviewer
Analista de TI at App Vida
Achieved nonstop medical imaging access and secure patient data while automating daily operations
Regarding how RedHat 9 with support by ProComputers could be improved, I believe there are some points that could be enhanced, such as reducing the complexity and cost of licensing. The subscription model and socket counting can be complex and have a high cost for expanding smaller development environments. The learning curve could also be simplified: although security is impeccable, solving SELinux troubleshooting issues in advanced scenarios requires a considerable amount of diagnostic time for those who are just starting out. Documentation and the unified migration interface could be improved as well. The process of transitioning between major versions, such as from RedHat 8 to 9, has evolved a lot with Leapp, but it could still have tools such as simpler visual wizards and less dependency on manual scripts and customized scenarios. For me, the main improvement points in RedHat 9 with support by ProComputers are mainly the cost of the subscription model, which can be high when scaling new environments, and the complexity of configuring SELinux, which requires more time for the team to analyze errors when advanced blocks occur. I believe that RedHat 9 with support by ProComputers, to be a 10, would need to address what I mentioned in the previous answer. That would be broader documentation in the sense of providing tools with more visual and simple assistance, with less dependence on scripts, and reducing cost complexity. Some subscription and socket counting models can have a high cost for expansions of smaller development environments. I believe I have mentioned all the improvement suggestions I think are viable.
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 Enterprise6
 

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...
Ask a question
Earn 20 points
 

Comparisons

No data available
No data available
 

Overview

Find out what your peers are saying about Dice, Upbound, Tulip Interfaces and others in AWS Marketplace. Updated: October 2026.
921,523 professionals have used our research since 2012.