For more information, see Issue with the Hibernate Agent (20 AMIs).Microsoft recently announced that they will not release monthly patches or security updates for the month of February.In general, the AWS Windows AMIs are configured with the default settings used by the Microsoft installation media. For example, the AWS Windows AMIs come with the following software and drivers: After you launch a Windows instance, you are responsible for installing updates on it.You can manually install only the updates that interest you, or you can start from a current AWS Windows AMI and build a new Windows instance.They pickup their first scan at the foreign processing hub before leaving the country. Be sure you check the tracking number though and not just through Amazon if there’s an issue.Complaining to USPS and/or your local postmaster can help sometimes.
AWS provides managed Amazon Machine Images (AMIs) that include various versions and configurations of Windows Server.If you do change VPC/subnet settings, be aware of these internal IP address prefix values and avoid creating a conflict. After the release of the 20 Windows AMIs, we discovered an unquoted path in the configuration of the Amazon EC2 Hibernate Agent.The agent was included in the AMIs for Windows Server 2008 through Windows Server 2016.All February patches and security updates will be included in the March update.Amazon Web Services did not release updated Windows Server AMIs in February. The following features, which were previously available in Enterprise edition only, are now enabled in Standard, Web, and Express editions with SQL Server 2016 SP1: All Windows Server 2008 R2 AMIs for July were removed and rolled back to AMIs dated 20, because of an issue discovered in the AWS PV driver. The August AMI release will include Windows Server 2008 R2 AMIs with the fixed AWS PV driver and July/August Windows updates. If you run the Docker service on Windows Server 2016 AMIs, the service is configured to use a different CIDR value than the default internal IP address prefix value. Windows Server 2016 AMIs use 172.17.0.0/16 to avoid a conflict with the default Amazon EC2 VPC/subnet.After releasing new Windows AMIs, AWS makes the Windows AMIs that are older than three months private within 10 days.After an AMI has been made private, if you look at an instance launched from that AMI in the console, the AMI ID field states, "Cannot load detail for ami-xxxxx.This issue does not impact the AMIs for Windows Server 2003. To be notified when new Windows AMIs are available, see Subscribing to Windows AMI Notifications.To mitigate the issue, you can use one of the following procedures to add the missing quotation marks.If the agent is running, you must also restart the agent.Alternatively, you can terminate any instances that you launched from a 20 Windows AMI and replace them with instances launched using a different AMI.