winget-cli VS terraform-aws-vpc

GitHub

You're correct here, and that's exactly the reason Winget is a package manager, as dependency management is part of teh stable release since version 1.6.3133:

It's also on the official microsoft package manager (winget).

https://github.com/microsoft/winget-cli

Winget install

GitHub - microsoft/winget-cli: Windows Package Manager CLI (aka winget)

Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle - https://github.com/microsoft/winget-cli/releases

ECR VPC ECS

Now let us move on to the important part of the tutorial. Creating an EKS cluster in AWS is not as straightforward as in other cloud platforms. You need to also create a lot more resources for everything to work correctly without surprises. You will be using a bunch of Terraform providers to help with this, and you will also use some prebuilt Terraform modules like AWS VPC Terraform module and Amazon EKS Blueprints for Terraform to reduce the amount of boilerplate you need to write.

The infrastructure is created using terraform, and can be found in this git repository. The project uses community maintained AWS Terraform modules, which simplify this process. The code examples that follow in the post are using the vpc-endpoints module to create the Gateway and interface endpoints.

locals { region = data.aws_region.current.name } module "vpc" { source = "git::https://github.com/terraform-aws-modules/terraform-aws-vpc.git?ref=v3.16.0" name = var.vpc_name cidr = var.vpc_cidr azs = ["${local.region}a", "${local.region}b"] public_subnets = cidrsubnets(var.vpc_cidr, 1, 1) enable_dns_hostnames = true enable_dns_support = true map_public_ip_on_launch = true tags = { Name = var.vpc_name } public_subnet_tags = { Name = "public subnet" "kubernetes.io/role/elb" = "1" "kubernetes.io/cluster/${var.cluster_name}" = "shared" } }

If you take the vpc module of terraform-aws-modules as an example, you see that there's a lot more to it than solely the vpc itself (https://github.com/terraform-aws-modules/terraform-aws-vpc/blob/master/main.tf). The same for your other example the ec2 instance (https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/blob/master/main.tf).

This is a template to create a module. It has a lot of stuff built in like testing tools. Those are all covered in the README. The module itself is just a simple "Hello World" so it doesn't really use very complicated Terraform logic. It's not a great example for advanced Terraform logic but this is https://github.com/terraform-aws-modules/terraform-aws-vpc/blob/master/main.tf.

You can see the same structure in the official Consul module provided by Hashicorp as well as in the AWS community modules, like here in the VPC module.

yaml terragrunt_modules_settings: regional: vpc_eks: networking: repo: "git::https://github.com/terraform-aws-modules/terraform-aws-vpc.git" tf_variables: enable_dns_hostnames: true enable_ipv6: false enable_nat_gateway: false single_nat_gateway: false