commitdev / zero-aws-eks-stack

zero module for a basic AWS kubernetes stack on EKS

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Investigate using NAT instances instead of NAT gateways to save cost

bmonkman opened this issue · comments

It could be cheaper to use NAT instances if we use small instance classes, though we would potentially introduce issues for people who need a lot of outbound traffic from their cluster. Could be something we prompt for during setup - let them choose..

Specs:

  • NAT Instance suggested for Staging environment only, while keep NAT gateway for Production
  • One NAT instance per AZ (optional)

Spec:

  • Enable S3 VPC endpoint to save cost for S3 access

Put NAT instance as part of VPC module, with a controller enable_nat_gateway. When it is set as false, create NAT instance instead of NAT gateway.

Allow user to define own NAT instance type (default: t3.nano)