Quick start with WordPress on Alibaba Cloud. We use the WordPress image on Alibaba Cloud Marketplace.
Since in this tutorial, we will reply on the Terraform to provision the cloud resources. If you are the 1st time to use Terraform, please refer to https://github.com/alibabacloud-howto/terraform-templates to learn how to install and use the Terraform on different operating systems.
https://github.com/alibabacloud-howto/solution-marketplace-wordpress
- Phase 0: "ALL-IN-ONE" for entry level deployment
- Phase 1: WordPress ECS Server + Standalone RDS MySQL in Basic Edition
- Phase 2-1: SLB + WordPress ECS Servers (Auto-scaling) + Cloud Native PolarDB MySQL
- Phase 2-2: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + RDS MySQL in High Availability Edition
- Phase 2-3: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + Cloud Native PolarDB MySQL
- Pricing
- WordPress with web app server and MySQL database are all built within a single ECS instance.
- This is for entry level deployment with low cost but without high availability feature for both web app and database.
Run the terraform script to initialize the resources.
Within the terraform script, please use the right Image ID of WordPress image on the corresponding region.
After the Terraform script execution, open the following URL in a Web browser to initialize WordPress:
http://<ECS_EIP>
Note: Replace the <ECS_EIP> placeholder with the Elastic IP address of the ECS instance.
- Decouple the database from web app server.
- More stable for both web app and database but still without high availability feature for both of them.
Run the terraform script to initialize the resources.
Within the terraform script, please use the right Image ID of WordPress image on the corresponding region.
- After the Terraform script execution, logon to ECS via SSH, use the account root/N1cetest, the password has been predefined in Terraform script for this tutorial. If you changed the password, please use the correct password accordingly.
ssh root@<EIP_ECS>Edit the WordPress configuration file to set the RDS MySQL URL, database and account information.
vim /data/wwwroot/wordpress/wp-config.php
Open the following URL in a Web browser to initialize WordPress:
http://<ECS_EIP>
Note: Replace the <ECS_EIP> placeholder with the Elastic IP address of the ECS instance that you obtained previously.
- Setup SLB and auto-scaling group for multiple ECS servers with WordPress web app.
- Use cloud native database PolarDB with high availability and scalability.
Run the terraform script to initialize the resources.
Within the terraform script, please use the right Image ID of WordPress image on the corresponding region.
- After the Terraform script execution, logon to ECS via SSH, use the account root/N1cetest, the password has been predefined in Terraform script for this tutorial. If you changed the password, please use the correct password accordingly.
ssh root@<EIP_ECS>Edit the WordPress configuration file to set the PolarDB MySQL URL, database and account information.
vim /data/wwwroot/wordpress/wp-config.php
Open the following URL in a Web browser to initialize WordPress:
http://<ECS_EIP>
Note: Replace the <ECS_EIP> placeholder with the Elastic IP address of the ECS instance that you obtained previously.
After you have successfully configured and installed WordPress, you can follow the following guide for auto-scaling configurations:
Phase 2-2: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + RDS MySQL in High Availability Edition
- Setup SLB and auto-scaling group for multiple ECS servers with WordPress web app.
- Use RDS with cross availability zone feature for high availability.
- Use Redis as data cache to improve web app performance. The cross availability zone feature also ensure the high availability.
Run the terraform script to initialize the resources.
Within the terraform script, please use the right Image ID of WordPress image on the corresponding region.
- After the Terraform script execution, logon to ECS via SSH, use the account root/N1cetest, the password has been predefined in Terraform script for this tutorial. If you changed the password, please use the correct password accordingly.
ssh root@<EIP_ECS>Edit the WordPress configuration file to set the RDS MySQL URL, database and account information.
vim /data/wwwroot/wordpress/wp-config.php
Open the following URL in a Web browser to initialize WordPress:
http://<ECS_EIP>
Note: Replace the <ECS_EIP> placeholder with the Elastic IP address of the ECS instance that you obtained previously.
Run the following commands in sequence to download the Redis object cache plugin and unzip the plugin package:
wget https://downloads.wordpress.org/plugin/redis-cache.2.0.18.zip
unzip redis-cache.2.0.18.zip Run the following commands in sequence to copy the redis-cache folder to the /data/wwwroot/wordpress/wp-content/plugins/ path and configure WordPress to access ApsaraDB for Redis:
cp -rf redis-cache /data/wwwroot/wordpress/wp-content/plugins/
vim /data/wwwroot/wordpress/wp-config.phpComplete the settings as follows:
// Redis settings
define( 'WP_REDIS_HOST', '<Redis URL>' );
define( 'WP_REDIS_CLIENT', 'predis' );
define( 'WP_REDIS_PORT', '6379' );
define( 'WP_REDIS_DATABASE', '0');
define( 'WP_REDIS_PASSWORD', 'wordpress:N1cetest' );
Please MAKE SURE this Redis setting block is set at the first settings block of the wp-config.php file as shown in the image above.
Run the following command to copy the object-cache configuration file to the /data/wwwroot/wordpress/wp-content/ path:
cp /data/wwwroot/wordpress/wp-content/plugins/redis-cache/includes/object-cache.php /data/wwwroot/wordpress/wp-content/ Log on to WordPress to enable Redis object cache.
In the left-side navigation pane, click Plugins. Find the Redis Object Cache plugin and click Activate.
After the plugin is activated, click Settings.
Verify that the plugin status is Connected. Click Flush Cache to synchronize cache data to the ApsaraDB for Redis instance.
Now, your cloud native Wordpress has been setup successfully. You can visit it via SLB EIP:
http://<SLB_EIP>/After you have successfully configured and installed WordPress, you can follow the following guide for auto-scaling configurations:
Phase 2-3: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + Cloud Native PolarDB MySQL
- Setup SLB and auto-scaling group for multiple ECS servers with WordPress web app.
- Use cloud native database PolarDB with high availability and scalability.
- Use Redis as data cache to improve web app performance. The cross availability zone feature also ensure the high availability.
Run the terraform script to initialize the resources.
Within the terraform script, please use the right Image ID of WordPress image on the corresponding region.
- After the Terraform script execution, logon to ECS via SSH, use the account root/N1cetest, the password has been predefined in Terraform script for this tutorial. If you changed the password, please use the correct password accordingly.
ssh root@<EIP_ECS>Edit the WordPress configuration file to set the PolarDB MySQL URL, database and account information.
vim /data/wwwroot/wordpress/wp-config.php
Open the following URL in a Web browser to initialize WordPress:
http://<ECS_EIP>
Note: Replace the <ECS_EIP> placeholder with the Elastic IP address of the ECS instance that you obtained previously.
Please follow the this step to configure the Redis caching:
https://github.com/alibabacloud-howto/solution-marketplace-wordpress#configure-redis-caching
After you have successfully configured and installed WordPress, you can follow the following guide for auto-scaling configurations:
- We calculate the price based on the resource and service in
Singaporeregion. - If auto-scaling is configured, the extra scaled ECS instances are not counted within the total price.
- PolarDB is compute and storage decoupled, the fee of storage is not counted within the total price.
- By default, the ECS, RDS MySQL, PolarDB MySQL, Redis resource are all provisioned as "Pay As You Go" pricing mode through the Terraform provisioning script. Please go to the product web console to convert to "Subscription" pricing mode if needed.
| Cloud Service | Specification | Pay-As-You-Go Price | Subscription Price |
|---|---|---|---|
| ECS | ecs.c5.large, 40GB SSD system disk, 100GB ultra disk data disk | $0.11 USD/Hour | $55.94 USD/Month |
| WordPress Image | $0.055 USD/Hour | $40 USD/Month | |
| EIP | Pay By Bandwith 2Mbit/s | $0.28 USD/Day | |
| SLB | slb.s2.medium | $0.12 USD/Hour | |
| RDS MySQL basic | mysql.n2.small.1, 1 core 2GB general purpose, 20GB ESSD | $0.03 USD/Hour | $14.18 USD/Month |
| RDS MySQL high availability | mysql.x2.medium.2c, 2 core 4GB dedicated instance, 20GB ESSD | $0.25 USD/Hour | $119.17 USD/Month |
| PolarDB MySQL | polar.mysql.x4.medium, 2 core 8 GB dedicated instance | $0.318 USD/Hour | $152 USD/Month |
| Redis | redis.master.small.default, 1GB Master-Replica | $0.034 USD/Hour | $16.32 USD/Month |
| Solution Phase | Services | Estimated Hourly Price | Estimated Monthly Subscription Price |
|---|---|---|---|
| Phase 0: "ALL-IN-ONE" for entry level deployment | ECS, WordPress Image, EIP for ECS | $0.18 USD/Hour | $104.62 USD/Month |
| Phase 1: WordPress ECS Server + Standalone RDS MySQL in Basic Edition | ECS, WordPress Image, EIP for ECS, RDS MySQL basic | $0.21 USD/Hour | $118.80 USD/Month |
| Phase 2-1: SLB + WordPress ECS Servers (Auto-scaling) + Cloud Native PolarDB MySQL | ECS, WordPress Image, SLB, EIP for ECS, EIP for SLB, PolarDB MySQL | $0.63 USD/Hour | $351.69 USD/Month |
| Phase 2-2: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + RDS MySQL in High Availability Edition | ECS, WordPress Image, SLB, EIP for ECS, EIP for SLB, RDS MySQL high availability, Redis | $0.59 USD/Hour | $335.18 USD/Month |
| Phase 2-3: SLB + WordPress ECS Servers (Auto-scaling) + Multi-AZ Redis Cache + Cloud Native PolarDB MySQL | ECS, WordPress Image, SLB, EIP for ECS, EIP for SLB, PolarDB MySQL, Redis | $0.66 USD/Hour | $368.01 USD/Month |