Flow Logs for an Existing VPC in the Extended Format, at One Minute, All Traffic

Flow logs for an existing VPC in the extended format an investigation needs (flow direction, TCP flags, packet addresses through NAT), at one minute rather than ten, all traffic rather than rejects, to a CloudWatch log group created with retention and your KMS key, or to S3 as Hive-partitioned Parquet when a bucket is given. Partial traffic and the AWS-managed key are accepted by name.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAWSObservabilityv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Config Recorder that Is Actually Running A Dashboard that Reads One Account A Metrics Store that Can Actually Raise an Alarm CloudTrail with a Hardened Evidence Bucket CloudWatch Logs, Alarm & Dashboard Security Lake with Lifecycle Control

The same job on other clouds

Network Flow Logs on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

Flow Logs that Are On, Kept, and AnalysedAzure VCN Flow Logs per Subnet, All Traffic, with Retention Past the Default MonthOracle Cloud

Installing it

module "aws_vpc_flow_logs" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-vpc-flow-logs/aws"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.