Kaphera Cloud Terraform Modules
A collection of composable, opinionated Terraform modules that encode production-tested deployment patterns for the EDC operator family and Kaphera Cloud: the “golden paths” on top of the Terraform provider.
What it is
A collection of composable Terraform modules that encode production-ready deployment patterns for the EDC operator family and Kaphera Cloud platform. Built from scratch on top of the kaphera-cloud-terraform-provider, not wrappers around upstream modules. Each module represents an opinionated, tested pattern: a complete connector deployment, a data space participation setup, an infrastructure tier with database and secrets management. They are the “golden paths” that turn individual Terraform resources into deployable units.
What it does for the customer
Eliminates the gap between having a Terraform provider and knowing how to use it well. A systems integrator deploying their fifth client can use a connector module with a few parameters instead of assembling 15+ resources from scratch. An enterprise platform team can compose modules into their own internal deployment standard. The modules encode Kaphera’s operational experience (resource sizing, health check configuration, dependency ordering, naming conventions) so that every deployment starts from a production-tested baseline.
Who it serves
lars-hoffmann is the builder who needs repeatable, parameterised deployments across clients. The modules are the foundation of the standard delivery pattern he wants to establish at his organisation.
marco-ferretti’s engineering team uses the modules to automate client setup as part of the white-label managed connector offering.
dirk-wassermann’s platform engineers compose modules into their internal deployment standard for connector infrastructure on their private cloud.
Why this licence: Apache 2.0
Modules are adoption accelerators. They make the kaphera-cloud-terraform-provider (and by extension the operators) easier to use, driving ecosystem growth. The value they create is indirect: more teams using modules means more teams on the platform.
How it relates to other artefacts
Built entirely on the kaphera-cloud-terraform-provider: every module composes provider resources and data sources. They are the opinionated layer above the provider, which is the flexible layer above the operators. The [[kaphera-cli|kaphera CLI]] serves a similar role for interactive workflows; modules serve it for declarative, version-controlled infrastructure. Teams typically start with modules for initial deployment and use the CLI for day-two operations.
Related
- kaphera-cloud-terraform-provider: the provider these modules compose.
- kaphera-cli: interactive counterpart for day-two operations.
- lars-hoffmann: the platform engineer for whom modules are the foundation of repeatable client delivery.
- marco-ferretti: the white-label partner who automates client setup with modules.
- dirk-wassermann: the enterprise lead whose internal deployment standard composes from these modules.