test(vpc): Disable NAT gateway to test pipeline

[chris3ware]

No description provided.

[infracost]

💰 Infracost report

This pull request is aligned with your company's FinOps policies and the Well-Architected Framework.

Monthly estimate decreased by $86 📉

Changed project	Baseline cost	Usage cost*	Total change	New monthly cost
tf-dev-vpc	-$75	-$11	-$86 (-86%)	$14

*Usage costs were estimated using Infracost Cloud settings, see docs for other options.

Estimate details

Key: * usage cost, ~ changed, + added, - removed

──────────────────────────────────
Project: tf-dev-vpc
Module path: tf/dev/vpc

- module.vpc.aws_nat_gateway.this[0]
  -$29

    - NAT gateway
      -$25

    - Data processed
      -$4, -111 GB*

- module.vpc.aws_nat_gateway.this[1]
  -$29

    - NAT gateway
      -$25

    - Data processed
      -$4, -111 GB*

- module.vpc.aws_nat_gateway.this[2]
  -$29

    - NAT gateway
      -$25

    - Data processed
      -$4, -111 GB*

Monthly cost change for tf-dev-vpc (Module path: tf/dev/vpc)
Amount:  -$86 ($100 → $14)
Percent: -86%

──────────────────────────────────
Key: * usage cost, ~ changed, + added, - removed

*Usage costs were estimated using Infracost Cloud settings, see docs for other options.

161 cloud resources were detected:
∙ 23 were estimated
∙ 138 were free

---

There are also 37 pre-existing issues in the main branch. Fix some to climb your org’s leaderboard 🥇

_{This comment will be updated when code changes.}

[chris3ware]

Commit 1b1d069 which triggered tofu-ci run 10923199678 proved that TFLint deep checking works and the pipeline will fail.

[github-actions]

apply -chdir=tf/dev/vpc -lock=true tfplan

Outline of changes.

+ aws_instance.a4l_bastion will be created
+ aws_instance.a4l_internal will be created
+ aws_key_pair.a4l will be created
+ aws_security_group.bastion will be created
+ aws_security_group.internal will be created
+ aws_security_group_rule.bastion_egress["10.16.160.0/20"] will be created
+ aws_security_group_rule.bastion_egress["10.16.32.0/20"] will be created
+ aws_security_group_rule.bastion_egress["10.16.96.0/20"] will be created
+ aws_security_group_rule.bastion_ingress["192.0.2.1/32"] will be created
+ aws_security_group_rule.internal_egress will be created
+ aws_security_group_rule.internal_ingress will be created
+ module.vpc.aws_db_subnet_group.database[0] will be created
+ module.vpc.aws_default_network_acl.this[0] will be created
+ module.vpc.aws_default_route_table.default[0] will be created
+ module.vpc.aws_default_security_group.this[0] will be created
+ module.vpc.aws_internet_gateway.this[0] will be created
+ module.vpc.aws_route.public_internet_gateway[0] will be created
+ module.vpc.aws_route.public_internet_gateway_ipv6[0] will be created
+ module.vpc.aws_route_table.private[0] will be created
+ module.vpc.aws_route_table.private[1] will be created
+ module.vpc.aws_route_table.private[2] will be created
+ module.vpc.aws_route_table.public[0] will be created
+ module.vpc.aws_route_table_association.database[0] will be created
+ module.vpc.aws_route_table_association.database[1] will be created
+ module.vpc.aws_route_table_association.database[2] will be created
+ module.vpc.aws_route_table_association.private[0] will be created
+ module.vpc.aws_route_table_association.private[1] will be created
+ module.vpc.aws_route_table_association.private[2] will be created
+ module.vpc.aws_route_table_association.public[0] will be created
+ module.vpc.aws_route_table_association.public[1] will be created
+ module.vpc.aws_route_table_association.public[2] will be created
+ module.vpc.aws_subnet.database[0] will be created
+ module.vpc.aws_subnet.database[1] will be created
+ module.vpc.aws_subnet.database[2] will be created
+ module.vpc.aws_subnet.private[0] will be created
+ module.vpc.aws_subnet.private[1] will be created
+ module.vpc.aws_subnet.private[2] will be created
+ module.vpc.aws_subnet.public[0] will be created
+ module.vpc.aws_subnet.public[1] will be created
+ module.vpc.aws_subnet.public[2] will be created
+ module.vpc.aws_vpc.this[0] will be created

Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: cd84c7df-ef4c-41e8-bbe2-c7d9ca5fdfa8, api error InvalidAMIID.Malformed: Invalid id: "ami-033b95fb8079dc48" (expecting "ami-...")

OpenTofu CI by @chris3ware via push at 2024-09-18T14:41:32+01:00.

Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: cd84c7df-ef4c-41e8-bbe2-c7d9ca5fdfa8, api error InvalidAMIID.Malformed: Invalid id: "ami-033b95fb8079dc48" (expecting "ami-...")

  with aws_instance.a4l_bastion,
  on main.tf line 134, in resource "aws_instance" "a4l_bastion":
 134: resource "aws_instance" "a4l_bastion" {

::error::OpenTofu exited with code 1.

[3ware-release]

This PR is included in version 1.5.3