Your SlideShare is downloading. ×
  • Like
Auto Scaling Guided by Code
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Auto Scaling Guided by Code



Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Auto Scaling Guided by Code Pablo Cantero @pablocantero 19/09/2012
  • 2. Cloud Computing• Pay-as-you-go• Scale Resources up or down based on demand (Elastic Architecture)
  • 3. Auto Scaling steps
  • 4. Instance provisioning• Manually • Image (preconfigured)• Automated • Chef • Puppet • CloudFormation
  • 5. Create a launch configuration. The launch configuration are parameters to launchinstances, such as image (AMI), instance type, security group, key pair and user data.
  • 6. Create an auto scaling group. The auto scaling group defines the auto scaling conditions,minimum and maximum number of instances, available zones, default cool down and load balancer (ELB).
  • 7. Create a scaling policy. The scaling policydefines how the auto scaling should scale up or down, if it is by size or percent and the cool down.
  • 8. Create an alarm metric. The alarm metric is the metric used to decide when to increase ordecrease the instances. Usually by response time. The metrics are provided by CloudWatch.
  • 9. Alarm metrics
  • 10. Create an alarm request. It is the last step to setup the Auto Scaling. The alarm requestdefines how to measure the metrics defined by the alarm metric, for example the time and period to evaluate the metric.
  • 11. Talk is cheap. Show me the code.
  • 12. Some advices
  • 13. Don’t name your instancesYou should change your instances as you change your underwear. Lucas Teixeira
  • 14. Don’t forget to remove your tests
  • 15. Use Auto Scaling, avoid Cloud Smells avoid-cloud-smells/
  • 16. Thank you Pablo Cantero @pablocantero