removed deprecated arguments

[vibhutigoyal]

what

• removed deprecated arguments

why

• need to remove

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 MEDIUM VPC Flow Logs is not enabled for VPC  
────────────────────────────────────────────────────────────────────────────────
  main.tf:22-41
────────────────────────────────────────────────────────────────────────────────
   22  ┌ resource "aws_vpc" "default" {
   23  │   count = var.vpc_enabled == true ? 1 : 0
   24  │ 
   25  │   cidr_block                       = var.cidr_block
   26  │   instance_tenancy                 = var.instance_tenancy
   27  │   enable_dns_hostnames             = var.enable_dns_hostnames
   28  │   enable_dns_support               = var.enable_dns_support
   29  │   ipv4_ipam_pool_id                = var.ipv4_ipam_pool_id
   30  └   ipv4_netmask_length              = var.ipv4_ipam_pool_id != "" ? var.ipv4_netmask_length : null
   ..  
────────────────────────────────────────────────────────────────────────────────
          ID aws-ec2-require-vpc-flow-logs-for-all-vpcs
      Impact Without VPC flow logs, you risk not having enough information about network traffic flow to investigate incidents or identify security issues.
  Resolution Enable flow logs for VPC

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/ec2/require-vpc-flow-logs-for-all-vpcs/
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             94.2µs
  parsing              86.049562ms
  adaptation           79.6µs
  checks               15.718493ms
  total                101.941855ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     49
  files read           3

  results
  ──────────────────────────────────────────
  passed               2
  ignored              0
  critical             0
  high                 0
  medium               1
  low                  0

  2 passed, 1 potential problem(s) detected.

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 MEDIUM VPC Flow Logs is not enabled for VPC  
────────────────────────────────────────────────────────────────────────────────
  main.tf:22-41
────────────────────────────────────────────────────────────────────────────────
   22  ┌ resource "aws_vpc" "default" {
   23  │   count = var.vpc_enabled ? 1 : 0
   24  │ 
   25  │   cidr_block                       = var.cidr_block
   26  │   instance_tenancy                 = var.instance_tenancy
   27  │   enable_dns_hostnames             = var.enable_dns_hostnames
   28  │   enable_dns_support               = var.enable_dns_support
   29  │   ipv4_ipam_pool_id                = var.ipv4_ipam_pool_id
   30  └   ipv4_netmask_length              = var.ipv4_ipam_pool_id != "" ? var.ipv4_netmask_length : null
   ..  
────────────────────────────────────────────────────────────────────────────────
          ID aws-ec2-require-vpc-flow-logs-for-all-vpcs
      Impact Without VPC flow logs, you risk not having enough information about network traffic flow to investigate incidents or identify security issues.
  Resolution Enable flow logs for VPC

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/ec2/require-vpc-flow-logs-for-all-vpcs/
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             84.901µs
  parsing              98.708486ms
  adaptation           101.601µs
  checks               9.155745ms
  total                108.050733ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     49
  files read           3

  results
  ──────────────────────────────────────────
  passed               2
  ignored              0
  critical             0
  high                 0
  medium               1
  low                  0

  2 passed, 1 potential problem(s) detected.

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 MEDIUM VPC Flow Logs is not enabled for VPC  
────────────────────────────────────────────────────────────────────────────────
  main.tf:22-41
────────────────────────────────────────────────────────────────────────────────
   22  ┌ resource "aws_vpc" "default" {
   23  │   count = var.vpc_enabled ? 1 : 0
   24  │ 
   25  │   cidr_block                       = var.cidr_block
   26  │   instance_tenancy                 = var.instance_tenancy
   27  │   enable_dns_hostnames             = var.enable_dns_hostnames
   28  │   enable_dns_support               = var.enable_dns_support
   29  │   ipv4_ipam_pool_id                = var.ipv4_ipam_pool_id
   30  └   ipv4_netmask_length              = var.ipv4_ipam_pool_id != "" ? var.ipv4_netmask_length : null
   ..  
────────────────────────────────────────────────────────────────────────────────
          ID aws-ec2-require-vpc-flow-logs-for-all-vpcs
      Impact Without VPC flow logs, you risk not having enough information about network traffic flow to investigate incidents or identify security issues.
  Resolution Enable flow logs for VPC

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/ec2/require-vpc-flow-logs-for-all-vpcs/
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             124.301µs
  parsing              45.48262ms
  adaptation           95.3µs
  checks               10.005049ms
  total                55.70727ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     48
  files read           3

  results
  ──────────────────────────────────────────
  passed               2
  ignored              0
  critical             0
  high                 0
  medium               1
  low                  0

  2 passed, 1 potential problem(s) detected.

[yadavprakash]

LGTM!