A Service Network where the Network Is Not the Permission
auth_type defaults to NONE, so any client in any associated VPC can call any service with no identity and no policy - and associating one more VPC silently grants everything in it. Defaults to AWS_IAM and requires per-VPC security groups.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-13 · how we verify
Use it from the registry
terraform · opentofumodule "vpc_lattice" {
source = "www.iac-bazaar.com/iac-bazaar/aws-vpc-lattice/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 · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads static-verified because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-vpc-lattice?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [A Service Network where the Network Is Not the Permission](https://www.iac-bazaar.com/catalog/aws-vpc-lattice?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "vpc_lattice" {
source = "www.iac-bazaar.com/iac-bazaar/aws-vpc-lattice/aws"
version = "1.0.0"
}
```Preview:
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-lattice
A VPC Lattice service network, the services in it, the VPCs that reach it, and
the access logs that say who called what. Works with Terraform and OpenTofu
(>= 1.6), AWS provider >= 6.0, < 7.0.
auth_type defaults to NONE, and NONE means the network is the
permission. Any client in any associated VPC can call any service in the
network - no identity, no policy, no record. That is the appeal of Lattice and
it is also the whole risk: associating one more VPC silently grants every
workload in it access to every service already there. This module defaults to
AWS_IAM and refuses NONE unless you say you meant it.
Associating a VPC is the grant, which is why security_group_ids is
required on each association rather than optional - it is the only per-VPC
narrowing available.
Access logs are the only record of who called what. Lattice sits between services precisely so the callers need not know about each other, which also means nothing else in the path can tell you. They are off by default in AWS.
One nuance the module is built around: a service's own auth_type is
independent of the network's. AWS_IAM with an auth_policy on the service is
how one service restricts callers the network has already admitted, and
services_without_auth_policy lists the ones relying entirely on the network's.
That is a legitimate design - it is just worth knowing which they are.
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
aws-vpc-peering
A VPC peering between two VPCs in one account and region, accepted in the same apply, with DNS resolution across it and routes written in every listed route table on both sides for every CIDR of the other. A default route through a peering is refused (CKV2_AWS_44). Peering is not transitive; past a handful of VPCs the transit gateway is the product.
aws-client-vpn
Remote-access VPN endpoint with certificate or SAML authentication, split tunnelling, per-group authorization rules and connection logging. There is no allow-all shortcut: an endpoint with no rule reaches nothing.
aws-cloud-map
Private DNS, public DNS or API-only namespaces and the services registered in them. Documents the health-check trap: a private namespace gets a custom check that something else must update, and one nobody updates reports healthy forever.
aws-cloud-wan
A global network whose segments, routing and attachment placement live in one policy document rather than per-region route tables. The policy VERSION is executed as a second step, so a change cannot report success while the network still runs the previous one.
aws-direct-connect
Gateway, connections, virtual interfaces and associations. A private circuit is a private path, not a private conversation: traffic crosses it in clear text unless MACsec is on, and should_encrypt quietly falls back to clear text.
aws-ipam
Amazon VPC IPAM with a top-level pool, a pool per region with netmask bounds and required tags, and optional sharing through AWS RAM. IPAM forces nothing on its own - a VPC can still take a hand-typed CIDR - so the module outputs the SCP AWS documents for requiring a pool. The provider defaults to the Advanced tier, billed per active IP, so the tier has no default here.