Home [AWS Solution Architect] ASG (Auto Scaling Groups)
Post
Cancel

[AWS Solution Architect] ASG (Auto Scaling Groups)

ASG (Auto Scaling Groups)

  • Introduction
  • Capacity Settings
  • Health Check Replacements
  • Scaling Policies
    • Target tracking scaling policy
    • Simple scaling policy & Scaling policy with steps
    • Scaling with SQS
  • ELB Integration
  • Use Case
  • Launch Configuration
  • Autoscaling Groups Cheat Sheet

Screen Shot 2022-01-29 at 1 55 37 PM Screen Shot 2022-01-29 at 1 55 46 PM Screen Shot 2022-01-29 at 1 56 11 PM Screen Shot 2022-01-29 at 1 57 22 PM Screen Shot 2022-01-29 at 1 57 58 PM Screen Shot 2022-01-29 at 1 58 43 PM Screen Shot 2022-01-29 at 1 59 21 PM Screen Shot 2022-01-29 at 1 59 52 PM Screen Shot 2022-01-29 at 2 00 32 PM Screen Shot 2022-01-29 at 2 01 23 PM Screen Shot 2022-01-29 at 2 02 25 PM Screen Shot 2022-01-29 at 2 03 56 PM


Screen Shot 2022-01-24 at 2 06 05 PM Screen Shot 2022-01-24 at 2 22 23 PM from AWS (01/24/2022)

  • Key point : μš”μ²­μ˜ 90%, μ„±λŠ₯SLA, 4개의 μΈμŠ€ν„΄μŠ€λ‘œ μš”μ²­μ„ λΆ„μ‚°, μ„±λŠ₯ μš”κ΅¬ 사항을 μΆ©μ‘±, κ³ κ°€μš©μ„±
    • (+) κ°€μš© μ˜μ—­μ— 도달할 수 μ—†λŠ” 경우 (= ν•œκ°œμ˜ κ°€μš©μ˜μ—­μ΄ λ‹€μš΄λ¬μ„ 경우 -> 영문 νŒŒμ•… ν•„μš”)
  • a, b : 단일 AZλŠ” 전체 μ„œλΉ„μŠ€κ°€ λ‹€ λ‹€μš΄λ˜μ–΄μ„œ not correct
    • recommend using multi AZ for high availability, scalability
    • μ˜ˆμ™Έ μΌ€μ΄μŠ€ : cluster network serviceλ₯Ό λ§Œλ“€ λ•Œλ§Œ 단일 AZ μ‚¬μš©μ„ μΆ”μ²œ
  • c : 4개의 μ„œλ²„κ°€ 2개의 AZ에 각각 μžˆλŠ” 건지, λΆ„μ‚°λ˜μ–΄ μžˆλŠ” 건지 μ˜λ¬Έμ—μ„œ ꡬ체적으둜 확인할 ν•„μš”κ°€ 있음
    • 각각이라면, λ‚˜λ¨Έμ§€ AZ에 4개의 μ„œλ²„κ°€ 있기 λ•Œλ¬Έμ— 만쑱
  • d : 8개 too much

** SLA : Service Level Agreement


Amazon EC2 Auto Scaling

Screen Shot 2022-01-24 at 3 16 00 PM

  • Scale up, down : 수직적 쑰징
    • the size of instance, the count of cpu core, memory, etc.
  • Scale in, out : μˆ˜ν‰μ  μ‘°μ •
    • the count of instances -> auto scaling (μˆ˜ν‰μ  쑰정을 μœ„ν•œ κΈ°λŠ₯)

Screen Shot 2022-01-24 at 3 17 10 PM

  • multi AZ에 λ„μšΈ 수 있음
  • ELB 와 ν†΅ν•©ν•΄μ„œ μ‚¬μš© κ°€λŠ₯

Screen Shot 2022-01-24 at 3 18 01 PM from AWS (01/24/2022)

  • Amazon EC2 Auto Scaling
    • 각각의 μ„œλΉ„μŠ€ λ³„λ‘œ scale up, down κ°€λŠ₯
    • EC2 cpu utilization / memory utilization / provisioned throughput like DynamoDB

Screen Shot 2022-01-24 at 3 27 30 PM

  • a : ELB
  • c : cloudwatch
  • d : SNS
  • Answer : B, E, F
    • Amazon EC2 Auto Scaling
      • Amazon EC2 Instanceλ₯Ό μΆ”κ°€, μ’…λ£Œν•˜μ—¬ λ³€ν™”ν•˜λŠ” 상황에 λŒ€μ‘ν•©λ‹ˆλ‹€.
      • μ§€μ •λœ AMIμ—μ„œ Instanceλ₯Ό μ‹œμž‘ν•©λ‹ˆλ‹€.
      • μ‹€ν–‰ Amazon EC2 Instance의 μ΅œμ†Œ 수λ₯Ό μ μš©ν•©λ‹ˆλ‹€.
    • Cloudwatch Screen Shot 2022-01-24 at 3 19 31 PM
      • Role : λ¦¬μ†ŒμŠ€ μƒνƒœλ₯Ό νŒŒμ•…
      • network : throughput (λ„€νŠΈμ›Œν¬μ— 데이터가 μ–Όλ§ˆλ‚˜ μ™”λ‹€κ°”λ‹€ ν•˜κ³  μžˆλŠ”κ°€)
      • μ‚¬μš©μž 지정 μ§€ν‘œ : application λ‚΄λΆ€μ—μ„œ cloud watch μͺ½μœΌλ‘œ, λͺ¨λ‹ˆν„°λ§ν•˜κ³ μž ν•˜λŠ”, 기본적으둜 hiperbizerμ—μ„œ μˆ˜μ§‘ν•  수 μžˆλŠ” μ΄μ™Έμ˜ 값도 λ³΄λ‚΄μ€Œ (μ›Ήμ„œλ²„μ—μ„œλŠ” λ‚΄λΆ€ session 개수, μ‚¬μš©μžμˆ˜, etc / ec2μ—μ„œλŠ” memory μ‚¬μš©λŸ‰, etc)

Screen Shot 2022-01-24 at 3 24 35 PM

  • Key point : 8개의 Amazon EC2 instance, νŠΈλž˜ν”½μ΄ μΌμ‹œμ μœΌλ‘œ 급증, ν‰μ†Œ 2개의 EC2 Instanceκ°€ ν•„μš”, κ°€μž₯ λΉ„μš© 효과적인 방법
  • Answer :γ€€C
  • a, d : 수치(cpu or memory utilization)λ₯Ό λ³΄λ©΄μ„œ ν™•μž₯ν•˜λŠ” 것은 잘 μž‘λ™ν•˜μ§€ μ•Šμ„ μˆ˜λ„ 있음
    • ex. 이미 cpu의 μ‚¬μš©λ„κ°€ μ΄ˆκ³Όν•œ μƒνƒœμ—μ„œ μž₯μ• κ°€ λ°œμƒν•œ λ‹€μŒμ— ν™•μž₯될 수 있음
  • b : κ°€μž₯ λΉ„μš© νš¨κ³Όμ μ΄μ§€ μ•ŠμŒ

Reference

AWS Certified Solutions Architect - Associate 2020 (PASS THE EXAM!), Youtube, uploaded by freeCodeCamp.org, 12/24/2019, https://www.youtube.com/watch?v=Ia-UEYYR44s

This post is licensed under CC BY 4.0 by the author.

[AWS Solution Architect] ELB (Elastic Load Balancer)

[AWS Solution Architect] Cloud watch

Comments powered by Disqus.