-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Description
Describe the feature
Request to add Windows Server 2025 support in the WindowsVersion enum within the AWS CDK EC2 module. This addition is crucial for the AWS License Manager team's EC2 image pipeline workflows.
Use Case
As part of the AWS License Manager team, we are building EC2 image pipelines that require Windows Server 2025 support. Our EC2 Image Builder pipeline specifically depends on the aws-ec2 lib/WindowsVersion enum to retrieve Windows version names for image naming conventions. Currently, due to the absence of Windows 2025 in the enum:
We are forced to use hardcoded values as a temporary solution:
- This workaround is not sustainable for production environments
- It introduces potential maintenance and reliability issues
- It bypasses the standardized approach used by other AWS teams
Proposed Solution
Update the WindowsVersion enum in packages/@aws-cdk/aws-ec2/lib/windows-versions.ts to include Windows Server 2025 entries:
export enum WindowsVersion {
// ... existing versions ...
WINDOWS_SERVER_2025_ENGLISH_FULL_BASE = 'Windows_Server-2025-English-Full-Base',
WINDOWS_SERVER_2025_ENGLISH_CORE_BASE = 'Windows_Server-2025-English-Core-Base',
}
Other Information
Current Impact: The lack of Windows 2025 support affects the License Manager team's ability to build standardized production pipelines
Related Documentation: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.WindowsVersion.html
Change Type: Non-breaking addition to existing enum
Implementation Complexity: Low (simple enum extension)
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
CDK version used
aws-cdk: 2.178.2 aws-cdk-lib: 2.178.2
Environment details (OS name and version, etc.)
OS: Amazon Linux 2 (Karoo) EC2 Instance Type: c5.4xlarge System Manufacturer: Amazon EC2