AMI for Windows Server 2025 with SQL Server 2022 Web

Hello.

You can search using the AWS CLI command below.
For example, by executing the following command, you can search for Windows Server AMIs that can be used with "ap-northeast-1".
Please change the "--region" option to the region you are using and run the command.

aws ec2 describe-images --owners 'amazon' --filters 'Name=platform,Values=windows' 'Name=name,Values=*Windows_Server-2025-*' --query 'reverse(sort_by(Images, &CreationDate))[*].{Architecture:Architecture, CreationDate:CreationDate, ImageId:ImageId, Name:Name}' --output table --region ap-northeast-1

When you run the command, you can check it in table format as shown below.
The AMI for Microsoft Windows Server 2025 SQL Server2022 is listed in this table.

------------------------------------------------------------------------------------------------------------------------------------------
|                                                             DescribeImages                                                             |
+--------------+---------------------------+------------------------+--------------------------------------------------------------------+
| Architecture |       CreationDate        |        ImageId         |                               Name                                 |
+--------------+---------------------------+------------------------+--------------------------------------------------------------------+
|  x86_64      |  2025-02-13T06:20:01.000Z |  ami-0adb21c94a12bcac2 |  TPM-Windows_Server-2025-English-Full-Base-2025.02.13              |
|  x86_64      |  2025-02-13T06:19:59.000Z |  ami-0c11c8940b57103ee |  TPM-Windows_Server-2025-English-Core-Base-2025.02.13              |
|  x86_64      |  2025-02-13T06:19:36.000Z |  ami-0b5e57f433d91edb8 |  BIOS-Windows_Server-2025-English-Full-Base-2025.02.13             |
|  x86_64      |  2025-02-13T06:18:19.000Z |  ami-063f9244eacaf3565 |  Windows_Server-2025-English-Full-SQL_2022_Web-2025.02.13          |
|  x86_64      |  2025-02-13T06:18:13.000Z |  ami-04d6f5abe482e49a6 |  Windows_Server-2025-English-Full-SQL_2022_Standard-2025.02.13     |
|  x86_64      |  2025-02-13T06:18:12.000Z |  ami-0bb92e0f5b36b13fd |  Windows_Server-2025-English-Full-SQL_2022_Express-2025.02.13      |
|  x86_64      |  2025-02-13T06:18:06.000Z |  ami-0f7fb69cc988d0d19 |  Windows_Server-2025-English-Full-SQL_2022_Enterprise-2025.02.13   |
|  x86_64      |  2025-02-13T06:14:17.000Z |  ami-001fad2242d549ca7 |  Windows_Server-2025-Japanese-Full-Base-2025.02.13                 |
|  x86_64      |  2025-02-13T06:14:14.000Z |  ami-01d05abe0a27737b0 |  Windows_Server-2025-Korean-Full-Base-2025.02.13                   |
|  x86_64      |  2025-02-13T06:14:12.000Z |  ami-0b51a1c68e86976b6 |  Windows_Server-2025-English-Full-Base-2025.02.13                  |
|  x86_64      |  2025-02-13T06:14:07.000Z |  ami-056ad02ac0f7224f3 |  Windows_Server-2025-English-Core-Base-2025.02.13                  |
|  x86_64      |  2025-02-13T06:14:04.000Z |  ami-003c2fc12d6ca9d3c |  Windows_Server-2025-Chinese_Traditional-Full-Base-2025.02.13      |
|  x86_64      |  2025-02-13T06:13:58.000Z |  ami-035464a6f1aab04ae |  Windows_Server-2025-Chinese_Simplified-Full-Base-2025.02.13       |
|  x86_64      |  2025-01-16T02:31:42.000Z |  ami-0fc79477358193e22 |  Windows_Server-2025-English-Full-SQL_2022_Enterprise-2025.01.15   |
|  x86_64      |  2025-01-16T02:28:18.000Z |  ami-0bc1bcac13d1039ea |  TPM-Windows_Server-2025-English-Full-Base-2025.01.15              |
|  x86_64      |  2025-01-16T02:26:43.000Z |  ami-0c201ed5848fe00b7 |  TPM-Windows_Server-2025-English-Core-Base-2025.01.15              |
|  x86_64      |  2025-01-16T02:21:39.000Z |  ami-0aa0d1d469906d1df |  BIOS-Windows_Server-2025-English-Full-Base-2025.01.15             |
|  x86_64      |  2025-01-16T02:21:21.000Z |  ami-0d7d1e70671831651 |  Windows_Server-2025-English-Full-SQL_2022_Web-2025.01.15          |
|  x86_64      |  2025-01-16T02:21:19.000Z |  ami-0449cb0b3be6150ad |  Windows_Server-2025-English-Full-SQL_2022_Standard-2025.01.15     |
|  x86_64      |  2025-01-16T02:21:15.000Z |  ami-0422c8e05fb6dc8ca |  Windows_Server-2025-English-Full-SQL_2022_Express-2025.01.15      |
|  x86_64      |  2025-01-16T02:16:18.000Z |  ami-0c5e7a9d397b758cd |  Windows_Server-2025-Japanese-Full-Base-2025.01.15                 |
|  x86_64      |  2025-01-16T02:16:16.000Z |  ami-01e2f44faacca236f |  Windows_Server-2025-Korean-Full-Base-2025.01.15                   |
|  x86_64      |  2025-01-16T02:16:14.000Z |  ami-0229252f7173d9c82 |  Windows_Server-2025-English-Full-Base-2025.01.15                  |
|  x86_64      |  2025-01-16T02:16:09.000Z |  ami-02925597c57e348f1 |  Windows_Server-2025-English-Core-Base-2025.01.15                  |
|  x86_64      |  2025-01-16T02:16:05.000Z |  ami-0c614de7a19626de5 |  Windows_Server-2025-Chinese_Traditional-Full-Base-2025.01.15      |
|  x86_64      |  2025-01-16T02:16:04.000Z |  ami-07556d705299cba38 |  Windows_Server-2025-Chinese_Simplified-Full-Base-2025.01.15       |
|  x86_64      |  2024-12-13T08:25:07.000Z |  ami-0d2a23d210550ca7c |  Windows_Server-2025-English-Full-SQL_2022_Standard-2024.12.13     |
|  x86_64      |  2024-12-13T08:22:48.000Z |  ami-0af8595acfc0c723f |  Windows_Server-2025-English-Full-SQL_2022_Web-2024.12.13          |
|  x86_64      |  2024-12-13T08:22:23.000Z |  ami-03041709e26d4d492 |  TPM-Windows_Server-2025-English-Full-Base-2024.12.13              |
|  x86_64      |  2024-12-13T08:19:57.000Z |  ami-00c47a6aec0b52bbb |  BIOS-Windows_Server-2025-English-Full-Base-2024.12.13             |
|  x86_64      |  2024-12-13T08:18:36.000Z |  ami-032a4bd36a150d034 |  TPM-Windows_Server-2025-English-Core-Base-2024.12.13              |
|  x86_64      |  2024-12-13T08:11:03.000Z |  ami-0c16441980a150727 |  Windows_Server-2025-English-Full-SQL_2022_Enterprise-2024.12.13   |
|  x86_64      |  2024-12-13T08:09:58.000Z |  ami-08c50fbdf51a913af |  Windows_Server-2025-English-Full-SQL_2022_Express-2024.12.13      |
|  x86_64      |  2024-12-13T08:05:04.000Z |  ami-0eee317a7ef463742 |  Windows_Server-2025-Japanese-Full-Base-2024.12.13                 |
|  x86_64      |  2024-12-13T08:05:00.000Z |  ami-087a94c0fefc6cbce |  Windows_Server-2025-Korean-Full-Base-2024.12.13                   |
|  x86_64      |  2024-12-13T08:04:58.000Z |  ami-042b01a80943e830b |  Windows_Server-2025-English-Full-Base-2024.12.13                  |
|  x86_64      |  2024-12-13T08:04:56.000Z |  ami-00497e8e3777b2871 |  Windows_Server-2025-English-Core-Base-2024.12.13                  |
|  x86_64      |  2024-12-13T08:04:49.000Z |  ami-09b57d9b79532210b |  Windows_Server-2025-Chinese_Traditional-Full-Base-2024.12.13      |
|  x86_64      |  2024-12-13T08:04:47.000Z |  ami-03e76cf8a26a4a82b |  Windows_Server-2025-Chinese_Simplified-Full-Base-2024.12.13       |
+--------------+---------------------------+------------------------+--------------------------------------------------------------------+

