WordPress AWS infrastructure — Terraform blueprint

Built for operational WordPress workloads

This catalog item packages the Terraform you need to deploy a conventional WordPress tier on AWS: users reach an ALB listener, targets are Ubuntu instances sized through Auto Scaling, and the backing store is Aurora MySQL with RDS-managed Secrets Manager passwords where configured.

The repository splits concerns into reusable modules (kms, vpc, alb, wordpress, rds, efs, elasticache, optional cloudfront, etc.) plus opinionated environments/ roots for staging and production.

What is included

Reference architecture path

Optional CloudFront → WAF → ALB → EC2 (WordPress) with Aurora MySQL
Optional EFS mount for scalable wp-content
Optional Redis for caching or sessions
Minimal example trades CloudFront for direct ALB + WAF ingress

Terraform modules and roots

Composable modules aligned to each layer (IAM, KMS, RDS, ALB, WordPress compute, networking, CDN)
examples/minimal and examples/wordpress-production
environments/staging and environments/production reference deployments

Security and secrets

SSM placeholders for WordPress salt keys — rotate post-deploy
RDS-managed master credential via Secrets Manager where configured
CloudWatch alarms and SNS notifications documented in the upstream runbook

Documentation

Main README plus architecture, decisions, and runbook documentation shipped in the upstream repository

Repository overview

Upstream layout is terraform-aws-wordpress (commercial license). Typical paths include orchestration-ready modules plus environment roots tuned for repeatable staging/production applies.

terraform-aws-wordpress/
├── modules/
│   ├── wordpress/   ├── alb/       ├── rds/
│   ├── vpc/          ├── elasticache/
│   ├── cloudfront/   └── monitoring/
├── environments/
│   ├── staging/
│   └── production/
├── examples/minimal/
├── examples/wordpress-production/
├── docs/
└── README.md

Frequently asked questions

Who is this for?

Teams that want a repeatable WordPress footprint on AWS with Terraform—not a hosted SaaS—with room to tighten security controls and tagging to fit their own standards.

Does Terraform upload my theme and media?

Provision is infra-first. Themes and uploads land on EC2 volumes or optional EFS; day-two content pipelines are yours to automate (AMI baking, Ansible, pipelines, etc.).

What happens after checkout?

You receive secure product delivery links and, when a GitHub username is provided, private repository access for the purchased product.