Back to features

Terraform provider

Treat monitoring like the rest of your infrastructure. The official terraform-provider-xpiry will let you declare domains, alert rules, and notifications as code.

Planned resources

• › xpiry_domain — name, port, ssl_enabled, domain_expiry_enabled, alert thresholds, paused state.
• › xpiry_alert_rule — channel (email, slack, teams, discord, pagerduty, webhook), config, enabled state.

Planned data sources

• › xpiry_account — plan, limits, current usage.
• › xpiry_domain — read-only access to a single domain's monitored state, including the latest cert summary, security grade, and self-signed flag.

Example (preview syntax)

terraform {
  required_providers {
    xpiry = {
      source = "reedster-llc/xpiry"
    }
  }
}

provider "xpiry" {
  api_key = var.xpiry_api_key
}

resource "xpiry_domain" "production" {
  name = "example.com"
  port = 443

  ssl_enabled            = true
  domain_expiry_enabled  = true
  alert_thresholds       = [30, 14, 7, 1]
}

resource "xpiry_alert_rule" "ops_slack" {
  name        = "#ops-alerts"
  channel     = "slack"
  webhook_url = var.slack_webhook
  enabled     = true
}

Why use it

• › Bulk onboarding. Agencies adding 50+ domains for a new client can do it in one apply.
• › Reproducible config. Monitoring lives in the same repo as the rest of your infra, reviewed in PRs, rolled back via git.
• › Drift detection. A teammate adding or removing a domain in the dashboard shows up as a Terraform diff next time you plan.

Will publish to the Terraform Registry. Email [email protected] for early access.