You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Windows Server 2025 has been out for a while, but ECS-optimized AMIs do not seem to be available yet, which prevents running Windows Server 2025 containers on ECS.
It appears EC2 AMIs were made available in early November, so this request is to follow up with ECS-optimized AMIs and official ECS support. It's probably in progress, but I could not find an existing request.
Which service(s) is this request for?
ECS (non-Fargate in my specific case)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Are you currently working around this issue?
Continue to stick with Windows Server 2022 Core and mcr.microsoft.com/windows/servercore:ltsc2022 based containers.
Community Note
Tell us about your request
Windows Server 2025 has been out for a while, but ECS-optimized AMIs do not seem to be available yet, which prevents running Windows Server 2025 containers on ECS.
It appears EC2 AMIs were made available in early November, so this request is to follow up with ECS-optimized AMIs and official ECS support. It's probably in progress, but I could not find an existing request.
Which service(s) is this request for?
ECS (non-Fargate in my specific case)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Are you currently working around this issue?
Continue to stick with Windows Server 2022 Core and
mcr.microsoft.com/windows/servercore:ltsc2022
based containers.Additional context
Docs at https://docs.aws.amazon.com/AmazonECS/latest/developerguide/retrieve-ecs-optimized_windows_AMI.html
The text was updated successfully, but these errors were encountered: