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

Gruntwork AWS Terraform Module Libraries & Reference Architecture vs Hillstone Networks Hillstone CloudEdge Virtual-Firewall 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
61st
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Hillstone Networks Hillston...
Ranking in AWS Marketplace
460th
Average Rating
10.0
Number of Reviews
4
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.
Centralized security has protected hybrid workloads and provides deep visibility into cloud traffic
Cloud-native automation and IaC: Terraform support, auto-scaling templates, and API maturity lag behind Palo Alto VM-Series and FortiGate-VM. Dynamically scaling in public cloud requires more manual effort. Third-party integrations and ecosystem: fewer native connectors with SIEM/SOAR platforms, CSPM, and third-party tools compared to market leaders. Documentation and training material: technical documentation and community resources (forums, tutorials, KB) are more limited, which lengthens the learning curve for new teams. SASE/SSE capabilities: the integrated SASE/ZTNA offering is less mature compared to the convergence already provided by Fortinet or Palo Alto. Centralized multi-instance management: managing large fleets of virtual appliances could be smoother; centralized management (HSM) works, but some users would like more granularity and automation.
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
28%
Comms Service Provider
11%
Outsourcing Company
7%
Healthcare Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

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 Hillstone Networks Hillstone CloudEdge Virtual-Firewall?
Additional automation resources for AWS would also be helpful. More comprehensive CloudFormation or Terraform examples, deployment templates, and guidance for high-availability architectures could ...
What is your primary use case for Hillstone Networks Hillstone CloudEdge Virtual-Firewall?
We deploy Hillstone CloudEdge Virtual-Firewall in AWS to protect workloads hosted inside our VPC. We use it to inspect north-south traffic, enforce access-control policies, secure communication bet...
 

Comparisons

No data available
No data available
 

Overview

Find out what your peers are saying about Gruntwork AWS Terraform Module Libraries & Reference Architecture vs. Hillstone Networks Hillstone CloudEdge Virtual-Firewall and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.