Skip to content

Commit 293325f

Browse files
committed
Add an example aws command for querying valid AMI images
The current WMCO docs for AWS only mention "Windows Server 2019, version 1809 Long-Term Servicing Channel (LTSC)" as a supported Windows version. For newcomers to Windows containers and AWS it's hard to figure out the right AMI to use. The example command added in this pull request is actually taken from upstream: https://github.com/openshift/windows-machine-config-operator/blob/master/hack/machineset.sh#L82
1 parent cfb4649 commit 293325f

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

windows_containers/creating_windows_machinesets/creating-windows-machineset-aws.adoc

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,14 @@ You can create a Windows `MachineSet` object to serve a specific purpose in your
1212
== Prerequisites
1313

1414
* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
15-
* You are using a supported Windows Server as the operating system image.
15+
* You are using a supported Windows Server as the operating system image.
16+
+
17+
Use the following `aws` command to query valid AMI images:
18+
+
19+
[source,terminal]
20+
----------
21+
aws ec2 describe-images --region <aws region name> --filters "Name=name,Values=Windows_Server-2019*English*Full*Containers*" "Name=is-public,Values=true" --query "reverse(sort_by(Images, &CreationDate))[*].{name: Name, id: ImageId}" --output table
22+
----------
1623

1724
include::modules/machine-api-overview.adoc[leveloffset=+1]
1825
include::modules/windows-machineset-aws.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)