[ECS] [request]: Support Amazon Linux 2023 for underlying hosts on Fargate

[BwL1289]

Is there a timeline for the implementation of AL2023 for underlying hosts on Fargate launch type?

Amazon ECS Optimized Amazon Linux 2023 AMI is already supported for EC2, but Fargate offers significant abstractions that users love so we can build without the "undifferentiated heavy lifting" of managing fleets.

Seems like this is currently being worked on for EKS.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request Support for AL2023 for underlying hosts on Fargate launch type

Which service(s) is this request for? ECS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Many newer technologies are tied to, and rely on, advancements that AWS has made, and tight coupling is an inevitable reality. It would be advantageous to rely on AWS to manage infrastructure with support for an up to date kernel and tooling.

Why is this needed: Support for a more recent kernel and tools.

Are you currently working around this issue? Using EC2 launch type.

[mlanner-aws]

Rather than a specific Linux distro, what kernel version is it that you would like to see and what are the corresponding tools that require that kernel version? If the tools are independent of the kernel version, you can just bake them into your container image, but if there's a real kernel dependency, we'd like to learn more.

FWIW, Fargate is unlikely to ever use AL2023 as the underlying host operating system and is more likely to move to Bottlerocket as Bottlerocket is optimized for container workloads rather than being a general purpose Linux distro with a feature set that's more applicable to what Fargate needs as a service.

[BwL1289]

@mlanner-aws Bottlerocket is much preferred. Many of our issues will resolve with this transition.

Our only real dependency is the kernel version (6.1+). We rely heavily on graviton specific optimizations for native code and sometimes, for example, some features like bfloat16 don't work perfectly on kernels older than 6.

Is there an ETA to migrate to Bottlerocket so we can plan? Appreciate the support.

[BwL1289]

@mlanner-aws any update on Bottlerocket timeline? Thanks!