{"componentChunkName":"component---src-templates-blog-js","path":"/ctf/aws-formation/tp5-auto-scaling-group","result":{"data":{"markdownRemark":{"html":"

TP5-ASG

\n

1. Autoscaling Theory

\n

Definition

\n

https://docs.aws.amazon.com/autoscaling/ec2/userguide/AutoScalingGroup.html

\n

An Auto Scaling group :

\n\n

spot vs on-demand instances

\n

An Auto Scaling group can launch On-Demand Instances, Spot Instances, or both.

\n

Spot Instances = Amazon EC2 capacity at steep discounts relative to On-Demand prices.

\n

key differences :

\n\n

3 components

\n

\"asg1\"

\n
    \n
  1. \n

    Group

    \n\n
    2. \n
  2. \n

    Configuration Templates

    \n\n
    3. \n
  3. \n

    Scalling option

    \n\n
    4. \n
\n

launch configuration

\n

We recommend that you use launch templates instead of launch configurations to make sure that you can use the latest features of Amazon EC2.

\n

https://docs.aws.amazon.com/autoscaling/ec2/userguide/LaunchConfiguration.html

\n

A launch configuration is an instance configuration template that an Auto Scaling group uses to launch EC2 instances.

\n

When launch configuration creation, you specify information for the instances, including :

\n\n

You can specify your launch configuration with multiple Auto Scaling groups.

\n\n

When Auto Scaling group creation :

\n\n

2. Autoscaling Groups Lab

\n

ASG : Auto Scaling groups

\n

Creating an Auto Scaling Group Using an EC2 Instance

\n

https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-from-instance.html

\n

When you create an Auto Scaling group, you must specify the necessary information to configure :

\n\n

To configure Amazon EC2 instances, you can specify :

\n\n

When you create an Auto Scaling group using an EC2 instance, Amazon EC2 Auto Scaling creates a launch configuration for you and associates it with the Auto Scaling group.

\n

This launch configuration :

\n\n

Manual Scaling for Amazon EC2 Auto Scaling

\n

https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-manual-scaling.html

\n

At any time, you can change the size of an existing Auto Scaling group manually.\nYou can either :

\n\n

Manually scaling your group can be useful when :

\n\n

3. HA Architecture

\n

HA : High Availability

\n

You should always plan for failure

\n

\"asg-example\"

\n

ASG : Auto Scalling group\nEach SN are in a different AZ

\n

What is the ideal architecture for this environment, if we need a minimum of 6 instances and mustly available ?

\n\n

synthesis

\n\n

4. Building a Fault Tolerant WP - HA Word Press Site

\n

\"asg-network-diagram\"

\n

Steps :

\n
    \n
  1. S3 bucket
    2. \n
  2. CloudFront
    3. \n
  3. VPC -> create a WEBDMZ security group (which allow mysql port)
    4. \n
  4. RDS database with multi-az deployment ; no public accessible; define initial database-name
    5. \n
  5. IAM (Identity Access Managment) -> create a new role
    6. \n
  6. Create an EC2 instance
    7. \n
\n

At the final check the

\n\n

5. Building a Fault Tolerant WP - Setting Up EC2

\n

Steps :

\n
    \n
  1. configure the EC2 instance
    2. \n
  2. install on the EC2 WordPress
    3. \n
  3. create a post
    4. \n
  4. add to this post an image
    5. \n
  5. add a reduncancy by packing up this post to another S3 and checking the resilience between S3
    6. \n
  6. \n

    rewrite url access

    \n
      \n
    1. edit the .htaccess file (add url rewrite rule out the cloud front)
      2. \n
    2. edit the httpd.conf file (allow the new url rewrite) (you can make a backup config of the folder)
      3. \n
    \n
    7. \n
  7. restart the server to force the change(server httpd.service)
    8. \n
  8. make the bucket public and edit the public access setting to allow all input traffic
    9. \n
  9. check in chrome web explorer that the url rewrite has been well done
    10. \n
  10. create a LoadBalancer
    11. \n
  11. put the EC2 behind a LoadBalancer
    12. \n
  12. Set up Route53
    13. \n
  13. (optional) you can create a record set to save the dns domain to have a simpler url
    14. \n
\n

6. Building a Fault Tolerant WP - Adding Resilience And Autoscaling

\n

\"asg

\n

We have 2 isntances :

\n
    \n
  1. for Reading Note
    2. \n
  2. for Writting Note
    3. \n
\n

Steps :

\n
    \n
  1. \n

    edit the etc/crontab file (automating windows tasks) :

    \n
      \n
    1. Scan EC2 and copy to S3 every changes (sync to S3 with a perfect copy -> sync --delete EC2from s3to)
      2. \n
    2. send the image to the cloundfront ass well (sync to S3 with a perfect copy -> sync --delete EC2from s3to)
      3. \n
    3. trigger the update task of crontab : restart cron.service
      4. \n
    \n
    2. \n
  2. \n

    Create an Autoscaling group

    \n
      \n
    1. Create a launch configuration with IAM role of S3 access
      2. \n
    2. Create the Autoscaling group with IAM S3 access
      3. \n
    3. Edit the target group from the Autoscaling group
      4. \n
    \n
    3. \n
  3. \n

    edit the etc/crontab file (automating windows tasks) :\n1. Scan S3 and load every changes (sync to EC2 with a perfect copy -> sync --load s3from EC2to)

    \n
      \n
    1. trigger the update task of crontab : restart cron.service
      2. \n
    \n
    4. \n
\n

7. Building a Fault Tolerant WP - Cleaning Up

\n

By doing a reboot you can force a failover from one AZ to another AZ

\n

Steps

\n
    \n
  1. Reboot
    2. \n
  2. Delete RDS database,
    3. \n
  3. Delete Autoscaling which trigger EC2 Instance deleting (except the reading Note)
    4. \n
  4. Delete your target group
    5. \n
  5. Delete Application Load Balancer (which you relied to your target group)
    6. \n
  6. Delete the EC2 instance (the Writting note)
    7. \n
  7. Delete the cloudfront distribution
    8. \n
","frontmatter":{"date":"July 31, 2020","path":"ctf/aws-formation/tp5-auto-scaling-group","title":"TP4-ASG","tags":["cloud","ec2","aws"],"categorie":"ctf","thumbnail":"/assets/alex-machado-80sv993luki-unsplash.jpg"},"fields":{"readingTime":{"text":"7 min read"}}},"file":{"childImageSharp":{"fluid":{"base64":"data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAANABQDASIAAhEBAxEB/8QAFwAAAwEAAAAAAAAAAAAAAAAAAAMEBf/EABUBAQEAAAAAAAAAAAAAAAAAAAED/9oADAMBAAIQAxAAAAGFz11jKaIn/8QAGhAAAgMBAQAAAAAAAAAAAAAAAAECERMSMf/aAAgBAQABBQLm3gxwaJTxe1i8/8QAGBEAAgMAAAAAAAAAAAAAAAAAAAECElH/2gAIAQMBAT8BUdKn/8QAFhEBAQEAAAAAAAAAAAAAAAAAABEB/9oACAECAQE/Abqv/8QAGhAAAQUBAAAAAAAAAAAAAAAAAQACEBESIv/aAAgBAQAGPwJckOjObVBtR//EABwQAQACAgMBAAAAAAAAAAAAAAEAETFBIWFxkf/aAAgBAQABPyEVB9ih2jUSxfkFQDkWX4Ju5grU/9oADAMBAAIAAwAAABDjD//EABYRAQEBAAAAAAAAAAAAAAAAAAEAIf/aAAgBAwEBPxAA1M//xAAWEQEBAQAAAAAAAAAAAAAAAAABIRD/2gAIAQIBAT8QWYTP/8QAGhABAQEAAwEAAAAAAAAAAAAAAREAIUFxwf/aAAgBAQABPxAYkFlcFzRnCFCH3zCCggiKI5gk6hL1lpwEhs0zEABv/9k=","aspectRatio":1.4970059880239521,"src":"/static/11cdcb302d032fa2db3a46428a8f74c9/a7715/alex-machado-80sv993luki-unsplash.jpg","srcSet":"/static/11cdcb302d032fa2db3a46428a8f74c9/8f7df/alex-machado-80sv993luki-unsplash.jpg 250w,\n/static/11cdcb302d032fa2db3a46428a8f74c9/0f3a1/alex-machado-80sv993luki-unsplash.jpg 500w,\n/static/11cdcb302d032fa2db3a46428a8f74c9/a7715/alex-machado-80sv993luki-unsplash.jpg 1000w,\n/static/11cdcb302d032fa2db3a46428a8f74c9/37d86/alex-machado-80sv993luki-unsplash.jpg 1500w,\n/static/11cdcb302d032fa2db3a46428a8f74c9/a41d1/alex-machado-80sv993luki-unsplash.jpg 2000w,\n/static/11cdcb302d032fa2db3a46428a8f74c9/6a059/alex-machado-80sv993luki-unsplash.jpg 6000w","sizes":"(max-width: 1000px) 100vw, 1000px"}}}},"pageContext":{"slug":"ctf/aws-formation/tp5-auto-scaling-group","featuredImage":"alex-machado-80sv993luki-unsplash.jpg"}}}