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
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
🪲 bug report
🚀 feature request
📚 construct library gap
☎️ security issue or vulnerability => Please see policy
❓ support request => Please see note at the top of this template.
// For other custom (Linux) images, instantiate a `GenericLinuxImage` with// a map giving the AMI to in for each region:constlinux=newec2.GenericLinuxImage({'us-east-1': 'ami-97785bed','eu-west-1': 'ami-12345678',// ...});
What is the expected behaviour (or behaviour of feature suggested)?
Expand the feature to allow allow custom window image
e.g.
// For other custom (Windows) images, instantiate a `GenericWindowImage` with// a map giving the AMI to in for each region:constwindowsImage=newec2.GenericWindowImage({'us-east-1': 'ami-97785bed','eu-west-1': 'ami-12345678',// ...});
What is the motivation / use case for changing the behaviour or adding this feature?
Due to the time it takes to build and a patch Windows environments install and install any necessary features etc. We create a custom AMI on a pipeline and then switch over in the ASG for Blue/ Green deployment.
Customs that are migrating system from Windows can not deploy any pre-built hardened/golden image/ or marketplace image via CDK,
Please tell us about your environment:
CDK CLI Version: 1.1.0
Module Version: xx.xx.xx
OS: [all ]
Language: [all ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered:
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
What is the current behaviour?
Currently when creating an EC2 machine from an image you can only create a Windows server
by selecting the Windows version the AMI this then looked up using the values published to the SSM parameter store. this actical explains how that works.
https://aws.amazon.com/blogs/mt/query-for-the-latest-windows-ami-using-systems-manager-parameter-store/
Example Below
but for Linux you you have the choice of:
or
Expand the feature to allow allow custom window image
e.g.
Due to the time it takes to build and a patch Windows environments install and install any necessary features etc. We create a custom AMI on a pipeline and then switch over in the ASG for Blue/ Green deployment.
Customs that are migrating system from Windows can not deploy any pre-built hardened/golden image/ or marketplace image via CDK,
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered: