Design DevOps of Wordpress Cluster in AWS

***************************************************************************************** PROJECT 1 - Local Wordpress Stack ***************************************************************************************** Set-up and configure a CI/CD DevOps infrastructure optimized for an advanced cluster of Wordpress websites using Amazon Web Services. CI/CD deliverables: 1) AWS CloudFormation Templates to create necessary secure and scalable AWS OpsWorks stacks with Ubuntu 14.04 & Chef 12 2) AWS OpsWorks with custom Chef 12 recipes to provision secure development, staging environments and scalable multi-zone production environments 3) AWS EC2 Custom AMI with a Ubuntu 14.04 base for stable high performance PHP Websites including HTTPS/2 support using NGINX 4) Demo via Skype: simulation of deployment of a new Stack (US) and layer 1 of a single application local website (/us) using an AWS account and IAM user provided by us. 5) Demo via Skype: simulation of deployment of an update of Stack (US) and layer 1 from development, staging and production to 3 applications (/us /ca-en /ca-fr) 6) Demo via Skype: simulation of deployment failure and a roll-back of Stack (US) and layer 1 from staging and production to 1 application (/us) including PHP and DB changes 7) All DevOps code delivered documented in US English This is the first step of many projects. Delivery date: December 30, 2015. Background ---------------- Local WordPress Websites Stack ---------------------------------------------- Application #2..{n} - Local WordPress Websites (public access) * Each OpsWorks stack can contain one or several local Wordpress Websites sharing the same EC2 & RDS instances & S3 buckets * Each local WordPress website runs as an application layer for each country/language to create and upload local content * The local Wordpress website will use CloudFlare DNS & CDN * These local WordPress websites all run using the same domain name using a wildcard TLS/SSL with each site run in a different directory (Ex. [login to view URL], [login to view URL] and [login to view URL]) * Each WordPress website would use a private Git repo for both infrastructure code and application code * Each WordPress website infrastructure can be easily be configured to be deployed to a current either share EC2 & RDS instances or use a separate EC2 and/or RDS instance * Production: 1 ELB instance + 1..{n} EC2 instances + 1..{n} RDS instances + 1..{n} ElastiCache instances + 1..{n} S3 buckets (one bucket per site) * Scaling: Up and Out starting with a single [login to view URL] instance shared by one or more applications (availability zones configurable) * Security: High, VPN and other recommended security measures EXAMPLES of local Websites Stacks in production: Stack 1 using EU (Ireland) Layer 1 - Northern Europe (5 applications) - shared EC2, RDS & S3 buckets etc. Stack 2 using EU (Frankfurt) Layer 2 - Eastern Europe 1 (3 applications) - shared EC2, RDS & S3 buckets Layer 3 - Eastern Europe 2 (10 applications) - shared EC2, RDS & S3 buckets Layer 4 - Western Europe 1 (2 applications) - shared EC2, RDS & S3 buckets etc. Stack 3 using US (N. Virginia) Layer 1 - North America (3 applications) - shared EC2, RDS & S3 buckets etc. *****************************************************************************************