The Provider Side of PrivateLink, Not Open to Everyone
An endpoint service, who may attach and the private DNS it answers on. A wildcard principal offers the service to every AWS account, so the module refuses it unless said out loud - and warns that zone names differ per account.
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-12 · how we verify
Use it from the registry
terraform · opentofumodule "privatelink_service" {
source = "www.iac-bazaar.com/iac-bazaar/aws-privatelink-service/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-privatelink-service?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [The Provider Side of PrivateLink, Not Open to Everyone](https://www.iac-bazaar.com/catalog/aws-privatelink-service?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "privatelink_service" {
source = "www.iac-bazaar.com/iac-bazaar/aws-privatelink-service/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-privatelink-service
The provider side of PrivateLink: an endpoint service in front of a load
balancer, who may connect to it, and the private DNS name it answers on. Works
with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
allowed_principals = ["*"] publishes the service to every AWS account. Not
to the internet - a consumer still creates an endpoint - but to anyone who knows
the service name, which is discoverable. Paired with acceptance_required = false it is a service anything can attach to without a request you ever see.
The module refuses the wildcard unless allow_any_principal says it was meant,
and refuses the wildcard-plus-no-acceptance combination outright.
Availability zone names are per account. Your us-east-1a and a consumer's
us-east-1a are usually different physical zones - AWS shuffles the mapping
deliberately. A consumer creating an endpoint in what they call us-east-1a can
find the service unavailable there while everything looks healthy from your
side. The availability_zones output is labelled with that warning rather than
offered as something to pass on.
Related, and the other half of the same problem: the NLB needs a subnet in every zone a consumer connects from, with cross-zone load balancing on unless you are certain there are healthy targets in each.
Private DNS needs a TXT record first. Claiming api.example.com means
proving you own the domain. Verification started before the record is published
fails, and the service then sits unverified while consumers quietly keep using
the AWS-generated name. private_dns_name_configuration is an output for
exactly that reason - it is the record to publish.
Two outputs exist to be asserted on in a policy test rather than read by a
person: open_to_every_account and connections_are_reviewed.
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-lattice
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.
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.