Difference between revisions of "AWS launch template"
Jump to navigation
Jump to search
Line 16: | Line 16: | ||
* <code>[[controller.aws.launchtemplate]]</code> | * <code>[[controller.aws.launchtemplate]]</code> | ||
* <code>[[kind: AWSNodeTemplate]]</code> | * <code>[[kind: AWSNodeTemplate]]</code> | ||
− | * [[ | + | * [[Terraform data source: aws ami]] |
== News == | == News == |
Revision as of 14:38, 2 April 2023
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html
- We strongly recommend that all Auto Scaling groups use launch templates to ensure full functionality for Amazon EC2 Auto Scaling and Amazon EC2.
- If you use Auto Scaling groups and you need to require the use of IMDSv2 on all new instances, your Auto Scaling groups must use launch templates.
- Karpenter best practices strongly recommends against using custom launch templates
Related
- Terraform resource:
aws_launch_template
controller.aws.launchtemplate
kind: AWSNodeTemplate
- Terraform data source: aws ami
News
See also
- AWS launch template,
aws ec2 create-launch-template, aws autoscaling update-launch-configuration
- AWS EC2, Amazon EC2 API,
aws ec2, AWS::EC2
, Amazon EC2 Spot Instances, CPU credits, Instance type, EC2 limitations, 169.254.169.254, Instance metadata and user data (IMDS),InstanceType, InstanceId
, Amazon EC2 Auto Scaling, AWS EC2 Instance Connect, launch template, lifecycle, AWS Security group (SG), Amazon EC2 Recycle Bin, Amazon EC2 Mac Instances, Global View
Advertising: