chore(ecs): add Windows2025 AMI

[phuhung273]

Issue # (if applicable)

None

Reason for this change

https://aws.amazon.com/about-aws/whats-new/2025/07/aws-availability-ecs-optimized-windows-server-2025-amis/

Description of changes

• Add Windows 2025 AMI
• Integ update instance type + image since old ones no longer compatible

Error of old image on Windows2025

CannotStartContainerError: Error response from daemon: container f21c7ecd0047ff6ab04059523979ab2c16f20efa2a40a8a68d718fa30131f40c encountered an error during hcs::System::Start: failure in a Windows system call: The container operating system does not match the host operating system.

Describe any new or updated permissions being added

Description of how you validated changes

Integ

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[kumsmrit]

Thank you for your contribution.

The ECS API does seem to support Windows Server 2025 as an operating system family: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RuntimePlatform.html. Please consider adding these to runtime-platform.ts and validate if integ test error still occurs.

[phuhung273]

Thanks for taking a look @kumsmrit, I can confirm the same issue as of today on us-east-1

Looking at cpuArchitecture param description You can run your Linux tasks on an ARM-based platform by setting the value to ARM64. This option is available for tasks that run on Linux Amazon EC2 instance or Linux containers on Fargate, I also tried to remove it but same error.

Could you help inform ECS team ?

[phuhung273]

@kumsmrit I can see #34981 already covered runtime-platform.ts

[kumsmrit]

@kumsmrit I can see #34981 already covered runtime-platform.ts

Thank you for linking the associated PR. I was waiting on getting update from ECS team, but since that change is already merged, approving this current PR for other changes.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

Pull request has been modified.

[phuhung273]

Thanks so much for helping @kumsmrit

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: d05b44b
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.