terraform-aws-modules

terraform-aws-vpc

HCL2017–2022

terraform-aws-modules / terraform-aws-vpc

terraform-aws-vpc

Terraform module to create AWS VPC resources 🇺🇦

DevOps & Cloud

Explore on GitHub Read Hacker News discussions

5Distinct people

5Mentions

0Explicit recommenders

3.3KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Terraform module to create AWS VPC resources 🇺🇦

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

joeduffy/pulumi-architectures · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2017-09-19 18:32:21 UTC to 2022-03-17 14:14:42 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	1
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	2	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	2	2

What Hacker News says

5 sources

antonbabenko·Mar 17, 2022

I have updated the wording in README - https://github.com/terraform-aws-modules/terraform-aws-vpc#a... . The project was and will be under the same Apache 2 license.

In Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

sciurus·Mar 17, 2022

This license change appears to affect not just the EKS module, but all the modules in the terraform-aws-modules organization. For example, here is the same change in their VPC module: https://github.com/terraform-aws-modules/terraform-aws-vpc/c...

In Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

mtalantikite·Apr 14, 2020

"For comparison, this Amazon VPC example may be worth checking out" It might be better to compare how to use the module/stack: - Terraform: https://github.com/terraform-aws-modules/terraform-aws-vpc - Pulumi: https://github.com/joeduffy/pulumi-architectures/tree/master... So as a user, can I configure this Pulumi VPC stack before it's instantiated? Or do I have to use the defaults first and then use the CLI to change things? Do these CLI changes then get placed into code, or just into state? Does that mean I'm now in a situation where the code doesn't match the state? Personally I find the Terraform configuration much easier to reason about, I see exactly where resources are declared just by scanning the file. (But I've also used Terraform a lot). Edit: Ah, maybe I have to configure it via this config.py file [1]? I appreciate what Pulumi

Read the rest

is trying to accomplish, but that is certainly not a config format I'd like to be using. Maybe you could use HCL or YAML for it? ;) Edit 2: Another last thought, I think a lot of the mindset in Terraform comes from Go, where the proverb "A little copying is better than a little dependency" is pretty well adopted. Before I started writing Go as my main language I didn't appreciate that mindset, but after 5 years with Go I've found it more and more appropriate [2]. [1] https://github.com/joeduffy/pulumi-architectures/blob/master... [2] https://go-proverbs.github.io/ -- https://www.youtube.com/watch?v=PAAkCSZUG1c&t=9m28s

In Pulumi – Modern Infrastructure as Code

joeduffy·Apr 14, 2020

[Disclaimer: also member of the Pulumi team.] We've worked with a lot of end users to migrate from Terraform, and we honestly do see a lot of copy-and-paste. I agree that it's not as rampant as with YAML/JSON, however, in practice we find a lot of folks struggle to share and reuse their Terraform configs for a variety of reasons. Even though HCL2 introduced some basic "programming" constructs, it's a far cry from the expressiveness of a language like Python. We frequently see not only better reuse but significant reduction in lines of code when migrating. Being able to create a function or class to capture a frequent pattern, easily loop over some data structure (e.g., for every AZ in this region, create a subnet), or even conditionals for specialization (e.g., maybe your production environment is slightly different than development, us-e

Read the rest

ast-1 is different, etc). And linters, test tools, IDEs, etc just work. For comparison, this Amazon VPC example may be worth checking out: - Terraform: https://github.com/terraform-aws-modules/terraform-aws-vpc/b... - Pulumi (Python): https://github.com/joeduffy/pulumi-architectures/blob/master... - CloudFormation: https://github.com/aws-quickstart/quickstart-aws-vpc/blob/ma... It's common to see a 10x reduction in LOCs going from CloudFormation to Terraform and a 10x reduction further going from Terraform to Pulumi. A key importance in how Pulumi works is that everything centers around the declarative goal state. You are shown previews of this (graphically in the CLI, you can serialize that as a plan, you always have full diffs of what the tool is doing and has done. This helps to avoid some of the "danger" of having a turing-complete language. Plus, I prefer having a familiar language with familiar control constructs, rather than learning a proprietary language that the industry generally isn't supporting or aware of (schools teach Python -- they don't teach HCL). In any case, we appreciate the feedback and discussion -- all great and valid points to be thinking about -- HTH.

In Pulumi – Modern Infrastructure as Code

zimbatm·Sep 19, 2017

Interesting, they are adopting the same pattern that I had discovered for AWS modules: * all modules take in a var.name and var.tags variables. * if the resource has a unique identifier, use var.name as a prefix (eg: "${var.name}-elb") * all resources are tagged with the Name merged into var.tags This allows to (1) avoid name clashes with the name prefix and (2) make sure everything is tagged and easier to filter by on AWS, while deferring most of the tagging decision to the user. See https://github.com/terraform-aws-modules/terraform-aws-vpc/b... EDIT: there is still an issue with autoscaling groups who take a list of tags instead of a map. https://github.com/terraform-aws-modules/terraform-aws-autos...

In Terraform Module Registry