Course contentsShow
← Cloud and Infrastructure
Lesson 314 of 2,9896. Auto ScalingFree lesson

ASG Launch Templates and Configurations

Understanding launch templates vs launch configurations and their settings for instance provisioning.

ASG Launch Templates and Configurations

What You'll Learn

You'll understand the two ways AWS lets you define how your Auto Scaling Group should launch instances, and which one you should use today.


The Core Idea

When an Auto Scaling Group needs to launch a new EC2 instance (scaling out), it needs instructions: What AMI? What instance type? Which security groups? Network settings? Think of it like a recipe card for baking identical cookies.

AWS offers two recipe formats:

Launch Configurations (Legacy)

The older format, now largely deprecated. You define instance settings once, and they're immutable — you can't edit them. Want to change the instance type? You must create an entirely new launch configuration and update your ASG to use it.

Limitations:

  • Cannot be modified after creation
  • No versioning
  • Doesn't support newer features (mixed instance types, multiple instance types, spot instance flexibility)

Launch Templates (Modern)

The current best practice. Launch templates are versioned — you can create v1, then v2 with updated settings, and roll back if needed. They support all the latest AWS features.

Advantages:

  • Editable with versioning (like document revision history)
  • Support for multiple instance types
  • Support for spot + on-demand mixing
  • Built-in T2/T3 unlimited mode
  • Can specify multiple network interfaces
  • Future-proof for new AWS features

Settings Both Include

  • AMI ID (which OS image)
  • Instance type (t3.medium, etc.)
  • Security groups
  • SSH key pairs
  • IAM instance profile
  • User data scripts
  • Storage volumes

Key Takeaway: Always use Launch Templates over Launch Configurations — they're more flexible, versioned, and support modern Auto Scaling features like mixed instance policies. Launch Configurations are legacy and should be avoided in new deployments.