- 最新
- 最多得票
- 最多評論
As announced in EC2's Blog Post in 2021 1 and more recently through an email campaign, after Dec 31st 2022 AWS will not be adding support for newly released instance types to EC2 Auto Scaling groups that use launch configurations. As a customer of Elastic Beanstalk, your Environments that are configured to use launch configurations will continue to be supported past this date, but no newly released instance types will be available for use in those environments. Environments configured to use launch configurations will function as expected and attempts to Update with a new (unsupported) instance type will fail. If you are interested in configuring your Environment to use launch templates, you may migrate your Environment to an AL2 platform 2 and set IMDSDisableV1 to true 3. For more information on the IAM policies required to use launch templates, see our developer guide 4.
相關內容
- 已提問 1 年前
- 已提問 6 個月前
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 9 個月前
Hi @Shahad_C , We have already done all of those: 1 - Our Environment is on an AL2 platform 2 - IMDSDisableV1 is set to true 3 - We are using the AWS managed IAM policies that have the correct permissions for LaunchTemplates
Yet our environment still uses launch configurations and there is nothing documented on how to migrate an existing environments to use LaunchTemplates. Nothing seems exposed on Elastic Beanstalk to make this possible. Even cloning the environment keeps the launch configuration. Only brand new Applications seem to use LaunchTemplates. Please advise.
Hi @duckworth - Are there EBExtensions which might be forcing the environment to use a launch configuration? I'm not able to see your account information here, do you have a support plan where you can open a support case to have someone look into your specific settings?