If you do not have the technical skills to build and manage a website in-house but do have a content management team, you can build simple websites. If you have high requirements such as customization, availability, and scalability for your website, you can use a Resource Orchestration Service (ROS) template to install WordPress and phpMyAdmin.
Background information
WordPress is a blog platform that is developed in the PHP programming language and uses a MySQL database. phpMyAdmin is a software tool that is written in PHP and is developed for the administration of MySQL databases in a web browser. phpMyAdmin allows users to manage MySQL databases by using a web interface.
This topic describes how to install WordPress and phpMyAdmin. This topic also describes how to create a stack that contains resources such as virtual private clouds (VPCs), Server Load Balancer (SLB) instances, Auto Scaling resources, Elastic Compute Service (ECS) instances, and ApsaraDB RDS instances. In this topic, the Create a Scalable WordPress Cluster Based on Resources Such as ApsaraDB RDS sample template is used. ROS automatically creates and configures instances based on your business requirements. No manual operation is required.
Step 1: Create a stack
Log on to the ROS console.
In the left-side navigation pane, choose .
In the top navigation bar, select the region of the stack from the region drop-down list. In this example, China (Hangzhou) is selected.
Find the Create a Scalable WordPress Cluster Based on Resources Such as ApsaraDB RDS template.
Click Create Stack.
In the Configure Template Parameters step, configure Stack Name and the following parameters.
Parameter
Description
Example
Bucket Name
The name of the Object Storage Service (OSS) bucket. The name must be unique within an Alibaba Cloud account in a region.
application-wordpress-oss
Bucket Mount Point
The mount path of the OSS bucket.
/ossbucket
Zone ID
The zone ID of the vSwitch.
Qingdao Zone C
Instance Type
The instance type of the ECS instance.
Select a valid instance type. For more information, see Overview of instance families.
ecs.g6.large
Image ID
The image ID of the ECS instance.
For more information, see Image overview.
centos_7_04_64_20G_alibase_201701015.vhd
Disk Category
The data disk category of the ECS instance. Valid values:
cloud_efficiency: ultra disk
cloud_ssd: standard SSD
cloud_essd: Enhanced SSD (ESSD)
cloud: basic disk
ephemeral_ssd: local SSD
For more information, see Disks.
cloud_efficiency
Data Disk Size
The data disk size of the ECS instance.
Valid values: 20 to 32768.
Unit: GB.
40
Data Disk Mount Point
The data disk mount target of the ECS instance.
/data
Instance Password
The password that you use to log on to the ECS instance.
Test_12****
Specifications
The specifications of the SLB instance.
Select a valid instance specification. For more information, see Instance specifications.
slb.s1.small
Instance Type
The instance type of the ApsaraDB RDS instance.
Select a valid instance type. For more information, see Primary ApsaraDB RDS instance types.
rds.mysql.s1.small
Engine
The type and version number of the database engine.
MySQL-5.6
Network Type
The network type of the ApsaraDB RDS instance. Valid values:
Internet:
Intranet
Intranet
Instance Storage
The storage space of the ApsaraDB RDS instance.
Valid values: 5 to 1000. The value must be in increments of 5.
Unit: GB.
10
Database Name
The name of the ApsaraDB RDS database.
wordpress
User Name
The username that is used to connect to the ApsaraDB RDS database.
wpuser
User Password
The password that is used to connect to the ApsaraDB RDS database.
Test_13****
Total Data Disk
The total number of data disks that are attached to the ECS instance.
1
Click Create.
On the Stack Information tab, view the status of the stack. After the stack is created, click the Outputs tab to query the information about PhpAdminUrl.
Access PhpAdminUrl and log on to the PHP management console.
Step 2: View resources
In the left-side navigation pane, click Stacks.
On the Stacks page, click the stack that you created.
Click the Resources tab to view the information about resources in the stack.
The following table describes the resources in this example.
Resource
Quantity
Description
Specifications
ALIYUN::ECS::Instance
1
Creates an ECS instance to install WordPress.
Quantity: 1
Instance Type: ecs.g6.large
System Disk Category: cloud_efficiency
System Disk Size: 40 GB
Allocate Public IP Addresses: Yes
ALIYUN::ECS::VPC
1
Creates a VPC to enhance network security.
None.
ALIYUN::ECS::VSwitch
1
Creates a vSwitch in the VPC to manage instances within a zone.
None.
ALIYUN::RDS::DBInstance
1
Creates an ApsaraDB RDS database to store WordPress data.
Instance Storage: 5 GB
Instance Type: rds.mysql.s1.small
ALIYUN::OSS::Bucket
1
Creates an OSS bucket to store service data of phpMyAdmin.
None.
ALIYUN::VPC::EIP
2
Creates an EIP to associate with an ECS instance. This way, the instance can be accessed over the Internet.
None.
ALIYUN::ESS::ScalingGroup
1
Creates a scaling group to install multiple WordPress and phpMyAdmin services. Scaling groups scale computing resources based on the scaling rules that you configure to meet your business requirements.
None.
ALIYUN::VPC::NatGateway
1
Creates a NAT gateway. A NAT gateway is an enterprise-grade Internet gateway that controls the traffic flowing to and from a VPC. NAT Gateway provides SNAT and DNAT features, a maximum forwarding capacity of 10 Gbit/s, and cross-zone disaster recovery.
None.
ALIYUN::SLB::LoadBalancer
1
Creates an SLB instance to distribute traffic to multiple ECS instances. SLB distributes network traffic to backend servers to improve the responsiveness and availability of your applications. You can use SLB to prevent service interruptions caused by single points of failure (SPOFs) and to improve the availability of applications.
Specifications: slb.s1.small (free)
Network Type: VPC
Note For more information about the resource charges, see the pricing schedule on the official website or the product pricing documentation.