AWS AWS infrastructure availability solutions -Wordpress-5

4. AutoScaling, Elastic Load Balancer and Route 53

4.1 Elastic Load Balancer，创建Application Load Balancer

4.2 Route 53, and Route 53 created using Alias ​​record parsing ELB

4.3 Settings

4. Create AMI image, create a launch configuration (Lauch Configuration), create Auto Scaling group

4.4.1 public subnet & Target group

Note: Creating Auto Scaling group, using expansion strategy to adjust the capacity of this group

4.5 verification

Analog EC2 instance failure, RDS instance failure failover test to see if the application can be switched automatically to ensure that services are not interrupted.

When a termination when EC2, Auto Scaling is automatically added in the same area an AZ ec2, in a production environment, will not have some impact slightly, access will be slightly delayed. We can change some threshold Lauch Configuration. Let health check time becomes shorter.

When restarting the RDS, since the deployment of multiple instances of the available area, it is then restarted example, backup will automatically take effect in another area. In theory only affects the main database, backup database will not have any impact.

5. cleanup

Cleanup content include:

Auto Scaling Group

EC2 instances

WHICH

Snapshot

ELB

Route53

EFS

S3

RDS instances