Launch Template
vs
Launch Configuration


Launch Templates were introduced in 2017. At a high level, both Launch Templates and Launch Configuration are used to configure AMI, Instance Type, Key Pair, etc in order to launch new instances in Auto Scaling environment.
However, Launch Templates allow you to version the template which was not the possible using Launch Configuration. The common practice is to create a default template with standard configuration and create new versions which allows specifying new parameters.
With Launch Templates, you can also provision instances across multiple instance types using On-Demand and Spot Instances. It was not possible using Launch Configuration.
You can also launch instances right from the Launch Templates. It allows you to have single source of configuration for your instances. It is worth mentioning that instances created directly using Launch Templates are not put under Auto Scaling by default.
Below animation demonstrates simple process of creating a launch template.

Once a basic launch template is created, you can take do any of the following:



Out of three options, option 1 and 3 cannot be done using Launch Configuration. Option 1 is useful for provisioning instances from same template which leads to greater consistency.
Option second allows you to launch fleet of spot instances with configuration steps as shown below:

Hope it helps in understanding the key differences between Launch Templates and Launch Configuration.