Product Information

• Product Name: Windows 2016 STIG AMI
• OS Version: Windows 2016
• AMI Name: Win2016-STIG-Dec2021
• AMI ID:ami-0b89c524d681c25b4
• Date Published: December 22, 2021

Image Release Notes

• The image uses the 'ec2-user' user account.

Image Builder Notes

• The image was STIGGED utilizing the Microsoft Windows Server 2016 STIG Benchmark - Ver 2, Rel 1 STIG
• Image is FIPS 140-2 compliant.
• Elastic Network Adapter (ENA) support enabled.

Launch Instructions

• Login to the AWS console AWS Console
• In the upper right-hand corner, locate your current region (first dropdown from the right of the "Support" dropdown menu).
• Select "US East (N Virginia) us east-1". You should now see "N Virginia" as your region.
• Select the "Services" dropdown.
• Locate, then select "EC2", under the "Compute" listing.
• Under "Launch Instance", click "Launch Instance --> Launch Instance".
• In the search bar, type "RGS Windows 2019 STIG".
• Click "Select".
• After ensuring the correct AMI has been selected, click "Continue".
• Select appropriate Instance Type, then click "Configure Instance Details".
• Select appropriate instance details (i.e. subnet, number of instances, etc).
• At the bottom of the page, click the "Advanced Details" dropdown.
• Click "Add Storage".
• After adding the appropriate amount of storage, click "Add Tags".
• After adding the appropriate Tags, click "Configure Security Group".
• If there are no security groups that exist, create a new one, ensuring port 389 (Type RDP) is included.
• Click "Review and Launch".
• After reviewing the instance details, click "Launch".
• This will produce a dialogue box allowing you to create a new shared key, select a current key or proceed without a key. In the case of either creating a new key or selecting a current key, you will need to have that key located on your system in order to access the newly created instance. Proceeding without a key will prevent you from accessing the server via RDP.
• With whatever option is chosen, acknowledge your action by clicking the box just below the key pair questionnaire, then click Launch Instances”.
• This will produce a "Launch Status" page, with the instance ID (ex: i-0e86cb5b9e9eef909). Click on that Instance ID.
• You will be redirected to the status of your recently launched instance. When the instance shows a "2/2" under the "Status check" header, it is ready to be accessed
• Once the instance shows "2/2" under the "Status check" header, click the checkmark next to the instance. This should highlight the "Connect" button.
• Via your connection utility of choice, connect to the server.