Database Infrastructure-as-Code Engineer

Manual database setup is error-prone, hard to reproduce, and impossible to audit. Infrastructure-as-code changes all of that — but writing good IaC for databases requires understanding both the tooling and the database systems being provisioned. The Database Infrastructure-as-Code Engineer assistant helps teams write, review, and improve the Terraform, Ansible, CloudFormation, and Pulumi code that provisions their database environments.

This assistant specializes in the intersection of IaC tooling and database provisioning. It helps you write Terraform modules for cloud-managed database services (RDS, Cloud SQL, Azure Database), Ansible playbooks for self-hosted database installation and configuration, CloudFormation or CDK stacks for AWS database resources, and Pulumi programs for teams working in Python, TypeScript, or Go. The focus is always on producing code that is modular, reusable, and safe to apply repeatedly across environments.

For Terraform, the assistant helps you structure database resource blocks correctly: configuring parameter groups, option groups, subnet groups, security groups, KMS encryption keys, automated backup windows, maintenance windows, and deletion protection. It helps you manage sensitive values like master passwords using Terraform's sensitive output handling and integration with AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. It also guides you through Terraform state management considerations specific to stateful database resources.

For Ansible, the assistant generates role-structured playbooks for installing and configuring PostgreSQL, MySQL, or MongoDB on Linux hosts: package installation, configuration file templating with Jinja2, service management, user and privilege setup, and idempotency design. It helps you structure roles for reuse across different environments while overriding variables per environment using group_vars and host_vars.

Ideal for DevOps and platform engineers building automated database provisioning pipelines, SRE teams enforcing infrastructure consistency through code, and development teams adopting IaC practices for the first time. Also valuable for teams auditing or refactoring existing IaC that has grown inconsistent or fragile over time.

Outputs include Terraform modules, Ansible roles, CloudFormation templates, variable definitions, and IaC structure recommendations with rationale.