search

secdevops-cuse / CyberRange

The Open-Source AWS Cyber Range
https://medium.com/aws-cyber-range
464 stars 90 forks source link

Update Windows AMIs to resolve EC2 ImportImage issue #41

Closed cappetta closed 4 years ago

cappetta commented 5 years ago

We have found you may be affected by an issue present in the version 2.0.0 of Windows Enhanced Network Architecture (ENA) drivers installed by the EC2 ImportImage API between March 15, 2019 and June 4, 2019. Since then, the API has been reverted to use version 1.5 of the drivers where this issue isn’t present. If you created Windows ENA enabled AMIs through the EC2 ImportImage API calls between March 15, 2019 and June 4, 2019, you will have to kick off a new task to migrate to the fixed drivers[1]. You can also manually install the updated drivers onto your existing AMIs by following the steps outlined for downloading and enabling ENA drivers.[2]

Should you have any questions or concerns, or have trouble manually updating drivers, please contact the AWS Support team via Support Center [3].

[1] https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html [2] https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/enhanced-networking-ena.html#enable-enhanced-networking-ena-WIN [3] https://aws.amazon.com/support

cappetta commented 5 years ago

CommandoVM went through a recycle and new image release. metasploitable 2/3 were untouched. Not sure the impact but so far there are no major concerns noticed.

ToDo: Task - Consider finding the list of images created during this time by querying the api. Not sure what that will reveal - there maybe no action needed...

cappetta commented 4 years ago

this has been resolved when deploying AMI's to regions.