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
{{ message }}
Repository navigation
(2024.04.02 and earlier) Windows NVIDIA instances in ap‐southeast‐2(Sydney) fail to launch
ravipranjal edited this page May 6, 2024
·
1 revision
The issue
Amazon Machine Images (AMIs) are used to spin up virtual desktops (VDIs) in RES with specific configurations. Each AMI has an associated ID that differs per region. The AMI ID configured in RES to launch Windows Nvidia instances in ap-souteast-2 (Sydney) is currently incorrect.
AMI-ID ‘ami-0e190f8939a996caf’ for this type of instance configuration is incorrectly listed in ap-souteast-2 (Sydney). AMI ID ‘ami-027cf6e71e2e442f4’ should be used instead.
Customers will get the following error when trying to launch an instance with the default ‘ami-0e190f8939a996caf’ AMI.
An error occured (InvalidAMIID.NotFound) when calling the RunInstances operation: The image id ‘[ami-0e190f8939a996caf]’ does not exist
Steps to reproduce the bug, including an example configuration file.
Deploy RES in ap-southeast-2 region
Launch an instance using Windows-NVIDIA default software stack (AMI ID ‘ami-0e190f8939a996caf’)
Affected versions
All RES version 2024.04.02 or earlier are impacted
Mitigation
The following mitigation has been tested on RES version 2024.01.01
Register a new software stack with the following settings
AMI ID: ami-027cf6e71e2e442f4
Operating System: Windows
GPU Manufacturer: NVIDIA
Min. Storage Size (GB): 30
Min. RAM (GB): 4
Use this software stack to launch Windows - NVIDIA instances