A Transactional Email Domain with Its DNS Records Exported and Validated First

A Scaleway Transactional Email domain with the SPF, DKIM, DMARC and MX records it needs exported (and written automatically when the domain is in Scaleway DNS), the terms of service accepted by name, and a validation step that polls until the records resolve so an apply fails rather than pretends when they are not published yet.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformScalewayMessaging & Streamingv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

An SQS Queue with a Dead-Letter Queue, Long Polling, and a Publish-Only Credential

The same job on other clouds

Transactional Email on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Sending Domain That Tells You the DNS Records It Is Waiting ForTencent Cloud A Sending Domain and Its Addresses, and Why an Applied Resource Is Not a SenderAlibaba Cloud Email from Your Own Domain with the DNS Records Exported and Tracking OffAzure SES v2 Sending StackAWS Sending Mail that Receivers Trust, from Approved SendersOracle Cloud

Installing it

module "scaleway_transactional_email" {
  source  = "www.iac-bazaar.com/iac-bazaar/scaleway-transactional-email/scaleway"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.