alternat VS terraform-aws-vpc

This is perfect for preprod environments. I'd probably not deploy in production. There is a better nat instance setup available called alternat [1] which is a little more durable and better for production cases.

[1] https://github.com/1debit/alternat

We use https://github.com/1debit/alternat in our EKS cluster to save the AWS tax (surcharge for NAT on top of the egress fee)

Unfortunately we've been getting absolutely hammered by NAT gateway pricing, and we've had to switch over to NAT instances. We deployed (alternat)[https://github.com/1debit/alternat] for some OOTB resiliency, but I've never had to manage a group of NAT instances myself at this scale.

alterNAT is another approach that makes it even easier, and falls back to NAT GW if needed.

As for the alternatives they already exists. Feel free to create more if your like, more the merrier. https://github.com/1debit/alternat

You can go around NAT gateway costs (not completely) by using alternat: https://github.com/1debit/alternat

Welcome to hell. I default to public subnets where possible; past that I either bend the knee or use alterNAT.

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.

Let us use an example from AWS to see how we can use a publicly available module. When setting up a virtual network (or Virtual Private Cloud, VPC) in AWS there are a lot of resources you must create. One popular module is the AWS VPC module. The documentation for this module is available at registry.terraform.io/modules/terraform-aws-modules/vpc/aws. The simplest example of using this module looks like this:

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" } }

/u/akirakotkata all of the answers in this thread are correct, but nobody's empowered you to figure this out on your own in the future. In the registry link you provided, there's a link to Source Code. Follow that link and take a look at variables.tf in the repo, lines 13-17. That block is what is expected for the parameter, so you need to tweak what you're sending into what it expects.