
WordPress on AWS ECS
Terraform blueprint that deploys a robust and scalable WordPress on AWS using ECS Fargate, Aurora MySQL and WordPress container from Bitnami.
Change Log
All notable changes to this blueprint.
1.3.0 (2025-11-17)
- Switch to Amazon ECR Public gallery for container images.
- Upgrade Terraform AWS provider to v6 and update all Terraform modules for v6 compatibility.
- Add DNS
HTTPSresource record type to improve performance and security. - Add application layer (L7) DDoS protections ruleset support in the WAF configuration.
1.2.0 (2025-02-10)
- The default CPU architecture is now
ARM64, offering up to 20% savings on ECS. - Fargate CPU architecture is now configurable using the
service_task_cpu_architectureinput variable. - Added support for the Fargate Spot capacity provider; use
service_task_spot_weightto define what percentage of tasks run on Fargate Spot.
Upgrading
- Upgrading to
ARM64completes as a rolling process without downtime. To retain x86, setservice_task_cpu_architecturetoX86_64. - Enabling Fargate Spot recreates the ECS service, causing a brief service interruption.
1.1.9 (2024-08-23)
- Add support for the new Amazon Aurora SSL/TLS CA.
1.1.8 (2024-08-03)
- Updating to this version will perform rolling restart of the Aurora instances without downtime. This is due to the changes in the RDS module.
1.1.5 (2023-12-12)
- Added EFS throughput mode configuration
1.1.0 (2023-08-15)
- Added WAF protection
1.0.0 (2023-07-27)
- Initial release