Open juinquok opened 7 months ago
Thank you for the possible solution
. Yes this might be an option. Making this a p1 as it's not easy to work it around.
Happy to help raise a PR to implement it if the possible solution is acceptable :)
Also experiencing this. Need an option to specify AMAZON_LINUX_2023
.
@juinquok also happy to help with this.
Additionally, we should add a note that if you choose BOTTLEROCKET
you need to be using it in your ASG machine image. Experienced a bug today that cost me a bunch of hours due to userData
not being set so the ecs agent
did not know the name of the cluster.
Just to add: We've noticed this issue with AL2 as well. We solved it by installing iptables-services in the userdata, so that the command can be run.
@pahud Should I raise a PR to implement this change if its agreeable with the team?
@juinquok Yes feel free to submit a PR and let's move this forward.
Describe the bug
When using EC2 as the capacity provider in the
addAsgCapacityProvider
method, the user is expected to specify themachineImageType
for the capcity provider. In doing so, it will add a user data script that will inject additional data that is relevant to the user for the /etc/ecs/ecs.config fileOne of the commands that is injected is:
On AWS Linux 2023 running the Linux 6.1.66-91.160.amzn2023.x86_64 kernel, this command results in an error when executing the cloud-init file.
This results in the line after
to not get run which is not ideal.
Expected Behavior
It should successfully run the required ECS setup configs when the EC2 instance starts.
Current Behavior
The cloud-init script will fail with the error message
The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, reload-or-restart, try-reload-or-restart, force-reload, status, condrestart). For other actions, please try to use systemctl.
Reproduction Steps
Start an ECS Cluster with an EC2 capacity provider and the AMI in the launch template for the autoscaling group to be the latest AWS Linux 2023 AMI (
ecs.EcsOptimizedImage.amazonLinux2023(AmiHardwareType.STANDARD)
). The error will occur when the instance starts up and the logs can be found in/var/log/cloud-init-output.log
Possible Solution
Introduce a new
machineImageType
in theaddAsgCapacityProvider
method and name itAMAZON_LINUX_2023
. In theconfigureAutoScalingGroup
method incluster.ts
, add in a new switch condition to render different user data for the ECS Optimized AMI for AWS Linux 2023. In particular, thesudo service iptables save
will be changed tosudo iptables-save > /etc/sysconfig/iptables
which will not throw the same error as above.Additional Information/Context
No response
CDK CLI Version
2.114.1 (build 02bbb1d)
Framework Version
No response
Node.js Version
v18.17.0
OS
macOS 14.2
Language
TypeScript
Language Version
No response
Other information
No response