Verification
Live-testedReally 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 · opentofumodule "cloud_map" {
source = "www.iac-bazaar.com/iac-bazaar/aws-cloud-map/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 live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-cloud-map?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud Map Service Registry](https://www.iac-bazaar.com/catalog/aws-cloud-map?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_map" {
source = "www.iac-bazaar.com/iac-bazaar/aws-cloud-map/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-cloud-map
Cloud Map service registry: private DNS, public DNS or API-only namespaces, and
the services registered in them. Works with Terraform and OpenTofu
(>= 1.6), AWS provider >= 6.0, < 7.0.
The distinction worth understanding before you use it:
- A public DNS namespace can carry a real Route 53 health check that probes the endpoint. It bills per check per month
- A private DNS namespace cannot. It gets a custom health check, which is a flag something else has to set - an ECS task, a Lambda, your own agent
- A service with a custom check and nothing updating it stays healthy
forever, including after the thing behind it is gone. That is the failure
this module documents at the top of
main.tf, because it looks like monitoring and is not
A private namespace is validated to require a vpc_id: it resolves inside that
VPC and nowhere else.
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-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.