AWS Launch Template

-

 

Launch template allows you to have multiple versions of a launch template unavailable in launch configurations.

Launch Templates streamline and simplify the launch process for Auto Scaling, Spot Fleet, Spot, and On-Demand instances.

Launch Templates reduce the steps required to create an instance by capturing all launch parameters within one resource.

For each launch template, you can create one or more numbered launch template versions. 

Each version can have different launch parameters.

When you launch an instance from a launch template, you can use any version of the launch template.

If you do not specify a version, the default version is used.

You can set any version of the launch template as the default version—by default, it's the first version of the launch template.

Launch Configuration(Legacy): Must be recreated every time because the modification is not allowed.

Launch Template (Recommended By AWS) :

Allows to edit and update.

Maintains versions.

Can use T2 unlimited burst feature.

Allow provisioning using both On-demand and Spot Instances.

Creation of parameter subsets. (Partial configuration for reuse and inheritance)

It can also be used to launch a standalone instance using AWS Console, SDK, and CLI.

We are creating a launch template with version 1 which will show output as "Welcome to My App - Version1"




Now, Let's create an instance from the template version 1.

It works. Now, Let's modify the launch template to show the output as " Welcome to My App -Version 2"



Now, We need to set version 2 as the default version.

Let's create an instance from the launch template version 2.



Deleting a launch template version. NOTE: The launch template of the default version cannot be deleted.


Deleting the launch template.









Comments

Post a Comment

Popular posts from this blog

SRE/DevOps Syllabus

-
Image
  DEVOPS/SRE Principles. Git What is Git? Architecture of Git. Working principle of Git. Create and cloning a repo. Version control branching. Version control commit. Version control managing workflows. Git hooks. Git Reflog. Git Stash. Git Cherry Picking. Undoing changes in different states of Git. Git based terraform template management. AWS CI/CD SDLC Automation. Code Commit. Code Build. Code Deployment. Code Pipeline. Elastic Beankstalk. Code Artifact. CodeGuru. Terraform Terraform Basics. Terraform State. Working with Terraform. Terraform with AWS. Remote State. Terraform Provisioners. Terraform Import, Tainting and Debugging. Terraform Modules. Terraform Functions and Conditional Expressions. Automation using Python - AWS AWS lambda. Automating EC2 with Lambda. Automating S3 with Lambda. Automating VPC with Lambda. Cost optimization with Lambda. SNS,SQS and SES with Python. Managing and Automating AWS Security with Python. Kubernetes - CKAD Application Developer. Kubernetes A...
Read more

AWS Code Commit - CI/CD Series Part 1

-
Image
  This is a multi-part series to show how to implement a CI/CD pipeline in AWS. In this post, We will see how to use AWS Code Commit. AWS CodeCommit is a fully managed source control service that allows you to store and manage your code securely in the cloud.  It provides a private Git repository for your code and supports all Git commands and workflows. CodeCommit also integrates with other AWS services like AWS CodePipeline and AWS CodeBuild, allowing you to automate your entire software release process. This can help you streamline your development workflows and improve the overall efficiency of your team. I created a repo from AWS CodeCommit -> Create Repository. And I begin with cloning the repo locally. So that I can make changes and push it. To clone the repo click on "HTTPS" under Clone URL. I make changes to index.html file. Now push it to AWS CodeCommit. Let’s verify the changes in AWS Code commit. Changes are reflected in AWS CodeCommit. We are done with Part ...
Read more

Docker - Preventing IP overlapping

-
Image
  What is IP address overlapping? When the container IP address overlaps with another IP external, then the application running on the container is not accessible from outside due to the IP address overlapping.  NOTE: This IP address overlapping can happen on the bridge interface IP or docker container IP. Let's see how to address this IP overlapping issue on the bridge interface. I already have a running container.  root@demo:~# docker run -d --name web --network mynet1 nginx:alpine 268647e11011d513d2357ce1c81e0f48787038a83d01d028d31a5b29dbdb885b root@demo:~# docker container ls CONTAINER ID   IMAGE          COMMAND                  CREATED         STATUS         PORTS     NAMES 268647e11011   nginx:alpine   "/docker-entrypoint.…"   4 seconds ago   Up 3 seconds   80/tcp  ...
Read more