The main use case for Gruntwork AWS Terraform Module Libraries & Reference Architecture is to create a VPC, as well as EKS, RDS, S3 applications, and have all these Terraform states in an S3 bucket so that it's maintained, with the whole infrastructure maintained.

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.

Gruntwork AWS Terraform Module Libraries & Reference Architecture should have less Terragrunt lock-in, as it's heavily tied to Terragrunt. AWS is moving very fast, and with AWS bringing your own EKS cluster, those new things that are coming immediately can be modulated inside Gruntwork. With the fast pace of AWS, Gruntwork should keep up and keep on developing those modules.

I have been using Gruntwork AWS Terraform Module Libraries & Reference Architecture for the past two years, and I have worked with Gruntwork AWS Terraform modules.

Gruntwork AWS Terraform Module Libraries & Reference Architecture is very much stable.

Gruntwork AWS Terraform Module Libraries & Reference Architecture's scalability is very high; for different environments, we can just mention it there, and it can handle all those environments.

Customer support for Gruntwork AWS Terraform Module Libraries & Reference Architecture is really nice, as there are a lot of people outside of customer support who can answer questions and who are using this application.

We previously used Terraform before adopting Gruntwork AWS Terraform Module Libraries & Reference Architecture. It helps in multi-cloud as well as multi-region developments, QA, and everything in between. Terraform works on a single module, so we moved to Gruntwork AWS Terraform Module Libraries & Reference Architecture.

We can use the same Gruntwork AWS Terraform Module Libraries & Reference Architecture modules again and again without needing to change a lot of things, and Gruntwork helps with that. Multi-account AWS foundations, such as AWS Organization and Control Tower, provide us with very good support for those things.

I have seen a return on investment with Gruntwork AWS Terraform Module Libraries & Reference Architecture, as fewer employees are needed. We don't need anyone else; we can have everything as infrastructure as code. Money is saved because we don't need to make sure that things are decommissioned; we can just decommission it using the infrastructure as code. We can override what we want and don't want, and things go out.

My experience with pricing for Gruntwork AWS Terraform Module Libraries & Reference Architecture is that it's free as it's open-source. Licensing is also free to use with the open-source modules, so it's pretty much easy, and that's why we moved to it.

Before choosing Gruntwork AWS Terraform Module Libraries & Reference Architecture, I did not evaluate other options, as moving from Terraform to Terragrunt was pretty much easy, so we moved with this.

My advice for others looking into using Gruntwork AWS Terraform Module Libraries & Reference Architecture is to go ahead with it, as it's really helpful. When people first start using it, they will get a better grip on it. It's also a coding language, so it's pretty simple if you have a basic coding understanding. I would rate this product a 7 out of 10.