I apologize, but there are a few inaccuracies in your question that I need to address:

1. Windows Server 2025 does not exist yet. The latest version of Windows Server is 2022.

2. For upgrading an existing EC2 instance running Windows Server 2019 with SQL Server Web, you have a few options:

   a. You can use AWS Systems Manager Automation runbooks to upgrade both the Windows Server and SQL Server versions. There's a specific runbook called AWSEC2-CloneInstanceAndUpgradeSQLServer that can help with this process.

   b. You can perform an in-place upgrade, though Microsoft typically recommends migrating to a newer version instead.

   c. You can create a new instance with the desired configuration and migrate your data and settings.

For the latest Windows Server (2022) with SQL Server 2022 Web Edition, you should be able to find an appropriate AMI through the EC2 console. AWS provides a set of publicly available AMIs for Windows Server versions that run on EC2 instances, and these are updated monthly.

If you can't find the exact combination you're looking for, you might need to start with a Windows Server 2022 AMI and then install SQL Server 2022 Web Edition manually.

Remember that AMI availability can vary by region, so make sure to check in your specific region for the most up-to-date options. If you're still unable to find what you need, you may want to contact AWS Support for more specific guidance.
Sources
Upgrade an EC2 Windows instance to a newer version of Windows Server - Amazon Elastic Compute Cloud
Use Automation runbooks to upgrade an EC2 Windows instance - Amazon Elastic Compute Cloud
Windows Server In place upgrades with regards major versions | AWS re:Post