There and Back Again...With AWS Auto Scaling


Auto scaling has been one of the most talked about AWS services, and for good reason. Briefly, auto scaling makes available instrumentation and automation that is typically employed to address availability and ‘cost optimization’.



Auto scaling has been one of the most talked about AWS services, and for good reason. Briefly, auto scaling makes available instrumentation and automation that is typically employed to address availability and ‘cost optimization’. It does this by enabling and managing horizontal scale of grouped EC2 instances. Members of that group can be dynamically added and removed based on a number of defined and monitored criteria. Additional details can be found here.

Hey, Over Here…

While being able to react with massive scale in an automated fashion (the ‘there’) is indeed one of the more sexy features of auto scaling, practical implications (such as ‘the back again’) are often less touted and overlooked.

Travel Light

While I may not immediately need to dynamically scale out my application, I also don’t need to run my application with resources I have typically allocated in a traditional (whether virtual or physical) static manner. As the comparison illustrates below, with AWS auto scaling I can run my application with significantly less resources (using a smaller instance type for example) and scale out as needed, avoiding any potential waste that occurs at times in traditional environments.

iTMethods is a Global AWS Cloud and Managed Services Provider. Our organization was founded on the premise of developing long term, transparent relationships where open communication, agile execution, collaboration and trust are the hallmarks for enduring success.
CONTACT
Paul Goldman
innovate@itmethods.com
888-248-9122
  Company Website
  Linkedin
  Company Blog
  Google +