- Newest
- Most votes
- Most comments
If you're encountering this error related to Secure Boot updates on an AWS EC2 Windows instance, it's important to note that AWS doesn't allow direct changes to UEFI/BIOS settings, including Secure Boot, on standard EC2 instances. This is because most EC2 instances are virtual machines with limited access to underlying hardware settings.
For Windows 11 instances specifically, AWS automatically enables UEFI Secure Boot using Microsoft keys when importing Windows 11 images. This is done to ensure compatibility and security for Windows 11, which requires UEFI.
If you're experiencing issues with Secure Boot updates or need to modify these settings for specific testing or compatibility reasons, you have a few options:
-
Contact AWS Support: They can provide guidance specific to your EC2 instance and use case.
-
Consider using EC2 bare metal instances: These provide direct access to the underlying hardware, which may allow more control over UEFI/BIOS settings.
-
Review your instance configuration: Ensure your instance is properly configured and up-to-date, as some updates may require specific configurations.
Remember that modifying low-level system settings like Secure Boot can have significant security implications, so proceed with caution and always follow best practices for your specific use case.
Sources
Disable Secure Boot on EC2 Windows 11 to enable Windows Test Mode | AWS re:Post
windows server 2022 - vmware workstation and hyper-v are not compatible | AWS re:Post
Relevant content
- AWS OFFICIALUpdated 2 years ago
