AWSLive-testedreceipt

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.

terraformAWSaws

Compare Network Flow Logs across clouds →

aws-vpc-flow-logsvizier v1.2.0

Verification

Live-tested

Really deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan test superseded by live test

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live-tested on registry.opentofu.org/hashicorp/aws - applied, verified, destroyed

Last verified 2026-10-31 · tofu 1.12.1 · how we verify

Use it from the registry

terraform · opentofu
module "vpc_flow_logs" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-vpc-flow-logs/aws"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/aws-vpc-flow-logs/badge)](https://www.iac-bazaar.com/catalog/aws-vpc-flow-logs?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, live-tested on IaC Bazaar: [Flow Logs for an Existing VPC in the Extended Format, at One Minute, All Traffic](https://www.iac-bazaar.com/catalog/aws-vpc-flow-logs?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

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

Preview:IaC Bazaar: live-tested

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

aws-vpc-flow-logs

Flow logs for an existing VPC in the extended format, at one-minute aggregation, to CloudWatch Logs or to S3 as Parquet. Works with Terraform and OpenTofu (>= 1.6), aws provider >= 6.0, < 7.0.

The default format is missing the fields that matter; flow direction, TCP flags and packet addresses are in the format here.

Ten-minute aggregation hides short flows; one minute here.

Accept and reject, not just reject; ALL here, partial by name.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage

Related modules

Static validatedLive test pending

aws-config

Recorder, delivery channel, service role and managed rules. Starting the recorder is a separate resource people leave out, so a stopped recorder looks identical to a running one until an investigation finds an empty timeline.

View module
Static validatedLive test pending

aws-grafana

account_access_type ORGANIZATION lets a workspace query observability data in accounts whose owners never approved it, and SERVICE_MANAGED means AWS wrote those data-source policies. Current account, a role you wrote, and an endpoint narrowed to a prefix list rather than the whole internet.

View module
Static validatedLive test pending

aws-prometheus

Alerting needs BOTH an alert manager definition and a rule group namespace; with either missing the workspace stores metrics and raises nothing while every dashboard reports it healthy. Without logging_configuration a throttled remote_write likewise produces no metrics, no error and no alert.

View module
Static validatedLive test pending

aws-cloudtrail-lake

A CloudTrail Lake event data store with the retention decided rather than inherited. The aws provider defaults retention to 2555 days; on the default pricing option AWS includes 366 and bills the rest, so the provider default quietly buys 2,189 days of storage. This module defaults to 366, prints the billed days, and keeps termination protection on.

View module
Static validatedLive test pending

aws-cloudtrail

Multi-region trail with log file validation always on, a bucket that blocks public access, versions, encrypts and denies non-TLS, a policy pinned to this trail, optional CloudWatch delivery and opt-in data events.

View module
Live-tested

aws-cloudwatch

A self-contained CloudWatch observability bundle - an encrypted log group with retention, a metric alarm, and a dashboard - that stands up from just a name and points at any real metric.

View module