A Metrics Store that Can Actually Raise an Alarm
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.
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 "prometheus" {
source = "www.iac-bazaar.com/iac-bazaar/aws-prometheus/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-prometheus?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, static-verified on IaC Bazaar: [A Metrics Store that Can Actually Raise an Alarm](https://www.iac-bazaar.com/catalog/aws-prometheus?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "prometheus" {
source = "www.iac-bazaar.com/iac-bazaar/aws-prometheus/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-prometheus
An Amazon Managed Service for Prometheus workspace that can actually raise an
alarm, and that tells you when it stops receiving metrics. Works with
Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
A workspace with no alert manager definition never alerts. AMP stores
metrics and answers queries; alerting is a separate thing you have to define,
and it takes two pieces - an alert manager definition for routing, and at
least one rule group namespace for the rules that fire. With either one missing,
the workspace stores metrics and raises nothing, while every dashboard reports
it as healthy. A precondition refuses that combination unless
accept_no_alerting states that this is a metrics store only, and
alerting_configured is an output that is true only when both exist.
Without logging_configuration, a failing remote_write looks exactly like a
healthy one. Ingestion and rule-evaluation errors go to CloudWatch Logs and
nowhere else, so a misconfigured or throttled writer produces no metrics, no
error and nothing to notice. That is the worst failure mode a monitoring system
has, because the absence of alerts reads as good news.
kms_key_arn defaults to an AWS-owned key at AWS. Metrics carry hostnames,
request paths and customer identifiers far more often than people expect, so the
module takes yours.
remote_write_url is an output because the workspace endpoint is not the
ingestion URL - the path has to be appended, and getting that wrong is a
silent failure of exactly the kind above.
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-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.
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.
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.
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.
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.
aws-vpc-flow-logs
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.