This repository provides example Amazon CDK stacks to deploy containers to Amazon ECS using Bottlerocket OS for the compute. This includes deploying a Bottlerocket updater in a stack with its CloudFormation template.
(Assume account/region are bootstrapped)
ARCH=arm64 cdk deploy k-ecs-bottlerocket-arm64 --require-approval neverOr
ARCH=x86_64 cdk deploy k-ecs-bottlerocket-x86-64 --require-approval neverTo watch the updater in realtime, you can tail the logs to gain insight into what's happening.
To tail the logs via the AWS CLI, run the following command:
aws logs tail --since 1h --follow <LOG_GROUP_NAME_HERE>What is happening in realtime is the updater monitors for any hosts that are on an older version of the OS.
When it finds hosts that are outdated, it will begin to work in waves.
It will determine which host to update, and begins by putting the host into a DRAINING state.
Next, the scheduler will schedule those tasks to a new host which will come up because of capacity providers and cluster autoscaling.
Finally, once the tasks are rescheduled the OS update will take place and when the update is complete it will reboot and register back into the cluster.
Navigate to the ECS Console, and drill down into the ECS Instances.
When the updater begins the update process, it will first set the instance to DRAINING as mentioned above.
When this happens, pay attention as the scheduler will begin the process of rescheduling the tasks to a new instance.
This will take a couple of minutes as cluster autoscaling will kick in to bring up a new host to run the tasks.
cdk destroy -f k-ecs-bottlerocket-arm64
cdk destroy -f k-ecs-bottlerocket-x86-64