Split (1)

train · 107k rows

id stringlengths 8 78	source stringclasses 743 values	chunk_id int64 1 5.05k	text stringlengths 593 49.7k
wickr-ug-010	wickr-ug.pdf	10	Manage your devices enabled for the Wickr client. • Connectivity — Manage Wickr open access. • Appearance — Manage the appearance of the Wickr client. Contacts 35 AWS Wickr User Guide Refer a friend in the Wickr client You can refer a friend to use Wickr in the Wickr client Complete the following steps to invite a friend to use Wickr. 1. 2. 3. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose and then choose Refer a Friend. , In the Invite Someone by Mail window that appears, type the email address of your friend and choose Invite. Support in the Wickr client You can view the support options and resources available for Wickr in the Wickr client Complete the following steps to view the support options and resources. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose and then choose Support. , The multiple support options and resources available for Wickr are displayed on the Support page. Typing indicators in the Wickr client Typing indicators are a useful tool that allows users to see and share when messages are being typed. These indicators can be enabled or disabled at any time and appear as text-based notiﬁcations showing the name of the user who is typing. In case multiple users are typing simultaneously, the notiﬁcation will display "several users are typing" to make it easier to follow the conversation. Refer a friend 36 AWS Wickr Note Typing indicators are supported when users are within an environment with the same domain. Complete the following steps to enable or disable typing indicators. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose and then choose Settings. User Guide , 3. In the Settings pane that appears, choose Privacy & Safety. The Privacy & Safety page displays Enable Typing Indicators, and the option to enable or disable the typing indicator feature. When the typing indicators are disabled, users will not send or receive typing indicator notiﬁcations. Dark mode in the Wickr client Dark mode is an appearance setting that replaces bright backgrounds with dark colors and light text, creating a softer visual experience. You can enable dark mode in the Wickr client. On desktop, to enable dark mode, complete the following steps. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose the (three-dots) menu, and then choose Settings. 3. Choose Appearance. 4. In the Appearance pane, select Dark Theme in the Theme section. Dark mode 37 AWS Wickr Note User Guide Dark mode can be used only if the New User Experience Preview is enabled, which is the default setting. On Android, to enable dark mode, complete the following steps. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose the menu button. 3. At the bottom of the screen, select the sun/moon icon to toggle between light and dark modes. On iOS, the system theme defaults to dark when enabled. Check for updates in the Wickr client You can check for updates to the Wickr client. Complete the following steps to check for updates to the Wickr client. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose and then choose Check For Updates. The prompt that appears will conﬁrm if you are up to date or if a new version of the Wickr client is available. If a new version is available, follow the prompts to download and install it. View current version in the Wickr client You can view the current version of the Wickr client that you are using. Complete the following steps to view your current version of the Wickr client. Check for updates , 38 AWS Wickr 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose User Guide . The bottom of the navigation pane, as shown in the following example, displays the current version of the Wickr client you have installed. ATAK for AWS Wickr The Android Team Awareness Kit (ATAK) is an Android solution used by the US military, state, and governmental agencies that require situational awareness capabilities for mission planning, execution, and incident response. ATAK has a plugin architecture which allows developers to add functionality. It enables users to navigate using GPS and geospatial map data overlaid with real- time situational awareness of ongoing events. In this document, we show
wickr-ug-011	wickr-ug.pdf	11	navigation pane, choose User Guide . The bottom of the navigation pane, as shown in the following example, displays the current version of the Wickr client you have installed. ATAK for AWS Wickr The Android Team Awareness Kit (ATAK) is an Android solution used by the US military, state, and governmental agencies that require situational awareness capabilities for mission planning, execution, and incident response. ATAK has a plugin architecture which allows developers to add functionality. It enables users to navigate using GPS and geospatial map data overlaid with real- time situational awareness of ongoing events. In this document, we show you how to install the Wickr plugin for ATAK on an Android device and pair it with the Wickr client. This allows you to message and collaborate on Wickr without exiting the ATAK application. Topics • Install the Wickr plugin for ATAK • Pair ATAK with Wickr Install the Wickr plugin for ATAK You can install the Wickr plugin for ATAK on an Android device. Complete the following procedure to install the Wickr plugin for ATAK. 1. Go to the Google Play store, and install the Wickr for ATAK plugin. ATAK 39 AWS Wickr 2. Open the ATAK application on your Android device. 3. In the ATAK application, choose the menu icon ( at the top-right of the screen, and choose Plugins. User Guide ) 4. Choose Import. 5. On the Select Import Type pop-up, choose Local SD and navigate to where you saved the Wickr plugin for ATAK .apk ﬁle. Install 40 AWS Wickr User Guide 6. Choose the plugin ﬁle and follow the prompts to install it. Note If you are asked to send the plugin ﬁle for scanning, choose No. 7. The ATAK application will ask if you would like to load the plugin. Choose OK. The Wickr plugin for ATAK is now installed. Continue to the following Pair ATAK with Wickr section to ﬁnish the process. Pair ATAK with Wickr You can pair the ATAK application with Wickr after you successfully installed the Wickr plugin for ATAK. Complete the following procedure to pair the ATAK application with Wickr after you successfully installed the Wickr plugin for ATAK. 1. In the ATAK application, choose the menu icon at the top-right of the screen, and choose Wickr Plugin. Pair 41 AWS Wickr 2. Choose Pair Wickr. User Guide A notiﬁcation prompt will appear asking you to review permissions for the Wickr plugin for ATAK. If the notiﬁcation prompt doesn't appear, open the Wickr client and go to Settings, then Connected Apps. You should see the plugin under the Pending section of the screen as shown in the following example. Pair 42 AWS Wickr User Guide 3. Choose Approve to pair. Pair 43 AWS Wickr User Guide 4. Choose Open Wickr ATAK Plugin button to go back to the ATAK application. Pair 44 AWS Wickr User Guide You have now successfully paired the ATAK plugin and Wickr, and can use the plugin to send messages and collaborate using Wickr without exiting the ATAK application. Markdown (preview) for AWS Wickr Wickr has launched Markdown as a preview feature. Markdown is a lightweight markup language used to format plain text. Using markdown can help improve the readability and detail of your messages. Markdown 45 AWS Wickr User Guide You can either use the What You See Is What You Get (WYSIWYG) formatting toolbar directly within the message ﬁeld or use Markdown to add options like bold text, italics, and list. Formatting toolbar To use the formatting toolbar, either click on the Aa icon for text formatting or highlight the text you wish to format and select the desired option. You can add diﬀerent formatting options to the same text and preview the ﬁnal message before sending it. Markdown syntax You can use Markdown syntax elements to format your messages. Formatting Description Bold Italic Add an asterisk before and after the word. bold Add one underscore before and after the word. _italic_ Strikethrough Add one tildes before and after the word. ~strikethrough~ Code Add a back-quote before and after your code. Blockquote Add a bracket in front of your text. `your code` Code block > your text Add three back-quotes before and after your block of code. ```this is a block of code``` Markdown 46 AWS Wickr Formatting Ordered list User Guide Description Add line items with numbers, starting with 1, followed by a period. 1. item 1 2. item 2 Bullet list Add an asterisk followed by a space. Headings Hyperlink * item 1 * item 2 Add number signs in front of a word. # Heading Add square brackets with link text, followed by the URL in parentheses. [Amazon](https://www.amazon.com) Markdown is enabled by default. To disable it, complete the following procedure. On desktop: 1. 2. Sign in to the Wickr
wickr-ug-012	wickr-ug.pdf	12	after your block of code. ```this is a block of code``` Markdown 46 AWS Wickr Formatting Ordered list User Guide Description Add line items with numbers, starting with 1, followed by a period. 1. item 1 2. item 2 Bullet list Add an asterisk followed by a space. Headings Hyperlink * item 1 * item 2 Add number signs in front of a word. # Heading Add square brackets with link text, followed by the URL in parentheses. [Amazon](https://www.amazon.com) Markdown is enabled by default. To disable it, complete the following procedure. On desktop: 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose the menu icon ( and then choose Settings. 3. Choose Appearance. ), 4. In the Appearance pane that appears, turn oﬀ the toggle in the New User Experience Preview section to disable. On mobile: 1. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. Markdown 47 AWS Wickr 2. In the navigation pane, choose the menu icon ( and then choose Settings. 3. Choose Appearance. User Guide ), 4. In the Appearance pane that appears, turn oﬀ the toggle in the Rich Text Editor Preview section to disable. Markdown 48 AWS Wickr User Guide AWS Wickr Data retention AWS Wickr Data retention can retain all conversations in network. This includes direct messages and conversations in Groups or Rooms between in-network (internal) members and those with other teams (external) with whom your network is federated. Data retention is only available to AWS Wickr Premium plan customers and enterprise customers who opt in for data retention. For more information about the Premium plan, see Wickr Pricing. When your network administrator activates data retention for your network, all messages and ﬁles that you share in your network are retained in accordance with your organization's compliance policies. You will see a Data Retention Turned On window, informing you of this new setting. You will also see a one-time control message in any Direct Message, Room or Group that has members from another network (external members). The control message indicates that all messages in the conversation can be retained as per external organizations' data retention policy. This doesn't expose or indicate the status of any network’s data retention policy. 49 AWS Wickr User Guide 50 AWS Wickr User Guide AWS Wickr Guest users The Wickr guest user feature allows individual guest users to sign in to the Wickr client and collaborate with Wickr network users. Important The guest users feature must be enabled for the Wickr network. If you are a guest user and experience diﬃculties communicating with users who are registered to a Wickr network, then the guest users feature might not be enabled for the Wickr network. Users who are registered to the Wickr network should get in touch with their Wickr administrator to determine if the guest users feature is enabled. Wickr administrators see Guest users in the Wickr Administration Guide. Topics • Guest user account limitations • Sign up for a guest account in the Wickr client • Close a guest user account in the Wickr client • Report a user in the Wickr client Guest user account limitations The following limitations apply to guest user accounts: • Guest users can’t initiate communication with Wickr network users. Wickr network users can start communication with guest users and add guest users to direct messages, rooms, or groups to initiate a secure conversation. Guest users can share their registered email address to let Wickr network users know how to ﬁnd them on Wickr. Note Wickr network users can ﬁnd guest users when writing a direct message, creating a room, or a group message. The dialog box when writing a direct message, creating a room, or group message allows you to search for network and guest users. Guest user account limitations 51 AWS Wickr User Guide • Guest users can't create rooms or groups. Wickr network users can create a room or group, and add guests and external users from other Wickr networks (if federation is enabled). After that, guest users can send messages in the room or group, view members, and start a direct message. • Guest users can’t be moderators or add members in Wickr rooms and groups. • Guest users can communicate with each other only when the guest users are in the same room as a network user. • A guest user can continue communicating in the Wickr network, only if a network user has communicated with the guest within the last 90 days. • Message expiration settings are limited to a maximum period of 30 days for guest users. For more information, see Set message expiration and burn timers. Sign up for a guest account in
wickr-ug-013	wickr-ug.pdf	13	and start a direct message. • Guest users can’t be moderators or add members in Wickr rooms and groups. • Guest users can communicate with each other only when the guest users are in the same room as a network user. • A guest user can continue communicating in the Wickr network, only if a network user has communicated with the guest within the last 90 days. • Message expiration settings are limited to a maximum period of 30 days for guest users. For more information, see Set message expiration and burn timers. Sign up for a guest account in the Wickr client You can sign up for a guest user account on AWS Wickr. Complete the following procedure to sign up for Wickr as a guest user. 1. Download and install the Wickr client. For more information, see Download and install the Wickr client. 2. Open the Wickr client. 3. At the bottom of the sign in screen, choose Don't have an account? Sign Up. Sign up account 52 AWS Wickr User Guide 4. On the Get started with Wickr page, choose Create a personal guest account. 5. On the Sign up with a new account page, enter your ﬁrst name, last name, email address, and password. 6. Choose Sign up. Wickr will send you a veriﬁcation email after you sign in. You can continue to the next step in this procedure. However, be aware that the veriﬁcation email can take up to 30 minutes to reach your inbox. Don't choose Send a new link until at least 30 minutes have passed. Keep the Wickr client open while waiting for the veriﬁcation email. Sign up account 53 AWS Wickr User Guide 7. In the Wickr veriﬁcation email, choose Verify Email. 8. Choose Continue and sign in to the Wickr client. 9. The Wickr client will display your Master Recovery Key (MRK). You can use the MRK to sign in to Wickr on a diﬀerent device than the one you're currently using. Save your MRK in a safe location and choose Next. Note The master recovery key is blurred in the following example. Sign up account 54 AWS Wickr User Guide You should now be signed in to the Wickr client. You will receive a message from the Wickrbot showing your guest account limitations. At this point, Wickr network users can add you to their conversations. However, guest user access must be enabled for their Wickr network. If you have diﬃculties communicating with other Wickr users in a Wickr network, those users should contact their Wickr administrator to troubleshoot the problem. Sign up account 55 AWS Wickr Note User Guide If you are a guest user, you can become a Wickr network user by creating a network. For more information, see Getting started with AWS Wickr in the AWS Wickr Administration Guide. Close a guest user account in the Wickr client You can close a guest user account on AWS Wickr. Complete the following procedure to close a guest user account. 1. 2. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, choose the menu icon ( and then choose Support. 3. Choose Close Account. ), 4. In the Close Your Account pane that appears, choose one of the following options (optional): • It's missing important features • I need help to better use Wickr • I'm not satisﬁed with the product quality • I have privacy/security concerns • Other 5. Choose Continue. 6. 7. In the Close Your Account pane that appears, choose Close Account. In the next Close Your Account pane that appears, enter your password in the text ﬁeld. 8. Choose Sign in. 9. In the pop up window, choose Close Account. Report a user in the Wickr client If you encounter any behavior that violates our Terms of Service we ask that you report it to us. Close account 56 AWS Wickr User Guide Complete the following procedure to report a user. 1. 2. 3. 4. 5. Sign in to the Wickr client. For more information, see Sign in to the Wickr client. In the navigation pane, ﬁnd and select the name of the user who you want to report. Select the information icon ( in the message window to view contact details. In the Contact Details pane, choose Report to report the user. In the Why are you reporting this? pane, choose one of the following options: ) • Spam/fraud • Child exploitation/abuse • Harassment/bullying/threats • Pretending to be someone else • Other 6. In the New Message window, you can provide additional information about your report a user request by emailing Wickr Abuse. Report user 57 AWS Wickr User Guide AWS Wickr Device sync You can sync existing data from your original device
wickr-ug-014	wickr-ug.pdf	14	who you want to report. Select the information icon ( in the message window to view contact details. In the Contact Details pane, choose Report to report the user. In the Why are you reporting this? pane, choose one of the following options: ) • Spam/fraud • Child exploitation/abuse • Harassment/bullying/threats • Pretending to be someone else • Other 6. In the New Message window, you can provide additional information about your report a user request by emailing Wickr Abuse. Report user 57 AWS Wickr User Guide AWS Wickr Device sync You can sync existing data from your original device to a new device. Note You must have both devices available and already have a Wickr account, and the AWS Wickr app installed on your original device. To sync your device using a QR code, complete the following procedure. Note You must have a camera on your original device to sync using a QR code. 1. On your new device, sign in to the Wickr client. 2. On the Transfer account and messages page, choose Scan QR code. A QR code page appears. 3. Open the Wickr app on your original device. 4. In the notiﬁcation window, choose Approve. 5. Hold the QR code on the new device in front of the camera of the original device. The Wickr app will automatically begin to sync your existing data to your new device. 6. When the sync is complete, a Welcome to AWS Wickr window appears on your new device. To sync your device manually entering a code, complete the following procedure. 1. On your new device, sign in to the Wickr client. 2. On the Transfer account and messages page, choose Enter code. A window with a code appears. 3. Open the Wickr app on your original device. 4. In the notiﬁcation window, choose Approve. 58 AWS Wickr User Guide 5. On the Enter Code Manually page, enter the ﬁrst six characters of the code displayed on your new device. Conﬁrm that the codes match visually, and then choose Continue. The Wickr app will automatically begin to sync your existing data to your new device. 6. When the sync is complete, a Welcome to AWS Wickr window appears on your new device. 59 AWS Wickr User Guide Document history for AWS Wickr The following table describes the documentation releases for Wickr. Change Description Date File management Markdown Device sync and Typing indicators Guest users February 4, 2025 February 12, 2024 December 18, 2023 November 8, 2023 Users and moderators can upload, view, delete, and organize ﬁles in group and room conversations. For more information, see Manage ﬁles in the Wickr client. Markdown is enabled by default, allowing users to improve message clarity and detail. For more information, see Markdown (preview). Users have the option to sync their existing data from their original device to a new device. For more information, see Device sync. Additionally, users can see and share when messages are being typed with typing indicators. For more information, see Typing indicators. Guest users have the option to delete their accounts and can also report other Wickr users. For more information, see Guest users. 60 AWS Wickr Global Federation Data retention Guest users (preview) Emoji reactions User Guide September 29, 2023 July 31, 2023 May 31, 2023 March 14, 2023 Wickr networks now have the ability to communicate across AWS Regions. Data retention is available to both internal and external communication in a Wickr network. For more informati on, see Data retention. Guest users can sign in to the Wickr client and collaborate with Wickr network users. For more information, see Guest users (preview). Users can now add emoji reactions to messages in the Wickr client. For more information, see Use emojis. Initial release Initial release of the Wickr User Guide November 28, 2022 61 AWS Wickr User Guide Release notes for AWS Wickr To help you keep track of the ongoing updates and improvements to Wickr, we publish release notices that describe recent changes. April 2025 • Enhancements • Wickr Open Access (WOA) performance and stability improvements. • Starting with the next client release (6.54), Wickr will discontinue updates and support for the macOS client when running version 11 (Big Sur). It's recommended that you upgrade to version 12 (Monterey) or above. February 2025 • Enhancements • File management is now available. For more information, see Manage ﬁles in the Wickr client. February 2024 • Enhancements • Markdown is now available. For more information, see Markdown (preview) for AWS Wickr. December 2023 • Enhancements • Wickr supports device sync. For more information, see AWS Wickr Device sync. • Wickr supports typing indicators. For more information, see Typing indicators in the Wickr client. November 2023 • Enhancements April 2025 62 AWS Wickr User Guide • Added support for guest
wickr-ug-015	wickr-ug.pdf	15	11 (Big Sur). It's recommended that you upgrade to version 12 (Monterey) or above. February 2025 • Enhancements • File management is now available. For more information, see Manage ﬁles in the Wickr client. February 2024 • Enhancements • Markdown is now available. For more information, see Markdown (preview) for AWS Wickr. December 2023 • Enhancements • Wickr supports device sync. For more information, see AWS Wickr Device sync. • Wickr supports typing indicators. For more information, see Typing indicators in the Wickr client. November 2023 • Enhancements April 2025 62 AWS Wickr User Guide • Added support for guest users. Support includes: • Ability to report abuse by other Wickr users. • The option to delete their accounts. For more information, see AWS Wickr Guest users. September 2023 • Enhancements • Added support for multi-region federation. July 2023 • Enhancements • Data retention is now available. For more information, see AWS Wickr Data retention. May 2023 • Enhancements • Added support for guest users. For more information, see AWS Wickr Guest users. March 2023 • Enhancements • Added support for emoji reactions in messages. For more information, see Emojis in the Wickr client. February 2023 • Enhancements • Added support for the Wickr plugin for Android Tactical Assault Kit (ATAK). For more information, see ATAK for AWS Wickr. September 2023 63 AWS Wickr January 2023 • Enhancements User Guide • Improved functionality and tools for moderating content that might violate AWS Terms of Use in the Android client. This can be done through blocking, muting, and reporting users. • Updated translations for the Android client. January 2023 64
windows-ami-reference-001	windows-ami-reference.pdf	1	Reference AWS Windows AMIs Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. AWS Windows AMIs Reference AWS Windows AMIs: Reference Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon. AWS Windows AMIs Table of Contents Reference AWS Windows AMIs ......................................................................................................................... 1 Specialized AWS Windows AMIs ................................................................................................................ 1 STIG Hardened AMIs ............................................................................................................................... 2 How Amazon creates AWS Windows AMIs ............................................................................................ 15 Windows Server installation media .................................................................................................. 15 What to expect from an oﬃcial AWS Windows AMI ..................................................................... 15 Validation of software on AWS AMIs ............................................................................................... 16 How Amazon decides which AWS Windows AMIs to oﬀer ........................................................... 17 Patches, security updates, and AMI IDs ........................................................................................... 17 Ports and Protocols ................................................................................................................................... 18 AllJoyn Router ....................................................................................................................................... 19 Cast to Device ........................................................................................................................................ 20 Core Networking ................................................................................................................................... 23 Delivery Optimization .......................................................................................................................... 69 Diag Track ............................................................................................................................................... 70 DIAL Protocol Server ............................................................................................................................ 70 File and Printer Sharing ...................................................................................................................... 71 File Server Remote Management ...................................................................................................... 76 ICMP v4 All ............................................................................................................................................. 76 Microsoft Edge ....................................................................................................................................... 77 Microsoft Media Foundation Network Source ................................................................................ 77 Multicast .................................................................................................................................................. 78 Remote Desktop .................................................................................................................................... 78 WindowsDevice Management ............................................................................................................ 80 WindowsFeature Experience Pack ..................................................................................................... 83 WindowsFirewall Remote Management ........................................................................................... 83 WindowsRemote Management .......................................................................................................... 83 Updates applied for AWS Windows AMIs .............................................................................................. 84 Changes in Windows Server AMIs by OS version ................................................................................ 88 AWS Windows AMI version history ......................................................................................................... 90 Monthly AMI updates for 2025 (to date) ........................................................................................ 90 Subscribe to AWS Windows AMI notiﬁcations ........................................................................... 212 Security ........................................................................................................................................ 214 Document history ........................................................................................................................ 215 iii AWS Windows AMIs Reference AWS Windows AMI reference AWS provides a set of publicly available Amazon Machine Images (AMIs) that contain software conﬁgurations speciﬁc to the Windows platform. You can quickly start building and deploying your applications with Amazon EC2 by using these AMIs. First choose the AMI that meets your speciﬁc requirements, and then launch an instance using that AMI. You retrieve the password for the administrator account and then log in to the instance using Remote Desktop Connection, just as you would with any other Windows Server. In general, the AWS Windows AMIs are conﬁgured with the default settings used by the Microsoft installation media. However, Amazon does apply some customizations. For example, the AWS Windows AMIs come with the following software and drivers: • EC2Launch v2 (Windows Server 2022 and 2025) • EC2Launch v1 (Windows Server 2016 and 2019) • EC2Conﬁg (through Windows Server 2012 R2) • AWS Systems Manager • AWS CloudFormation • AWS Tools for Windows PowerShell • Network drivers (SRIOV, ENA, Citrix PV) • Storage drivers (NVMe, AWS PV, Citrix PV) • Graphics drivers (NVidia GPU, Elastic GPU) With the Windows fast launch feature, you can conﬁgure pre-provisioned snapshots to launch instances up to 65% faster. For more information, see Conﬁgure Windows fast launch for your Windows Server AMI in the Amazon EC2 User Guide. To view changes to each release of the AWS Windows AMIs, including SQL Server updates, see the AWS Windows AMI version history. Specialized AWS Windows AMIs You can use specialized AWS Windows AMIs to create instances for your database and compliance hardening use cases as follows. Specialized AWS Windows AMIs 1 AWS Windows AMIs SQL Server AMIs Reference Some AWS Windows AMIs include an edition of Microsoft SQL Server (SQL Enterprise Edition, SQL Server Standard, SQL Server Express, or SQL Server Web). Launching an instance from a Windows AMI with Microsoft SQL Server enables you to run the instance as a database server. Alternatively, you can launch an instance from any Windows AMI and then install the database software that you need on the instance. To discover available SQL Server license-included AMIs, see Find a SQL Server license-included AMI in the Microsoft SQL Server on Amazon EC2 User Guide. STIG Hardened AMIs STIG Hardened EC2 Windows Server AMIs are pre-conﬁgured with over 160 required security settings to help ensure that the instances that you launch follow the latest guidelines for STIG compliance. For more information, see STIG Hardened AWS Windows Server AMIs. STIG Hardened AWS Windows Server AMIs Security Technical Implementation Guides (STIGs) are the conﬁguration standards created by the Defense Information Systems Agency (DISA) to secure information systems and software. DISA documents three levels of compliance risk, known as categories: • Category I — The highest level of risk. It covers the most severe risks, and includes any vulnerability that can result in a loss of conﬁdentiality, availability, or integrity. • Category II
windows-ami-reference-002	windows-ami-reference.pdf	2	security settings to help ensure that the instances that you launch follow the latest guidelines for STIG compliance. For more information, see STIG Hardened AWS Windows Server AMIs. STIG Hardened AWS Windows Server AMIs Security Technical Implementation Guides (STIGs) are the conﬁguration standards created by the Defense Information Systems Agency (DISA) to secure information systems and software. DISA documents three levels of compliance risk, known as categories: • Category I — The highest level of risk. It covers the most severe risks, and includes any vulnerability that can result in a loss of conﬁdentiality, availability, or integrity. • Category II — Medium risk. • Category III — Low risk. Each compliance level includes all STIG settings from lower levels. This means that the highest level includes all applicable settings from all levels. To ensure that your systems are compliant with STIG standards, you must install, conﬁgure, and test a variety of security settings. STIG Hardened EC2 Windows Server AMIs are pre-conﬁgured with over 160 required security settings. Amazon EC2 supports the following operating systems for STIG Hardened AMIs: • Windows Server 2022 • Windows Server 2019 STIG Hardened AMIs 2 AWS Windows AMIs • Windows Server 2016 • Windows Server 2012 R2 Reference The STIG Hardened AMIs include updated Department of Defense (DoD) certiﬁcates to help you get started and achieve STIG compliance. STIG Hardened AMIs are available in all commercial AWS and GovCloud (US) Regions. You can launch instances from these AMIs directly from the Amazon EC2 console. They are billed using standard Windowspricing. There are no additional charges for using STIG Hardened AMIs. You can ﬁnd the STIG Hardened EC2 Windows Server AMIs in the Community AMIs when you launch an instance, as follows. Launch an EC2 instance with a STIG Hardened Windows Server AMI 1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/. 2. Choose Instances from the navigation pane. This opens a list of your EC2 instances in the current AWS Region. 3. Choose Launch instances from the upper right corner above the list. This opens the Launch an instance page. 4. 5. To ﬁnd a STIG Hardened AMI, choose Browse more AMIs on the right side of the Application and OS Images (Amazon Machine Image) section. This displays an advanced AMI search. Select the Community AMIs tab, and enter part or all of one of the following name patterns in the search bar. Our AMIs indicate that they are "provided by Amazon." Note The date suﬃx for the AMI (YYYY.MM.DD) is the date when the latest version was created. You can search for the version without the date suﬃx. Name patterns for STIG Hardened AMI names • Windows_Server-2022-English-STIG-Full-YYYY.MM.DD • Windows_Server-2022-English-STIG-Core-YYYY.MM.DD • Windows_Server-2019-English-STIG-Full-YYYY.MM.DD • Windows_Server-2019-English-STIG-Core-YYYY.MM.DD STIG Hardened AMIs 3 AWS Windows AMIs Reference • Windows_Server-2016-English-STIG-Full-YYYY.MM.DD • Windows_Server-2016-English-STIG-Core-YYYY.MM.DD • Windows_Server-2012-R2-English-STIG-Full-YYYY.MM.DD • Windows_Server-2012-R2-English-STIG-Core-YYYY.MM.DD The following sections list the STIG settings that Amazon applies to WindowsOperating Systems and components. Topics • Core and base operating systems • Microsoft .NET Framework 4.0 STIG Version 2 Release 2 • WindowsFirewall STIG Version 2 Release 2 • Internet Explorer (IE) 11 STIG Version 2 Release 5 • Microsoft Edge STIG Version 2 Release 2 • Microsoft Defender STIG Version 2 Release 4 • Version history Core and base operating systems STIG Hardened EC2 AMIs are designed for use as standalone servers, and have the highest level of STIG settings applied. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. Windows Server 2022 STIG Version 2 Release 2 This release includes the following STIG settings for Windows operating systems: V-254293, V-254352, V-254353, V-254354, V-254374, V-254378, V-254381, V-254446, V-254465, V-254466, V-254467, V-254469, V-254474, V-254475, V-254500, V-254247, V-254265, V-254269, V-254270, V-254271, V-254272, V-254273, V-254274, V-254276, STIG Hardened AMIs 4 AWS Windows AMIs Reference V-254277, V-254278, V-254285, V-254286, V-254287, V-254288, V-254289, V-254290, V-254291, V-254292, V-254300, V-254301, V-254302, V-254303, V-254304, V-254305, V-254306, V-254307, V-254308, V-254309, V-254310, V-254311, V-254312, V-254313, V-254314, V-254315, V-254316, V-254317, V-254318, V-254319, V-254320, V-254321, V-254322, V-254323, V-254324, V-254325, V-254326, V-254327, V-254328, V-254329, V-254330, V-254331, V-254332, V-254333, V-254334, V-254339, V-254341, V-254342, V-254344, V-254345, V-254346, V-254347, V-254348, V-254349, V-254350, V-254355, V-254356, V-254356, V-254358, V-254359, V-254360, V-254361, V-254362, V-254364, V-254365, V-254366, V-254367, V-254368, V-254369, V-254370, V-254371, V-254372, V-254373, V-254375, V-254376, V-254377, V-254379, V-254380, V-254382, V-254383, V-254384, V-254431, V-254432, V-254433, V-254434, V-254435, V-254436, V-254438, V-254439, V-254442, V-254443, V-254444, V-254445, V-254449, V-254450, V-254451, V-254452, V-254453, V-254454, V-254455, V-254456, V-254459, V-254460, V-254461, V-254462, V-254463, V-254464, V-254468, V-254470, V-254471, V-254472, V-254473, V-254476, V-254477, V-254478, V-254479, V-254480, V-254482,
windows-ami-reference-003	windows-ami-reference.pdf	3	V-254308, V-254309, V-254310, V-254311, V-254312, V-254313, V-254314, V-254315, V-254316, V-254317, V-254318, V-254319, V-254320, V-254321, V-254322, V-254323, V-254324, V-254325, V-254326, V-254327, V-254328, V-254329, V-254330, V-254331, V-254332, V-254333, V-254334, V-254339, V-254341, V-254342, V-254344, V-254345, V-254346, V-254347, V-254348, V-254349, V-254350, V-254355, V-254356, V-254356, V-254358, V-254359, V-254360, V-254361, V-254362, V-254364, V-254365, V-254366, V-254367, V-254368, V-254369, V-254370, V-254371, V-254372, V-254373, V-254375, V-254376, V-254377, V-254379, V-254380, V-254382, V-254383, V-254384, V-254431, V-254432, V-254433, V-254434, V-254435, V-254436, V-254438, V-254439, V-254442, V-254443, V-254444, V-254445, V-254449, V-254450, V-254451, V-254452, V-254453, V-254454, V-254455, V-254456, V-254459, V-254460, V-254461, V-254462, V-254463, V-254464, V-254468, V-254470, V-254471, V-254472, V-254473, V-254476, V-254477, V-254478, V-254479, V-254480, V-254482, V-254483, V-254484, V-254485, V-254486, V-254487, V-254488, V-254489, V-254490, V-254493, V-254494, V-254495, V-254497, V-254499, V-254501, V-254502, V-254503, V-254504, V-254505, V-254507, V-254508, V-254509, V-254510, V-254511, V-254512, V-254335, V-254336, V-254337, V-254338, V-254351, V-254357, V-254363, and V-254481 Windows Server 2019 STIG Version 3 Release 2 This release includes the following STIG settings for Windows operating systems: V-254293, V-254352, V-254353, V-254354, V-254374, V-254378, V-254381, V-254446, V-254465, V-254466, V-254467, V-254469, V-254474, V-254475, V-254500, V-205625, V-205626, V-205627, V-205629, V-205630, V-205633, V-205634, V-205635, V-205636, V-205637, V-205638, V-205639, V-205643, V-205644, V-205648, V-205649, V-205650, V-205651, V-205652, V-205655, V-205656, V-205659, V-205660, V-205662, V-205671, V-205672, V-205673, V-205675, V-205676, V-205678, V-205679, V-205680, V-205681, V-205682, V-205683, V-205684, V-205685, V-205686, V-205687, V-205688, V-205689, V-205690, V-205692, V-205693, V-205694, V-205697, V-205698, V-205708, V-205709, V-205712, V-205714, V-205716, V-205717, V-205718, V-205719, V-205720, V-205722, V-205729, V-205730, V-205733, V-205747, V-205751, V-205752, V-205754, V-205756, V-205758, V-205759, V-205760, V-205761, V-205762, V-205764, V-205765, V-205766, V-205767, V-205768, V-205769, V-205770, V-205771, V-205772, V-205773, V-205774, V-205775, V-205776, V-205777, V-205778, V-205779, V-205780, V-205781, V-205782, V-205783, V-205784, V-205795, V-205796, V-205797, V-205798, V-205801, V-205808, STIG Hardened AMIs 5 AWS Windows AMIs Reference V-205809, V-205810, V-205811, V-205812, V-205813, V-205814, V-205815, V-205816, V-205817, V-205821, V-205822, V-205823, V-205824, V-205825, V-205826, V-205827, V-205828, V-205830, V-205832, V-205833, V-205834, V-205835, V-205836, V-205837, V-205838, V-205839, V-205840, V-205841, V-205842, V-205861, V-205863, V-205865, V-205866, V-205867, V-205868, V-205869, V-205872, V-205873, V-205874, V-205911, V-205912, V-205915, V-205916, V-205917, V-205918, V-205920, V-205921, V-205922, V-205924, V-205925, V-236001, V-257503, V-205691, V-205819, V-205858, V-205859, V-205860, V-205870, V-205871, and V-205923 Windows Server 2016 STIG Version 2 Release 9 This release includes the following STIG settings for Windows operating systems: V-224874, V-224932, V-224933, V-224934, V-224954, V-224958, V-224961, V-225025, V-225044, V-225045, V-225046, V-225048, V-225053, V-225054, V-225079, V-224850, V-224852, V-224853, V-224854, V-224855, V-224856, V-224857, V-224858, V-224859, V-224866, V-224867, V-224868, V-224869, V-224870, V-224871, V-224872, V-224873, V-224881, V-224882, V-224883, V-224884, V-224885, V-224886, V-224887, V-224888, V-224889, V-224890, V-224891, V-224892, V-224893, V-224894, V-224895, V-224896, V-224897, V-224898, V-224899, V-224900, V-224901, V-224902, V-224903, V-224904, V-224905, V-224906, V-224907, V-224908, V-224909, V-224910, V-224911, V-224912, V-224913, V-224914, V-224915, V-224920, V-224922, V-224924, V-224925, V-224926, V-224927, V-224928, V-224929, V-224930, V-224935, V-224936, V-224937, V-224938, V-224939, V-224940, V-224941, V-224943, V-224944, V-224945, V-224946, V-224947, V-224948, V-224949, V-224951, V-224952, V-224953, V-224955, V-224956, V-224957, V-224959, V-224960, V-224962, V-224963, V-225010, V-225013, V-225014, V-225015, V-225016, V-225017, V-225018, V-225019, V-225021, V-225022, V-225023, V-225024, V-225028, V-225029, V-225030, V-225031, V-225032, V-225033, V-225034, V-225035, V-225038, V-225039, V-225040, V-225041, V-225042, V-225043, V-225047, V-225049, V-225050, V-225051, V-225052, V-225055, V-225056, V-225057, V-225058, V-225059, V-225061, V-225062, V-225063, V-225064, V-225065, V-225066, V-225067, V-225068, V-225069, V-225072, V-225073, V-225074, V-225076, V-225078, V-225080, V-225081, V-225082, V-225083, V-225084, V-225086, V-225087, V-225088, V-225089, V-225092, V-225093, V-236000, V-257502, V-224916, V-224917, V-224918, V-224919, V-224931, V-224942, and V-225060 Windows Server 2012 R2 MS STIG Version 3 Release 5 This release includes the following STIG settings for Windows operating systems: STIG Hardened AMIs 6 AWS Windows AMIs Reference V-225574, V-225573, V-225572, V-225571, V-225570, V-225569, V-225568, V-225567, V-225566, V-225565, V-225564, V-225563, V-225562, V-225561, V-225560, V-225559, V-225558, V-225557, V-225556, V-225555, V-225554, V-225553, V-225552, V-225551, V-225550, V-225549, V-225548, V-225547, V-225546, V-225545, V-225544, V-225543, V-225542, V-225541, V-225540, V-225539, V-225538, V-225537, V-225536, V-225535, V-225534, V-225533, V-225532, V-225531, V-225530, V-225529, V-225528, V-225527, V-225526, V-225525, V-225524, V-225523, V-225522, V-225521, V-225520, V-225519, V-225518, V-225517, V-225516, V-225515, V-225514, V-225513, V-225512, V-225511, V-225510, V-225509, V-225508, V-225507, V-225506, V-225505, V-225504, V-225503, V-225502, V-225501, V-225500, V-225499, V-225498, V-225497, V-225496, V-225495, V-225494, V-225493, V-225492, V-225491, V-225490, V-225489, V-225488, V-225487, V-225486, V-225485, V-225484, V-225483, V-225482, V-225481, V-225480, V-225479, V-225478, V-225477, V-225476, V-225475, V-225474, V-225473, V-225472, V-225471, V-225470, V-225469, V-225468, V-225467, V-225466, V-225465, V-225464, V-225463, V-225462, V-225461, V-225460, V-225459, V-225458, V-225457, V-225456, V-225455, V-225454, V-225453, V-225452, V-225451, V-225450, V-225449, V-225448, V-225447, V-225446, V-225445, V-225444, V-225443, V-225442, V-225441, V-225440, V-225439, V-225438, V-225437, V-225436, V-225435, V-225434, V-225433, V-225432, V-225431, V-225430, V-225429, V-225428, V-225427, V-225426, V-225425, V-225424, V-225423, V-225422, V-225421, V-225420, V-225419, V-225418, V-225417, V-225416, V-225415, V-225414, V-225413, V-225412, V-225411, V-225410, V-225409, V-225408, V-225407, V-225406, V-225405, V-225404, V-225402, V-225401, V-225400, V-225399, V-225398, V-225397, V-225396, V-225395, V-225394, V-225393, V-225392, V-225391, V-225390, V-225389, V-225388, V-225387, V-225386, V-225385, V-225384, V-225383, V-225382, V-225381, V-225380, V-225379, V-225378, V-225377, V-225376, V-225375, V-225374, V-225373, V-225372, V-225371, V-225370, V-225369, V-225368, V-225367, V-225366, V-225365, V-225364, V-225363, V-225362, V-225361, V-225360, V-225359, V-225358, V-225357, V-225356, V-225355, V-225354, V-225353, V-225352, V-225351, V-225350, V-225349, V-225348, V-225347, V-225346, V-225345, V-225344, V-225343, V-225342, V-225341, V-225340, V-225339, V-225338, V-225337, V-225336, V-225335, V-225334, V-225333, V-225332, V-225331, V-225330, V-225329, V-225328, V-225327, V-225326,
windows-ami-reference-004	windows-ami-reference.pdf	4	V-225426, V-225425, V-225424, V-225423, V-225422, V-225421, V-225420, V-225419, V-225418, V-225417, V-225416, V-225415, V-225414, V-225413, V-225412, V-225411, V-225410, V-225409, V-225408, V-225407, V-225406, V-225405, V-225404, V-225402, V-225401, V-225400, V-225399, V-225398, V-225397, V-225396, V-225395, V-225394, V-225393, V-225392, V-225391, V-225390, V-225389, V-225388, V-225387, V-225386, V-225385, V-225384, V-225383, V-225382, V-225381, V-225380, V-225379, V-225378, V-225377, V-225376, V-225375, V-225374, V-225373, V-225372, V-225371, V-225370, V-225369, V-225368, V-225367, V-225366, V-225365, V-225364, V-225363, V-225362, V-225361, V-225360, V-225359, V-225358, V-225357, V-225356, V-225355, V-225354, V-225353, V-225352, V-225351, V-225350, V-225349, V-225348, V-225347, V-225346, V-225345, V-225344, V-225343, V-225342, V-225341, V-225340, V-225339, V-225338, V-225337, V-225336, V-225335, V-225334, V-225333, V-225332, V-225331, V-225330, V-225329, V-225328, V-225327, V-225326, V-225325, V-225324, V-225319, V-225318, V-225317, V-225316, V-225315, V-225314, V-225313, V-225312, V-225311, V-225310, V-225309, V-225308, V-225307, V-225306, V-225305, V-225304, V-225303, V-225302, V-225301, V-225300, V-225299, V-225298, V-225297, V-225296, V-225295, V-225294, V-225293, V-225292, V-225291, V-225290, V-225289, V-225288, V-225287, V-225286, V-225285, V-225284, V-225283, V-225282, STIG Hardened AMIs 7 AWS Windows AMIs Reference V-225281, V-225280, V-225279, V-225278, V-225277, V-225276, V-225275, V-225274, V-225273, V-225272, V-225271, V-225270, V-225269, V-225268, V-225267, V-225266, V-225265, V-225264, V-225263, V-225262, V-225261, V-225260, V-225259, V-225258, V-225257, V-225256, V-225255, V-225254, V-225253, V-225252, V-225251, V-225250, V-225249, V-225248, V-225247, V-225246, V-225245, V-225244, V-225243, V-225242, V-225241, V-225240, and V-225239 Microsoft .NET Framework 4.0 STIG Version 2 Release 2 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. .NET Framework on Windows Server 2019, 2016, and 2012 R2 MS V-225238 WindowsFirewall STIG Version 2 Release 2 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. WindowsFirewall on Windows Server 2022, 2019, 2016, and 2012 R2 MS V-241992, V-241997, V-242002, V-241989, V-241990, V-241991, V-241993, V-241993, V-241998, V-241998, V-242003, V-242003, V-241994, V-241995, V-241996, V-241999, V-242000, V-242001, V-242006, V-242007, and V-242008 STIG Hardened AMIs 8 AWS Windows AMIs Reference Internet Explorer (IE) 11 STIG Version 2 Release 5 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. IE 11 on Windows Server 2022, 2019, 2016, and 2012 R2 MS V-223015, V-223016, V-223017, V-223018, V-223019, V-223020, V-223021, V-223022, V-223023, V-223024, V-223025, V-223026, V-223027, V-223028, V-223029, V-223030, V-223031, V-223032, V-223033, V-223034, V-223035, V-223036, V-223037, V-223038, V-223039, V-223040, V-223041, V-223042, V-223043, V-223044, V-223045, V-223046, V-223048, V-223049, V-223050, V-223051, V-223052, V-223053, V-223054, V-223055, V-223056, V-223057, V-223058, V-223059, V-223060, V-223061, V-223062, V-223063, V-223064, V-223065, V-223066, V-223067, V-223068, V-223069, V-223070, V-223071, V-223072, V-223073, V-223074, V-223075, V-223076, V-223077, V-223078, V-223079, V-223080, V-223081, V-223082, V-223083, V-223084, V-223085, V-223086, V-223087, V-223088, V-223089, V-223090, V-223091, V-223092, V-223093, V-223094, V-223095, V-223096, V-223097, V-223098, V-223099, V-223100, V-223101, V-223102, V-223103, V-223104, V-223105, V-223106, V-223107, V-223108, V-223109, V-223110, V-223111, V-223112, V-223113, V-223114, V-223115, V-223116, V-223117, V-223118, V-223119, V-223120, V-223121, V-223122, V-223123, V-223124, V-223125, V-223126, V-223127, V-223128, V-223129, V-223130, V-223131, V-223132, V-223133, V-223134, V-223135, V-223136, V-223137, V-223138, V-223139, V-223140, V-223141, V-223142, V-223143, V-223144, V-223145, V-223146, V-223147, V-223148, V-223149, V-250540, V-250541, and V-252910 Microsoft Edge STIG Version 2 Release 2 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. STIG Hardened AMIs 9 AWS Windows AMIs Reference For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG
windows-ami-reference-005	windows-ami-reference.pdf	5	Release 2 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. STIG Hardened AMIs 9 AWS Windows AMIs Reference For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. Microsoft Edge on Windows Server 2022 V-235758, V-235759, V-235720, V-235721, V-235723, V-235724, V-235725, V-235726, V-235728, V-235729, V-235730, V-235732, V-235733, V-235734, V-235735, V-235736, V-235737, V-235738, V-235739, V-235740, V-235741, V-235742, V-235743, V-235744, V-235745, V-235746, V-235747, V-235748, V-235749, V-235750, V-235754, V-235756, V-235760, V-235761, V-235763, V-235764, V-235766, V-235767, V-235768, V-235769, V-235770, V-235771, V-235772, V-235773, V-235774, V-246736, V-235727, V-235731, V-235751, V-235752, and V-235765 Microsoft Defender STIG Version 2 Release 4 The following list contains STIG settings that apply to Windows operating system components for STIG Hardened EC2 AMIs. The following list contains STIG settings that apply for STIG Hardened Windows AMIs. Not all settings apply in all cases. For example, some STIG settings might not apply to standalone servers. Organization-speciﬁc policies can also aﬀect which settings apply, such as a requirement for administrators to review document settings. For a complete list of Windows STIGs, see the STIGs Document Library. For information about how to view the complete list, see STIG Viewing Tools. Microsoft Defender on Windows Server 2022 V-213426, V-213426, V-213452, V-213452, V-213452, V-213453, V-213453, V-213453, V-213427, V-213429, V-213430, V-213431, V-213432, V-213433, V-213434, V-213435, V-213436, V-213437, V-213438, V-213439, V-213440, V-213441, V-213442, V-213443, V-213444, V-213445, V-213446, V-213447, V-213448, V-213449, V-213450, V-213451, V-213455, V-213464, V-213465, and V-213466 Version history The following table provides version history updates for STIG settings that are applied to Windowsoperating systems and Windowscomponents. STIG Hardened AMIs 10 AWS Windows AMIs Reference Date AMIs Details 03/06/202 5 Windows Server 2022 STIG Version 2 Release 2 AMIs released for 2024 Q4 with updated versions where applicable, and applied STIGs. Windows Server 2019 STIG Version 3 Release 2 Windows Server 2016 STIG Version 2 Release 9 Windows Server 2012 R2 MS STIG Version 3 Release 5 Microsoft .NET Framework 4.0 STIG Version 2 Release 2 WindowsFirewall STIG Version 2 Release 2 Internet Explorer 11 STIG Version 2 Release 5 Microsoft Edge STIG Version 2 Release 2 Microsoft Defender STIG Version 2 Release 4 04/24/202 3 Windows Server 2022 STIG Version 1 Release 1 Microsoft Edge STIG Version 1 Release 6 Microsoft Defender STIG Version 2 Release 4 Added support for Windows Server 2022, Microsoft Edge, and Microsoft Defender. 03/01/202 3 Windows Server 2019 STIG Version 2 Release 5 AMIs released for 2022 Q4 with updated versions where applicable, and applied STIGs. STIG Hardened AMIs 11 AWS Windows AMIs Date AMIs Details Reference Windows Server 2016 STIG Version 2 Release 5 Windows Server 2012 R2 MS STIG Version 3 Release 5 Microsoft .NET Framework 4.0 STIG Version 2 Release 2 WindowsFirewall STIG Version 2 Release 1 Internet Explorer 11 STIG Version 2 Release 3 07/21/202 2 Windows Server 2019 STIG Version 2 R4 AMIs released with updated versions where applicable, and applied STIGs. Windows Server 2016 STIG Version 2 R4 Windows Server 2012 R2 MS STIG Version 3 R3 Microsoft .NET Framework 4.0 STIG Version 2 R1 WindowsFirewall STIG Version 2 R1 Internet Explorer 11 STIG V1 R19 STIG Hardened AMIs 12 AWS Windows AMIs Date AMIs Details Reference 12/15/202 1 Windows Server 2019 STIG Version 2 R3 AMIs released with updated versions where applicable, and applied STIGs. Windows Server 2016 STIG Version 2 R3 Windows Server 2012 R2 STIG Version 3 R3 Microsoft .NET Framework 4.0 STIG Version 2 R1 WindowsFirewall STIG Version 2 R1 Internet Explorer 11 STIG V1 R19 6/9/2021 Windows Server 2019 STIG Version 2 R2 Updated versions where applicable, and applied STIGs. Windows Server 2016 STIG Version 2 R2 Windows Server 2012 R2 STIG Version 3 R2 Microsoft .NET Framework 4.0 STIG Version 2 R1 WindowsFirewall STIG V1 R7 Internet Explorer 11 STIG V1 R19 STIG Hardened AMIs 13 AWS Windows AMIs Date AMIs Details Reference 4/5/2021 Windows Server 2019 STIG Version 2 R 1 Updated versions where applicable, and applied STIGs. Windows Server 2016 STIG Version 2 R 1 Windows Server 2012 R2 STIG Version 3 R 1 Microsoft .NET Framework 4.0 STIG Version 2 R 1 WindowsFirewall STIG V1 R 7 Internet Explorer 11 STIG V1 R 19 9/18/2020Windows Server 2019 STIG V1 R 5 Updated versions and applied STIGs. Windows Server 2016 STIG V1 R 12 Windows Server 2012 R2 STIG Version 2 R 19 Internet Explorer 11 STIG V1 R 19 Microsoft .NET Framework 4.0 STIG
windows-ami-reference-006	windows-ami-reference.pdf	6	Windows AMIs Date AMIs Details Reference 4/5/2021 Windows Server 2019 STIG Version 2 R 1 Updated versions where applicable, and applied STIGs. Windows Server 2016 STIG Version 2 R 1 Windows Server 2012 R2 STIG Version 3 R 1 Microsoft .NET Framework 4.0 STIG Version 2 R 1 WindowsFirewall STIG V1 R 7 Internet Explorer 11 STIG V1 R 19 9/18/2020Windows Server 2019 STIG V1 R 5 Updated versions and applied STIGs. Windows Server 2016 STIG V1 R 12 Windows Server 2012 R2 STIG Version 2 R 19 Internet Explorer 11 STIG V1 R 19 Microsoft .NET Framework 4.0 STIG V1 R 9 WindowsFirewall STIG V1 R 7 12/6/2019Server 2012 R2 Core and Base V2 R17 Updated versions and applied STIGs. Server 2016 Core and Base V1 R11 Internet Explorer 11 V1 R18 Microsoft .NET Framework 4.0 V1 R9 WindowsFirewall STIG V1 R17 STIG Hardened AMIs 14 AWS Windows AMIs Date AMIs Details Reference 9/17/2019Server 2012 R2 Core and Base V2 R16 Initial release. Server 2016 Core and Base V1 R9 Server 2019 Core and Base V1 R2 Internet Explorer 11 V1 R17 Microsoft .NET Framework 4.0 V1 R8 How Amazon creates AWS Windows AMIs The following content is a high level overview of the process Amazon uses to create AWS Windows AMIs. Details include what you can expect from an oﬃcial AWS Windows AMI, as well as the standards that Amazon uses to validate AMI security and reliability. Where AWS gets the Windows Server installation media When a new version of Windows Server is released, we download the Windows ISO from Microsoft and validate the hash Microsoft publishes. An initial AMI is then created from the Windows distribution ISO. The drivers needed to boot on EC2 are included in addition to our EC2 launch agent. To prepare this initial AMI for public release, we perform automated processes to convert the ISO to an AMI. This prepared AMI is used for the monthly automated update and release process. What to expect from an oﬃcial AWS Windows AMI Amazon provides AWS Windows AMIs with a variety of conﬁgurations for popular versions of Microsoft supported Windows Server Operating Systems. As outlined in the previous section, we start with the Windows Server ISO from Microsoft’s Volume Licensing Service Center (VLSC) and validate the hash to ensure it matches Microsoft’s documentation for new Windows Server operating systems. We perform the following changes using automation on AWS to take the current Windows Server AMIs and update them: How Amazon creates AWS Windows AMIs 15 AWS Windows AMIs Reference • Install all Microsoft recommended Windows security patches. We release images shortly after the monthly Microsoft patches are made available. • Install the latest drivers for AWS hardware, including network and disk drivers, the EC2WinUtil utility for troubleshooting, as well as GPU drivers in selected AMIs. • Include the following AWS launch agent software by default: • EC2Launch v2 for Windows Server 2022 and 2025, and optionally for Windows Server 2019 and 2016 with speciﬁc AMIs. • EC2Launch v1 for Windows Server 2016 and 2019. • EC2Conﬁg for Windows Server 2012 R2 and earlier. • Conﬁgure Windows Time to use the Amazon Time Sync Service. • Change all power schemes to set the display to never turn oﬀ. • Perform minor bug ﬁxes – generally one-line registry changes to enable or disable features that we have found to improve performance on AWS. • Tests and validates AMIs across new and existing EC2 platforms to help ensure compatibility, stability, and consistency before release. For a more detailed list that includes initialization, installation, and conﬁguration settings that are applied, see Updates applied for AWS Windows AMIs. How Amazon validates security, integrity, and authenticity of software on AMIs We take a number of steps during the image build process, to maintain the security, integrity, and authenticity of AWS Windows AMIs. A few examples include: • AWS Windows AMIs are built using source media obtained directly from Microsoft. • Windows Updates are downloaded directly from Microsoft’s Windows Update Service by Windows, and installed on the instance used to create the AMI during the image build process. • AWS Software is downloaded from secure S3 buckets and installed in the AMIs. • Drivers, such as for the chipset and GPU, are obtained directly from the vendor, stored in secure S3 buckets, and installed on the AMIs during the image build process. Validation of software on AWS AMIs 16 AWS Windows AMIs Reference How Amazon decides which AWS Windows AMIs to oﬀer Each AMI is extensively tested prior to release to the public. We periodically streamline our AMI oﬀerings to simplify customer choice and to reduce costs. • New AMI oﬀerings are created for new OS releases. You can count on Amazon releasing Base, Core, and SQL Express/Standard/Web/Enterprise oﬀerings in English and other
windows-ami-reference-007	windows-ami-reference.pdf	7	Drivers, such as for the chipset and GPU, are obtained directly from the vendor, stored in secure S3 buckets, and installed on the AMIs during the image build process. Validation of software on AWS AMIs 16 AWS Windows AMIs Reference How Amazon decides which AWS Windows AMIs to oﬀer Each AMI is extensively tested prior to release to the public. We periodically streamline our AMI oﬀerings to simplify customer choice and to reduce costs. • New AMI oﬀerings are created for new OS releases. You can count on Amazon releasing Base, Core, and SQL Express/Standard/Web/Enterprise oﬀerings in English and other widely used languages. The primary diﬀerence between Base and Core oﬀerings is that Base oﬀerings have a desktop/GUI whereas Core oﬀerings are PowerShell command line only. For more information, see Windows Server Core on the Microsoft website. • New AMI oﬀerings are created to support new platforms – for example, the Deep Learning andNvidia AMIs were created to support customers using our GPU-based instance types (P2 and P3, G3, and others). • Less popular AMIs are sometimes removed. If we see a particular AMI is launched only a few times in its entire lifespan, we will remove it in favor of more widely used options. If there is an AMI variant that you would like to see, let us know by opening a support case, or by providing feedback. Patches, security updates, and AMI IDs Amazon provides updated, fully-patched AWS Windows AMIs within ﬁve business days of Microsoft's patch Tuesday (the second Tuesday of each month). The new AMIs are available immediately from the Images page in the Amazon EC2 console. The new AMIs are available in the AWS Marketplace and the Quick Start tab of the launch instance wizard within a few days of their release. Note Instances launched from Windows Server 2019 and later AMIs may show a Windows Update dialog message stating "Some settings are managed by your organization." This message appears as a result of changes in Windows Server 2019 and does not impact the behavior of Windows Update or your ability to manage update settings. To remove this warning, see "Some settings are managed by your organization". How Amazon decides which AWS Windows AMIs to oﬀer 17 AWS Windows AMIs Reference To ensure that customers have the latest security updates by default, AWS keeps AWS Windows AMIs available for three months. After releasing new AWS Windows AMIs, AWS makes the AWS Windows AMIs that are older than three months private within 10 days. After AWS makes an AMI private, you may no longer retrieve it by any method. In the console, the AMI ID ﬁeld for a private AMI states, Cannot load detail for ami-1234567890abcdef0. You may not be permitted to view it. If an AMI is deprecated but is not yet marked private, you can still use it. However, we recommend that you always use the latest version. The AWS Windows AMIs; in each release have new AMI IDs. Therefore, we recommend that you write scripts that locate the latest AWS Windows AMIs by their names, rather than by their IDs. For more information, see the following examples: • Get-EC2ImageByName (AWS Tools for Windows PowerShell) • Query for the Latest AWS Windows AMI Using Systems Manager Parameter Store • Walkthrough: Looking Up Amazon Machine Image IDs (AWS Lambda, AWS CloudFormation) Ports and Protocols for AWS Windows AMIs The following tables list the ports, protocols, and directions by workload for AWS Windows Amazon Machine Images (AMIs). Contents • AllJoyn Router • Cast to Device • Core Networking • Delivery Optimization • Diag Track • DIAL Protocol Server • File and Printer Sharing • File Server Remote Management • ICMP v4 All Ports and Protocols 18 Reference AWS Windows AMIs • Microsoft Edge • Microsoft Media Foundation Network Source • Multicast • Remote Desktop • WindowsDevice Management • WindowsFeature Experience Pack • WindowsFirewall Remote Management • WindowsRemote Management AllJoyn Router OS Rule Description Port Protocol Direction Windows Server 2016 AllJoyn Router (TCP- In) Inbound rule for AllJoyn Router traﬃc [TCP] Local: 9955 TCP In Remote: Any Windows Server 2019 Windows Server 2022 AllJoyn Router (TCP- Out) Outbound rule for AllJoyn Local: Any TCP Out Remote: Any AllJoyn Router (UDP- In) AllJoyn Router (UDP- Out) Router traﬃc [TCP] Inbound rule for AllJoyn Router traﬃc [UDP] Outbound rule for AllJoyn Router traﬃc [UDP] Local: Any UDP In Remote: Any Local: Any UDP Out Remote: Any AllJoyn Router 19 AWS Windows AMIs Cast to Device Reference OS Rule Description Port Protocol Direction Windows Server 2016 Cast to Device Inbound rule for the Cast Local: 2177 TCP In Windows Server 2019 Windows Server 2022 functionality to Device (qWave-TCP- functiona Remote: Any In) lity to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177] Cast to Device Outbound
windows-ami-reference-008	windows-ami-reference.pdf	8	AllJoyn Router (UDP- In) AllJoyn Router (UDP- Out) Router traﬃc [TCP] Inbound rule for AllJoyn Router traﬃc [UDP] Outbound rule for AllJoyn Router traﬃc [UDP] Local: Any UDP In Remote: Any Local: Any UDP Out Remote: Any AllJoyn Router 19 AWS Windows AMIs Cast to Device Reference OS Rule Description Port Protocol Direction Windows Server 2016 Cast to Device Inbound rule for the Cast Local: 2177 TCP In Windows Server 2019 Windows Server 2022 functionality to Device (qWave-TCP- functiona Remote: Any In) lity to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177] Cast to Device Outbound rule for functionality the Cast (qWave-TCP- to Device Local: Any TCP Out Remote: 2177 Out) Cast to Device functionality (qWave-UDP- In) functiona lity to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177] Inbound rule for the Cast to Device functiona lity to allow use of the Local: 2177 UDP In Remote: Any Cast to Device 20 AWS Windows AMIs Reference OS Rule Description Port Protocol Direction Quality Windows Audio Video Experience Service. [UDP 2177] Cast to Device Outbound rule for functionality the Cast (qWave-UDP- to Device Local: Any UDP Out Remote: 2177 Out) functiona lity to allow use of the Quality Windows Audio Video Experience Service. [UDP 2177] Cast to Device SSDP Inbound rule to allow Local: Ply2Disc Discovery discovery (UDP-In) of Cast Remote: Any UDP In to Device targets using SSDP Cast to Device 21 AWS Windows AMIs Reference OS Rule Description Port Protocol Direction Local: 10246 TCP In Remote: Any Local: Any UDP In Remote: Any Local: Any UDP Out Remote: Any Cast to Device Inbound rule for Streaming the Cast to Server Device server (HTTP-Str to allow eaming-In) streaming using HTTP. [TCP 10246] Inbound rule for the Cast to Device server to allow Cast to Device Streaming Server (RTCP-Str eaming-In) streaming using RTSP and RTP. [UDP] Cast to Device Outbound rule for Streaming the Cast to Server (RTP- Device server Streaming- to allow Out) streaming using RTSP and RTP. [UDP] Cast to Device 22 AWS Windows AMIs Reference OS Rule Description Port Protocol Direction Cast to Device Inbound rule for Local: 235, 542, 355, Streaming the Cast to 523, 556 Server Device server (RTSP-Str to allow eaming-In) streaming Remote: Any TCP In using RTSP and RTP. [TCP 23554, 23555, 23556] Cast to Device UPnP Inbound rule to allow Events (TCP- receiving Local: 2869 TCP In Remote: Any In) UPnP Events from Cast to Device targ ets Core Networking Windows Server 2016, 2019, and 2022 OS Rule Deﬁnition Port Protocol Direction Windows Server 2016 Windows Server 2019 Windows Server 2022 Destination Unreachable (ICMPv6-In) Destination Unreachab le error messages are sent from any node that a packet ICMPv6 In Core Networking 23 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction traverses which is unable to forward the packet for any reason except congestion. Destination Unreachable Destination Unreachable Fragmenta tion Needed Fragmenta tion Needed (ICMPv4-In) error me ICMPv4 In ssages are sent from any node that a packet traverses which is unable to forward the packet because fragmenta tion was needed and the don't fragment bit was set. Core Networking 24 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networking Outbound rule to - DNS (UDP- allow DNS Local: Any Remote: 53 UDP Out Out) requests. DNS responses based on requests that match this rule are permitted regardless of source address. This behavior is classiﬁed as loose source mapping. Dynamic Host Allows DHCP (Dynamic Local: 68 UDP In Conﬁgura Host tion Protocol Conﬁgura (DHCP-In) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. Core Networking 25 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Dynamic Host Allows DHCP (Dynamic Local: 68 UDP Out Conﬁgura Host tion Protocol Conﬁgura (DHCP-Out) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. UDP In Dynamic Host Allows DHCPV6 Conﬁgura (Dynamic tion Protocol Host for IPv6 Conﬁgura (DHCPV6-In) tion Protocol Local: 546 Remote: 547 for IPv6) messages for stateful and stateless conﬁgu ration. Core Networking 26 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction UDP Out Dynamic Host Allows DHCPV6 Conﬁgura (Dynamic tion Protocol Host for IPv6 Conﬁgura (DHCPV6-O tion Protocol Local: 546 Remote: 547 ut) for IPv6) messages for stateful and stateless conﬁgu ration. Core Networking - Outbound rule to allow Group Policy remote (LSASS-Out) LSASS traﬃc Local: Any Remote: Any TCP Out for Group Policy updates. TCP Out TCP Out Core Networking - Core Networking - Group Policy Group Policy (NP-Out) (NP-Out) Local: Any Remote: 445 Core Networking - Group Policy (TCP-Out) Outbound rule to allow remote RPC traﬃc for Group Po licy updates. Local: Any Remote: Any Core Networking 27 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction 2 In 2 Out Internet Group IGMP messages Managemen
windows-ami-reference-009	windows-ami-reference.pdf	9	546 Remote: 547 ut) for IPv6) messages for stateful and stateless conﬁgu ration. Core Networking - Outbound rule to allow Group Policy remote (LSASS-Out) LSASS traﬃc Local: Any Remote: Any TCP Out for Group Policy updates. TCP Out TCP Out Core Networking - Core Networking - Group Policy Group Policy (NP-Out) (NP-Out) Local: Any Remote: 445 Core Networking - Group Policy (TCP-Out) Outbound rule to allow remote RPC traﬃc for Group Po licy updates. Local: Any Remote: Any Core Networking 27 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction 2 In 2 Out Internet Group IGMP messages Managemen are sent and t Protocol received by (IGMP-In) nodes to create, join, and depart multicast groups. IGMP messages are sent and received by Core Networkin g - Internet Group Managemen nodes to t Protocol create, join, (IGMP-Out) and depart multicast groups. Core Networkin Inbound TCP rule to allow g - IPHTTPS IPHTTPS (TCP-In) tunneling Local: IPHTPS Remote: Any TCP In technology to provide connectivity across HTTP proxies and ﬁrewalls. Core Networking 28 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Outbound TCP rule g - IPHTTPS to allow (TCP-Out) IPHTTPS Local: Any Remote: IPHTPS TCP Out IPv6 (IPv6- In) tunneling technology to provide connectivity across HTTP proxies and ﬁrewalls. Inbound rule required to permit IPv6 traﬃc for ISATAP ( Intra-Site Automatic Tunnel Addressin g Protocol) and 6to4 tunneling services. 41 In Core Networking 29 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction IPv6 (IPv6- Out) Outbound rule required 41 Out to permit IPv6 traﬃc for ISATAP (Intra-Site Automatic Tunnel Addressin g Protocol) and 6to4 tunneling services. Multicast Listener Done Multicast Listener Done (ICMPv6-In) messages ICMPv6 In inform local routers that there are no longer any members remaining for a specif ic multicast address on the subnet. Core Networking 30 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Done Multicast Listener Done (ICMPv6-O messages ICMPv6 Out ut) inform local routers that there are no longer any members remaining for a specif ic multicast address on the subnet. Multicast Listener Query An IPv6 multicast -capable (ICMPv6-In) router uses ICMPv6 In the Multicast Listene r Query message to query a link for multicast group me mbership. Core Networking 31 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction ICMPv6 Out Multicast Listener Query An IPv6 multicast -capable (ICMPv6-O router uses ut) the Multicast Listene r Query message to query a link for multicast group me mbership. Core Networking 32 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Report The Multicast Listener (ICMPv6-In) Report ICMPv6 In message is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 33 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Report The Multicast Listener (ICMPv6-O Report ICMPv6 Out ut) message is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 34 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-In) message ICMPv6 In is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 35 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-O message ICMPv6 Out ut) is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 36 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Neighbor Discovery Advertise ment Neighbor Discovery Advertise ment (ICMPv6-In) messages ICMPv6 In are sent by nodes to notify other nodes of link-laye r address changes or in response to a Neighbor Discovery Solicitation request. Core Networking 37 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Neighbor Discovery Advertise ment Neighbor Discovery Advertise ment (ICMPv6-O messages ICMPv6 Out ut) are sent by nodes to notify other nodes of link-laye r address changes or in response to a Neighbor Discovery Solicitation request. Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-In) are sent by ICMPv6 In nodes to discover the link-layer address of another on- link IPv6 node. Core Networking 38 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction ICMPv6 Out Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-O are sent by ut) nodes to discover the link-layer address of another on- link IPv6 node. Packet Too Big (ICMPv6- Packet
windows-ami-reference-010	windows-ami-reference.pdf	10	Advertise ment Neighbor Discovery Advertise ment (ICMPv6-O messages ICMPv6 Out ut) are sent by nodes to notify other nodes of link-laye r address changes or in response to a Neighbor Discovery Solicitation request. Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-In) are sent by ICMPv6 In nodes to discover the link-layer address of another on- link IPv6 node. Core Networking 38 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction ICMPv6 Out Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-O are sent by ut) nodes to discover the link-layer address of another on- link IPv6 node. Packet Too Big (ICMPv6- Packet Too Big error ICMPv6 In In) messages are sent from any node that a packet traverses which is unable to forward the packet b ecause the packet is too large for the next link. Core Networking 39 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Packet Too Big (ICMPv6- Packet Too Big error ICMPv6 Out Out) messages are sent from any node that a packet traverses which is unable to forward the packet b ecause the packet is too large for the next link. Parameter Problem Parameter Problem (ICMPv6-In) error ICMPv6 In messages are sent by nodes when packets are incorrectly generated. Core Networking 40 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Parameter Problem Parameter Problem (ICMPv6-O error ICMPv6 Out ut) messages are sent by nodes when packets are incorrectly generated. Router Advertise ment Router Advertise ment (ICMPv6-In) messages are sent by routers to other nodes for stateless auto-conf iguration. Router Advertise ment Router Advertise ment (ICMPv6-O messages ut) are sent by routers to other nodes for stateless auto-conf iguration. ICMPv6 In ICMPv6 Out Core Networking 41 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Router Solicitation Router Solicitation (ICMPv6-In) messages ICMPv6 In are sent by nodes seeking routers to provide stateless auto-conf iguration. Router Solicitation Router Solicitation (ICMPv6-O messages ICMPv6 Out ut) are sent by nodes seeking routers to provide stateless auto-conf iguration. Core Networking 42 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Inbound UDP rule g - Teredo to allow Local: Teredo (UDP-In) Teredo edge Remote: Any UDP In traversal . This tec hnology provides address assignmen t and automatic tunneling for unicast IPv6 traﬃc when an IPv6/IPv4 host is locat ed behind an IPv4 network address translator. Core Networking 43 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Outbound UDP rule g - Teredo to allow (UDP-Out) Teredo edge Local: Any Remote: Any UDP Out traversal . This tec hnology provides address assignmen t and automatic tunneling for unicast IPv6 traﬃc when an IPv6/IPv4 host is locat ed behind an IPv4 network address translator. Core Networking 44 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-In) error ICMPv6 In messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Core Networking 45 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-O error ICMPv6 Out ut) messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Windows Server 2012 and 2012 R2 OS Rule Deﬁnition Port Protocol Direction Local: 68 ICMPv6 In Remote: 67 Destination Unreachable (ICMPv6-In) Windows Server 2012 Windows Server 2012 R2 Destination Unreachab le error messages are sent from any node that a packet traverses which is unable to forward the Core Networking 46 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction packet for any reason except congestion. Destination Unreachable Destination Unreachable Fragmenta Fragmenta tion Needed tion Needed (ICMPv4-In) error me Local: 68 ICMPv4 In Remote: 67 ssages are sent from any node that a packet traverses which is unable to forward the packet because fragmenta tion was needed and the don't fragment bit was set. Core Networking 47 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networking Outbound rule to - DNS (UDP- allow DNS Local: Any Remote: 53 UDP Out Out) requests. DNS responses based on requests that match this rule are permitted regardless of source address. This behavior is classiﬁed as loose source mapping. Dynamic Host Allows DHCP (Dynamic Local: 68 UDP In Conﬁgura Host tion Protocol Conﬁgura (DHCP-In) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. Core Networking 48 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Dynamic Host Allows DHCP (Dynamic Local: 68 UDP Out Conﬁgura Host tion Protocol Conﬁgura (DHCP-Out) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. UDP In Dynamic Host Allows DHCPV6 Conﬁgura (Dynamic tion Protocol Host for IPv6 Conﬁgura (DHCPV6-In) tion Protocol Local: 546 Remote:
windows-ami-reference-011	windows-ami-reference.pdf	11	requests that match this rule are permitted regardless of source address. This behavior is classiﬁed as loose source mapping. Dynamic Host Allows DHCP (Dynamic Local: 68 UDP In Conﬁgura Host tion Protocol Conﬁgura (DHCP-In) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. Core Networking 48 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Dynamic Host Allows DHCP (Dynamic Local: 68 UDP Out Conﬁgura Host tion Protocol Conﬁgura (DHCP-Out) tion Remote: 67 Protocol) messages for stateful auto-conf iguration. UDP In Dynamic Host Allows DHCPV6 Conﬁgura (Dynamic tion Protocol Host for IPv6 Conﬁgura (DHCPV6-In) tion Protocol Local: 546 Remote: 547 for IPv6) messages for stateful and stateless conﬁgu ration. Core Networking 49 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction UDP Out Dynamic Host Allows DHCPV6 Conﬁgura (Dynamic tion Protocol Host for IPv6 Conﬁgura (DHCPV6-O tion Protocol Local: 546 Remote: 547 ut) for IPv6) messages for stateful and stateless conﬁgu ration. Core Networking - Outbound rule to allow Group Policy remote (LSASS-Out) LSASS traﬃc Local: Any Remote: Any TCP Out for Group Policy updates. TCP Out TCP Out Core Networking - Core Networking - Group Policy Group Policy (NP-Out) (NP-Out) Local: Any Remote: 445 Core Networking - Group Policy (TCP-Out) Outbound rule to allow remote RPC traﬃc for Group Po licy updates. Local: Any Remote: Any Core Networking 50 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Internet Group IGMP messages Managemen are sent and t Protocol received by (IGMP-In) nodes to Local: 68 Remote: 67 2 In create, join, and depart multicast groups. IGMP messages are sent and received by Core Networkin g - Internet Group Managemen nodes to t Protocol create, join, (IGMP-Out) and depart multicast groups. 2 Out Local: 68 Remote: 67 Core Networkin Inbound TCP rule to allow g - IPHTTPS IPHTTPS (TCP-In) tunneling Local: IPHTPS Remote: Any TCP In technology to provide connectivity across HTTP proxies and ﬁrewalls. Core Networking 51 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Outbound TCP rule g - IPHTTPS to allow (TCP-Out) IPHTTPS Local: Any Remote: IPHTPS TCP Out IPv6 (IPv6- In) tunneling technology to provide connectivity across HTTP proxies and ﬁrewalls. Inbound rule required to permit IPv6 traﬃc for ISATAP ( Intra-Site Automatic Tunnel Addressin g Protocol) and 6to4 tunneling services. 41 In Local: Any Remote: 445 Core Networking 52 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction IPv6 (IPv6- Out) Outbound rule required Local: Any 41 Out Remote: 445 to permit IPv6 traﬃc for ISATAP (Intra-Site Automatic Tunnel Addressin g Protocol) and 6to4 tunneling services. Multicast Listener Done Multicast Listener Done (ICMPv6-In) messages Local: 68 ICMPv6 In Remote: 67 inform local routers that there are no longer any members remaining for a specif ic multicast address on the subnet. Core Networking 53 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Done Multicast Listener Done (ICMPv6-O messages Local: 68 ICMPv6 Out Remote: 67 ut) inform local routers that there are no longer any members remaining for a specif ic multicast address on the subnet. Multicast Listener Query An IPv6 multicast -capable (ICMPv6-In) router uses Local: 68 ICMPv6 In Remote: 67 the Multicast Listene r Query message to query a link for multicast group me mbership. Core Networking 54 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Query An IPv6 multicast -capable (ICMPv6-O router uses ut) the Multicast Local: 68 ICMPv6 Out Remote: 67 Listene r Query message to query a link for multicast group me mbership. Core Networking 55 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Report The Multicast Listener (ICMPv6-In) Report Local: 68 ICMPv6 In Remote: 67 message is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 56 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Report The Multicast Listener (ICMPv6-O Report Local: 68 ICMPv6 Out Remote: 67 ut) message is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 57 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-In) message Local: 68 ICMPv6 In Remote: 67 is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 58 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-O message Local: 68 ICMPv6 Out Remote: 67 ut) is used by a
windows-ami-reference-012	windows-ami-reference.pdf	12	response to a Multicast Listener Query. Core Networking 57 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-In) message Local: 68 ICMPv6 In Remote: 67 is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 58 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Multicast Listener Multicast Listener Report v2 Report v2 (ICMPv6-O message Local: 68 ICMPv6 Out Remote: 67 ut) is used by a listen ing node to either immediate ly report its interest in receiving multicast traﬃc at a speciﬁc multicast address or in response to a Multicast Listener Query. Core Networking 59 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Neighbor Discovery Advertise ment Neighbor Discovery Advertise ment (ICMPv6-In) messages Local: 68 ICMPv6 In Remote: 67 are sent by nodes to notify other nodes of link-laye r address changes or in response to a Neighbor Discovery Solicitation request. Core Networking 60 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Neighbor Discovery Advertise ment Neighbor Discovery Advertise ment (ICMPv6-O messages Local: 68 ICMPv6 Out Remote: 67 ut) are sent by nodes to notify other nodes of link-laye r address changes or in response to a Neighbor Discovery Solicitation request. Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-In) are sent by Local: 68 ICMPv6 In Remote: 67 nodes to discover the link-layer address of another on- link IPv6 node. Core Networking 61 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Neighbor Discovery Neighbor Discovery Solicitation Solicitations (ICMPv6-O are sent by Local: 68 ICMPv6 Out Remote: 67 ut) nodes to discover the link-layer address of another on- link IPv6 node. Packet Too Big (ICMPv6- Packet Too Big error Local: 68 ICMPv6 In In) Remote: 67 messages are sent from any node that a packet traverses which is unable to forward the packet b ecause the packet is too large for the next link. Core Networking 62 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Packet Too Big (ICMPv6- Packet Too Big error Local: 68 ICMPv6 Out Out) Remote: 67 messages are sent from any node that a packet traverses which is unable to forward the packet b ecause the packet is too large for the next link. Parameter Problem Parameter Problem (ICMPv6-In) error Local: 68 ICMPv6 In Remote: 67 messages are sent by nodes when packets are incorrectly generated. Core Networking 63 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Parameter Problem Parameter Problem (ICMPv6-O error Local: 68 ICMPv6 Out Remote: 67 ut) messages are sent by nodes when packets are incorrectly generated. Router Advertise ment Router Advertise ment (ICMPv6-In) messages Local: 68 ICMPv6 In Remote: 67 are sent by routers to other nodes for stateless auto-conf iguration. Router Advertise ment Router Advertise ment (ICMPv6-O messages Local: 68 ICMPv6 Out Remote: 67 ut) are sent by routers to other nodes for stateless auto-conf iguration. Core Networking 64 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Router Solicitation Router Solicitation (ICMPv6-In) messages Local: 68 ICMPv6 In Remote: 67 are sent by nodes seeking routers to provide stateless auto-conf iguration. Router Solicitation Router Solicitation (ICMPv6-O messages Local: 68 ICMPv6 Out Remote: 67 ut) are sent by nodes seeking routers to provide stateless auto-conf iguration. Core Networking 65 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Inbound UDP rule g - Teredo to allow Local: Teredo (UDP-In) Teredo edge Remote: Any UDP In traversal . This tec hnology provides address assignmen t and automatic tunneling for unicast IPv6 traﬃc when an IPv6/IPv4 host is locat ed behind an IPv4 network address translator. Core Networking 66 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Core Networkin Outbound UDP rule g - Teredo to allow (UDP-Out) Teredo edge Local: Any Remote: Any UDP Out traversal . This tec hnology provides address assignmen t and automatic tunneling for unicast IPv6 traﬃc when an IPv6/IPv4 host is locat ed behind an IPv4 network address translator. Core Networking 67 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-In) error Local: 68 ICMPv6 In Remote: 67 messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Core Networking 68 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-O error Local: 68 ICMPv6 Out Remote: 67 ut) messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Delivery Optimization OS Rule Deﬁnition
windows-ami-reference-013	windows-ami-reference.pdf	13	Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-In) error Local: 68 ICMPv6 In Remote: 67 messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Core Networking 68 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Time Exceeded Time Exceeded (ICMPv6-O error Local: 68 ICMPv6 Out Remote: 67 ut) messages are generated from any node tha t a packet traverses if the Hop Limit value is decre mented to zero at any point on the path. Delivery Optimization OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 Windows Server 2022 DeliveryO ptimization- TCP-In DeliveryO ptimization- UDP-In Inbound rule to allow Delivery Optimization to connect to remote endp oints. Inbound rule to allow Delivery Optimization Local: 7680 TCP In Remote: Any Local: 7680 UDP In Remote: Any Delivery Optimization 69 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction to connect to remote endp oints. Diag Track Windows Server 2019 and 2022 OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 Windows Server 2022 Connected User Uniﬁed Telemetry Experienc Client es and Outbound Telemetry Traﬃc. Local: Any Remote: 443 TCP Out Windows Server 2016 OS Rule Deﬁnition Port Protocol Direction Windows Server 2016 Connected User Experienc es and Telemetry Uniﬁed Telemetry Client Outbound Traﬃc. Local: Any Remote: Any TCP Out DIAL Protocol Server OS Rule Deﬁnition Port Protocol Direction Windows Server 2016 DIAL protocol server Inbound rule for DIAL Local: 10247 TCP In (HTTP-In) protocol Diag Track 70 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 Windows Server 2022 Remote: Any server to allow remote c ontrol of Apps using HTTP. File and Printer Sharing OS Rule Deﬁnition Port Protocol Direction Windows Server 2012 Windows Server 2012 R2 File and Printer Sharing (Echo Request - ICMPv4-In) File and Printer Sharing (Echo Echo Request messages are sent as ping requests to other nodes. Echo Request messages are sent as ping requests to Request - other nodes. ICMPv4-Out) File and Printer Sharing (Echo Request - ICMPv6-In) File and Printer Sharing Echo Request messages are sent as ping requests to other nodes. Echo Request messages are sent as ping ICMPv4 In Local: 5355 Remote: Any Local: 5355 ICMPv4 Out Remote: Any ICMPv6 In Local: 5355 Remote: Any Local: 5355 ICMPv6 Out File and Printer Sharing 71 AWS Windows AMIs OS Rule (Echo Request - ICMPv6-Out) Deﬁnition Port Protocol Direction requests to Remote: Any other nodes. Reference Local: 5355 UDP In Remote: Any UDP Out Local: Any Remote: 5355 File and Printer Sharing Inbound rule for File and Printer (LLMNR-UD Sharing to P-In) File and Printer Sharing allow Link Local Mu lticast Name Resolution. Outbound rule for File and Printer (LLMNR-UD Sharing to P-Out) allow Link Local Mu lticast Name Resolution. File and Printer Inbound rule for File Sharing (NB- and Printer Local: 138 Remote: Any UDP In Datagram-In) Sharing to allow NetBIOS Datagram transmis sion and reception. File and Printer Sharing 72 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction File and Printer Outbound rule for File Sharing (NB- and Printer Local: Any Remote: 138 UDP Out Datagram- Out) Sharing to allow NetBIOS Datagram transmis sion and reception. File and Printer Inbound rule for File Sharing (NB- and Printer Local: 137 UDP In Remote: Any Name-In) Sharing to allow NetBIOS Name Resolu tion. File and Printer Outbound rule for File Sharing (NB- and Printer Local: Any Remote: 137 UDP Out Name-Out) Sharing to allow NetBIOS Name Res olution. File and Printer Sharing 73 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction File and Printer Inbound rule for File Sharing (NB- and Printer Local: 139 TCP In Remote: Any Session-In) Sharing to allow NetBIOS Session Service connections. File and Printer Sharing (NB- Outbound rule for File and Printer Session-Out) Sharing Local: Any Remote: 139 TCP Out File and Printer Sharing (SMB-In) to allow NetBIOS Session Service connections. Inbound rule for File and Printer Sharing to allow Server Message Blo ck transmiss ion and reception via Named Pipes. Local: 445 TCP In Remote: Any File and Printer Sharing 74 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction File and Printer Sharing Outbound rule for File and Printer (SMB-Out) Sharing to Local: Any Remote: 445 TCP Out allow Server Message Block transmiss ion and reception via Named Pipes. Inbound rule for File and Printer Sharing to allow the Print Spooler Service to communicate via TCP/RPC. Inbound rule for the RPCSS service to allow RPC/ TCP traﬃc for the Spoo ler Service. File and Printer Sharing (Spooler Service - RPC) File and Printer Sharing (Spooler Service - RPC-EPMAP) Local: RPC TCP In Remote: Any TCP In Local: RPC- EPMap Remote: Any File and Printer Sharing 75 AWS
windows-ami-reference-014	windows-ami-reference.pdf	14	Protocol Direction File and Printer Sharing Outbound rule for File and Printer (SMB-Out) Sharing to Local: Any Remote: 445 TCP Out allow Server Message Block transmiss ion and reception via Named Pipes. Inbound rule for File and Printer Sharing to allow the Print Spooler Service to communicate via TCP/RPC. Inbound rule for the RPCSS service to allow RPC/ TCP traﬃc for the Spoo ler Service. File and Printer Sharing (Spooler Service - RPC) File and Printer Sharing (Spooler Service - RPC-EPMAP) Local: RPC TCP In Remote: Any TCP In Local: RPC- EPMap Remote: Any File and Printer Sharing 75 AWS Windows AMIs Reference File Server Remote Management OS Rule Deﬁnition Port Protocol Direction Windows Server 2012 File Server Remote Inbound rule to allow Local: 135 TCP In Windows Server 2012 R2 Management DCOM traﬃc (DCOM-In) to manage Remote: Any File Server Remote Management (SMB-In) WMI-In the File Services role. Inbound rule to allow SMB traﬃc to manage the File Services role. Inbound rule to allow WMI traﬃc to manage the File Services role. Local: 445 TCP In Remote: Any Local: RPC TCP In Remote: Any ICMP v4 All OS Rule Port Protocol Direction All ICMP v4 Local: 139 ICMPv4 In Remote: Any Windows Server 2012 Windows Server 2012 R2 File Server Remote Management 76 AWS Windows AMIs Microsoft Edge Reference OS Rule Port Protocol Direction Windows Server 2022 Microsoft Edge (mDNS-In) Local: 5353 UDP In Remote: Any Microsoft Media Foundation Network Source OS Rule Port Protocol Direction Windows Server 2022 Microsoft Media Foundation Local: 554, 8554-8558 TCP Network Source IN [TCP 554] Remote: Any Microsoft Media Foundatio Local: 5000-5020 UDP n Network Source IN [UDP 5004-5009] Microsoft Media Foundation Network Source OUT [TCP ALL] Remote: Any Local: Any TCP Remote: 554, 8554-8558 In In In Microsoft Edge 77 AWS Windows AMIs Multicast Windows Server 2019 and 2022 Reference OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 Windows Server 2022 mDNS (UDP- In) Inbound rule for mDNS Local: 5353 UDP In traﬃc. Remote: Any mDNS (UDP- Out) Outbound rule for Local: Any UDP Out mDNS traﬃc. Remote: 5353 Windows Server 2016 OS Rule Deﬁnition Port Protocol Direction Windows Server 2016 mDNS (UDP- In) Inbound rule for mDNS Local: mDNS UDP In traﬃc. Remote: Any mDNS (UDP- Out) Outbound rule for Local: 5353 UDP Out Remote: Any mDNS traﬃc. Remote Desktop Windows Server 2012 R2, 2016, 2019, and 2022 OS Rule Deﬁnition Port Protocol Direction Remote Desktop Inbound rule for the Local: Any TCP In Multicast 78 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction Windows - Shadow Remote Remote: Any Server 2012 R2 (TCP-In) Windows Server 2016 Windows Server 2019 Windows Server 2022 Remote Desktop - User Mode (TCP-In) Desktop service to allow sh adowing of an existing Remote Desktop session. Inbound rule for the Remote Desktop service to allow RDP trafﬁc. TCP In Local: 3389 Remote: Any Remote Desktop - Inbound rule for the User Mode Remote Local: 3389 Remote: Any UDP In (UDP-In) Desktop service to allow RDP trafﬁc. Windows Server 2012 OS Rule Deﬁnition Port Protocol Direction Windows Server 2012 Remote Desktop - User Mode (TCP-In) Inbound rule for the Remote Desktop service to Local: 3389 Remote: Any TCP In Remote Desktop 79 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction allow RDP traﬃc. Remote Desktop - Inbound rule for the User Mode Remote Local: 3389 Remote: Any UDP In (UDP-In) Desktop service to allow RDP traﬃc. WindowsDevice Management Windows Server 2022 OS Rule Deﬁnition Port Protocol Direction Windows Server 2022 WindowsDe vice Allow outbound Managemen TCP traﬃc t Certiﬁca from te Installer WindowsDe (TCP out) vice TCP Out Local: Any Remote: Any Managemen t Certiﬁcate Installer. Allow outbound TCP traﬃc from WindowsDe vice Managemen WindowsDe vice Managemen t Device Enroller (TCP out) TCP Out Local: Any Remote: 80, 443 WindowsDevice Management 80 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction t Device Enroller. WindowsDe vice Allow outbound Managemen TCP traﬃc t Enrollment from Service (TCP WindowsDe out) vice Managemen t Enrollmen t Service. TCP Out Local: Any Remote: Any WindowsDe vice Allow outbound Managemen TCP traﬃc t Sync Client from (TCP out) WindowsDe Local: Any Remote: Any TCP Out vice Managemen t Sync Cli ent. Windows Server 2019 OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 WindowsDe vice Managemen t Certiﬁca te Installer (TCP out) Allow outbound TCP traﬃc from WindowsDe vice Managemen Local: Any TCP Out Remote: Any WindowsDevice Management 81 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction t Certiﬁcate Installer. WindowsDe vice Allow outbound Managemen TCP traﬃc t Enrollment from Service (TCP WindowsDe out) vice Managemen t Enrollmen t Service. WindowsDe vice Allow outbound Managemen TCP traﬃc t Sync Client from (TCP out) WindowsDe vice Managemen t Sync Client . Allow outbound TCP traﬃc
windows-ami-reference-015	windows-ami-reference.pdf	15	Managemen t Sync Cli ent. Windows Server 2019 OS Rule Deﬁnition Port Protocol Direction Windows Server 2019 WindowsDe vice Managemen t Certiﬁca te Installer (TCP out) Allow outbound TCP traﬃc from WindowsDe vice Managemen Local: Any TCP Out Remote: Any WindowsDevice Management 81 AWS Windows AMIs Reference OS Rule Deﬁnition Port Protocol Direction t Certiﬁcate Installer. WindowsDe vice Allow outbound Managemen TCP traﬃc t Enrollment from Service (TCP WindowsDe out) vice Managemen t Enrollmen t Service. WindowsDe vice Allow outbound Managemen TCP traﬃc t Sync Client from (TCP out) WindowsDe vice Managemen t Sync Client . Allow outbound TCP traﬃc from WindowsEn rollment WinRT. WindowsEn rollment WinRT (TCP Out) Local: Any TCP Out Remote: Any Local: Any TCP Out Remote: Any Local: Any TCP Out Remote: Any WindowsDevice Management 82 AWS Windows AMIs Reference WindowsFeature Experience Pack OS Rule Deﬁnition Port Protocol Direction Windows Server 2022 WindowsFe ature WindowsFe ature Experience Experience Pack Pack. Any Out WindowsFirewall Remote Management OS Rule Deﬁnition Port Protocol Direction Windows Server 2012 R2 WindowsFi rewall Remote Inbound rule for the WindowsFi Local: RPC TCP In Remote: Any Management rewall to be (RPC) remotely managed via RPC/TCP. WindowsFi rewall Inbound rule for Remote the RPCSS Management service to Local: RPC- EPMap Remote: Any TCP In (RPC-EPMAP) allow RPC/ TCP traﬃc for the Windows Firewall. WindowsFeature Experience Pack 83 AWS Windows AMIs Reference WindowsRemote Management OS Rule Deﬁnition Port Protocol Direction Windows Server 2012 WindowsRe mote Inbound rule for Local: 5985 TCP In Management WindowsRe (HTTP-In) mote Remote: Any Managemen t via WS- Manage ment. Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows Server 2022 For more information about Amazon EC2 security groups, see Amazon EC2 Security Groups for WindowsInstances. Updates applied for AWS Windows AMIs To help ensure a smooth and consistent launch experience, AWS Windows AMIs include the following updates for initialization, installation, and conﬁguration. Note When you launch an instance from an Amazon managed AWS Windows AMI, the root device for the Windows instance is an Amazon Elastic Block Store (Amazon EBS) volume. AWS Windows AMIs don't support instance store for the root device. WindowsRemote Management 84 AWS Windows AMIs Clean and prepare Description Check for pending ﬁle renames or reboots, and reboot as needed Delete .dmp ﬁles Delete logs (event logs, Systems Manager, EC2Conﬁg) Delete temporary folders and ﬁles for Sysprep Perform virus scan Pre-compile queued .NET assemblies (before Sysprep) Restore default values for Microsoft browsers Reset the Windows wallpaper Run Sysprep Set EC2Launch v1 to run at the next launch Run Windows maintenance tools Reference Applies to All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs Windows Server 2016 and 2019 Windows Server 2012 R2 and later Clear recent history (Start menu, Windows Explorer, and more) Windows Server 2012 R2 and Restore default values for EC2Conﬁg Install and conﬁgure Description Disable Secure Time Seeding earlier Windows Server 2012 R2 and earlier Applies to All AMIs Updates applied for AWS Windows AMIs 85 AWS Windows AMIs Description Add links to the Amazon EC2 Windows Guide Reference Applies to All AMIs Attach instance storage volumes to extended mount points All AMIs Install the current AWS Tools for Windows PowerShell All AMIs Install the current AWS CloudFormation bootstrap scripts All AMIs Disable RunOnce for Internet Explorer Enable remote PowerShell Disable hibernation and delete the hibernation ﬁle All AMIs All AMIs All AMIs Disable the Connected User Experiences and Telemetry service All AMIs Set the performance options for best performance Set the power setting to high performance Disable the screen saver password Set the RealTimeIsUniversal registry key Set the timezone to UTC Disable Windows updates and notiﬁcations Run Windows Update and reboot until there are no pending updates All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs All AMIs Set the display in all power schemes to never turn oﬀ All AMIs Set the PowerShell execution policy to "Unrestricted" All AMIs Updates applied for AWS Windows AMIs 86 AWS Windows AMIs Description If Microsoft SQL Server is installed: Reference Applies to All AMIs • • • • Install service packs Conﬁgure to start automatically Add BUILTIN\Administrators to the SysAdmin role Open TCP port 1433 and UDP port 1434 Conﬁgure a paging ﬁle on the system volume as follows: All AMIs Windows Server 2016 and later - Managed by the system Windows Server 2012 R2 - Initial size and max size are 8 GB • • • Windows Server 2012 and earlier - Initial size is 512 MB, max size is 8 GB Install the current EC2Launch v2 and SSM Agent Install the current EC2Launch v1 and SSM Agent Install the current SRIOV drivers Install the current EC2WinUtil driver Install the current EC2Conﬁg and SSM Agent Install the current AWS PV,
windows-ami-reference-016	windows-ami-reference.pdf	16	Open TCP port 1433 and UDP port 1434 Conﬁgure a paging ﬁle on the system volume as follows: All AMIs Windows Server 2016 and later - Managed by the system Windows Server 2012 R2 - Initial size and max size are 8 GB • • • Windows Server 2012 and earlier - Initial size is 512 MB, max size is 8 GB Install the current EC2Launch v2 and SSM Agent Install the current EC2Launch v1 and SSM Agent Install the current SRIOV drivers Install the current EC2WinUtil driver Install the current EC2Conﬁg and SSM Agent Install the current AWS PV, ENA, and NVMe drivers Windows Server 2022 and later Windows Server 2016 and 2019 Windows Server 2012 R2 and later Windows Server 2008 R2 and later Windows Server 2012 R2 and earlier Windows Server 2008 R2 and later Updates applied for AWS Windows AMIs 87 AWS Windows AMIs Description Allow ICMP traﬃc through the ﬁrewall Reference Applies to Windows Server 2012 R2 and earlier Conﬁgure an additional system managed paging ﬁle on Z:, if available Windows Server 2012 R2 and earlier Windows Server 2012 R2 and earlier Windows Server 2008 SP2 and earlier Windows Server 2008 SP2 and R2 Windows Server 2008 SP2 and R2 Enable ﬁle and printer sharing Install the current Citrix PV driver Install PowerShell 2.0 and 3.0 Apply the following hotﬁxes: • • • • • MS15-011 KB2582281 KB2634328 KB2394911 KB2780879 Changes in Windows Server AMIs by OS version AWS provides AMIs for Windows Server 2016 and later. These AMIs include the following high-level changes between AWS Windows AMIs for diﬀerent Windows operating system versions: Windows Server 2025 • Windows Server 2025 AMIs use UEFI boot mode by default, except for Windows Server 2025 AMIs named BIOS-Windows_Server-2025-English-Full-Base. Changes in Windows Server AMIs by OS version 88 AWS Windows AMIs Note Reference EC2 metal instance sizes and some EC2 instance types do not support UEFI boot mode for Windows Server. To launch Windows Server 2025 on these instances, you must use the AWS managed BIOS-Windows_Server-2025-English-Full-Base AMI, or an AMI that is based on that image. For more information about UEFI requirements, Requirements for UEFI boot mode in the Amazon EC2 User Guide. • Windows Server 2025 AMIs support Nitro EC2 instance types only. • Windows Server 2025 AMIs use gp3 EBS volume types by default. • Windows Credential Guard is not supported on AWS Windows Server 2025 AMIs. Windows Server 2016-2022 • To accommodate the change from .NET Framework to .NET Core, the EC2Conﬁg service has been deprecated on Windows Server 2016 AMIs and replaced by EC2Launch. EC2Launch is a bundle of Windows PowerShell scripts that perform many of the tasks performed by the EC2Conﬁg service. For more information, see Conﬁgure a Windows instance using EC2Launch. EC2Launch v2 replaces EC2Launch in Windows Server 2022 and later. For more information, see Conﬁgure a Windows instance using EC2Launch v2. • On earlier versions of Windows Server AMIs, you can use the EC2Conﬁg service to join an EC2 instance to a domain and conﬁgure integration with Amazon CloudWatch. On Windows Server 2016 and later AMIs, you can use the CloudWatch agent to conﬁgure integration with Amazon CloudWatch. For more information about conﬁguring instances to send log data to CloudWatch, see Collect Metrics and Logs from Amazon EC2 Instances and On-Premises Servers with the CloudWatch Agent. For information about joining an EC2 instance to a domain, see Join an Instance to a Domain Using the AWS-JoinDirectoryServiceDomain JSON Document in the AWS Systems Manager User Guide. Other diﬀerences Note the following additional important diﬀerences for instances created from Windows Server 2016 and later AMIs. • By default, EC2Launch does not initialize secondary EBS volumes. You can conﬁgure EC2Launch to initialize disks automatically by either scheduling the script to run or by calling EC2Launch in Changes in Windows Server AMIs by OS version 89 AWS Windows AMIs Reference user data. For the procedure to initialize disks using EC2Launch, see "Initialize Drives and Drive Letter Mappings" in Conﬁgure EC2Launch. • If you previously enabled CloudWatch integration on your instances by using a local conﬁguration ﬁle (AWS.EC2.Windows.CloudWatch.json), you can conﬁgure the ﬁle to work with the SSM Agent on instances created from Windows Server 2016 and later AMIs. AWS Windows AMI version history The following tables summarize the changes to each release of the AWS Windows AMIs. Note that some changes apply to all AWS Windows AMIs, while others apply to only a subset of these AMIs. For more information about components included in these AMIs, see the following: • EC2Launch v2 version history • EC2Launch v1 version history • EC2Conﬁg version history • Systems Manager SSM Agent Release Notes • Amazon ENA driver versions • AWS NVMe driver versions • Paravirtual drivers for Windows instances • AWS Tools for PowerShell Change Log Monthly AMI
windows-ami-reference-017	windows-ami-reference.pdf	17	and later AMIs. AWS Windows AMI version history The following tables summarize the changes to each release of the AWS Windows AMIs. Note that some changes apply to all AWS Windows AMIs, while others apply to only a subset of these AMIs. For more information about components included in these AMIs, see the following: • EC2Launch v2 version history • EC2Launch v1 version history • EC2Conﬁg version history • Systems Manager SSM Agent Release Notes • Amazon ENA driver versions • AWS NVMe driver versions • Paravirtual drivers for Windows instances • AWS Tools for PowerShell Change Log Monthly AMI updates for 2025 (to date) For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2025 (KB894199) on the Microsoft website. Release Changes 2025.04.09 All AMIs AWSPowerShell version 4.1.791 cfn-bootstrap v2.0.34 • • • AWS Windows AMI version history 90 AWS Windows AMIs Reference Release Changes EC2Launch v2 version 2.0.2107 SSM Agent version 3.3.1957.0 SQL Server CUs installed: • SQL_2022: CU 18 • • • Windows Security Updates current to April 8, 2025 Previous versions of Amazon-published AWS Windows AMIs dated January 15, 2024 and earlier will be made private after May 13, 2025, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 91 AWS Windows AMIs Reference Release Changes 2025.03.12 All AMIs AWSPowerShell version 4.1.771 cfn-bootstrap v2.0.33 EC2Launch v1 version 1.3.2005119 EC2Launch v2 version 2.0.2081 SQL Server CUs installed: • SQL_2019: CU 32 • • • • • • Windows Security Updates current to March 11, 2025 Previous versions of Amazon-published AWS Windows AMIs dated December 13, 2024 and earlier will be made private after April 8, 2025, 10 AM Paciﬁc. Note Beginning March 2025, R Services and Machine Learning Services with R and Python runtimes are no longer enabled by default on SQL Server 2016, 2017, and 2019 AMIs. These features include runtimes that are not maintained through SQL server cumulative updates. You can enable these features on your instance launched from our SQL Server AMIs using the SQL installation media included at C:\SQLServerSetup. Monthly AMI updates for 2025 (to date) 92 AWS Windows AMIs Reference Release Changes 2025.02.13 All AMIs AWSPowerShell version 4.1.749 SSM Agent version 3.3.1611.0 SQL Server CUs installed: • SQL_2022: CU 17 • • • • Windows Security Updates current to February 12, 2025 Previous versions of Amazon-published AWS Windows AMIs dated November 19, 2024 and earlier will be made private after March 11, 2025, 10 AM Paciﬁc. 2025.01.15 All AMIs • • • • AWSPowerShell version 4.1.731 cfn-init v2.0.32 Elastic Network Adapter (ENA) version 2.9.0 Windows Security Updates current to January 14, 2025 Previous versions of Amazon-published AWS Windows AMIs dated October 9, 2024 and earlier will be made private after February 11, 2025, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 93 AWS Windows AMIs Reference Monthly AMI updates for 2024 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2024 on the Microsoft website. Release Changes 2024.12.13 All AMIs AWSPowerShell version 4.1.713 AWS PV driver version 8.5.0 SQL Server CUs installed: • SQL_2019: CU 30 • • • • Windows Security Updates current to December 10, 2024 Previous versions of Amazon-published AWS Windows AMIs dated September 11, 2024 and earlier will be made private after January 15, 2025, 10 AM Paciﬁc. 2024.11.19 All AMIs • SSM Agent version 3.3.1345.0 This SSM Agent version addresses an issue where Windows Server 2025 instances may not connect to Systems Manager Sessions Manager or Fleet Manager RDP. Monthly AMI updates for 2025 (to date) 94 AWS Windows AMIs Reference Release Changes Note This is a partial release. Only Windows Server 2025 AMIs are included in this release. 2024.11.13 All AMIs AWSPowerShell version 4.1.694 AWS NVMe driver version 1.6.0 cfn-init v2.0.31 EC2Launch v1 version 1.3.2005065 SSM Agent version 3.3.1230.0 SQL Server CUs installed: • • • • SQL_2022: GDR KB5046862 SQL_2019: CU 29 + GDR KB5046860 SQL_2017: GDR KB5046858 SQL_2006_SP3: KB5046855 • • • • • • • Windows Security Updates current to Nobember 12, 2024 Previous versions of Amazon-published AWS Windows AMIs dated August 14, 2024 and earlier will be made private after December 11, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 95 AWS Windows AMIs Reference Release Changes 2024.11.04 Release AMIs for Windows Server 2025. Windows Server 2025 AMIs are conﬁgured with UEFI boot-mode, gp3 root volumes, and have IMDS V2 enabled by default. A BIOS conﬁgured AMI is available for use on Bare Metal platforms and Nitro instances where UEFI support is not available. • AWS.Tools version 4.1.691 AWS.Tools PowerShell modules is a modularized version of the PowerShell toolset that reduces module load time. For more informati on see the AWS Tools for PowerShell User Guide. • • •
windows-ami-reference-018	windows-ami-reference.pdf	18	2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 95 AWS Windows AMIs Reference Release Changes 2024.11.04 Release AMIs for Windows Server 2025. Windows Server 2025 AMIs are conﬁgured with UEFI boot-mode, gp3 root volumes, and have IMDS V2 enabled by default. A BIOS conﬁgured AMI is available for use on Bare Metal platforms and Nitro instances where UEFI support is not available. • AWS.Tools version 4.1.691 AWS.Tools PowerShell modules is a modularized version of the PowerShell toolset that reduces module load time. For more informati on see the AWS Tools for PowerShell User Guide. • • • SSM Agent version 3.3.1230.0 You may encounter an issue connecting AWS Systems Manager Sessions Manager to a Windows Server 2025 instance. To address this issue, log onto the instance, then navigate to Settings > Apps > Optional Features , and add WMIC. Restart the SSM Agent service or reboot the instance, and Sessions Manager should connect. Windows Credential Guard is not supported on EC2 instances running Windows Server 2025. Monthly AMI updates for 2025 (to date) 96 AWS Windows AMIs Reference Release Changes 2024.10.09 All AMIs • • • • • • AWS Tools for Windows PowerShell version 4.1.667 EC2Launch v2 version 2.0.2046 Elastic Network Adapter (ENA) version 2.8.0 SSM Agent version 3.3.859.0 SQL Server CUs installed: • • • • SQL_2022: CU15 + GDR KB5046059 SQL_2019: GDR KB5046060 SQL_2017: GDR KB5046061 SQL_2016_SP3: GDR KB5046063 Windows Security Updates current to October 8, 2024 Previous versions of Amazon-published AWS Windows AMIs dated July 10, 2024 and earlier will be made private after November 11, 2024, 10 AM Paciﬁc. Note Starting in October, default root volume sizes on some AMIs changed to provide additional free space for the conﬁguration changes applied to the images. For all Core or Full Base Images, including EC2Launch v2 and TPM versions, the root volume size remains 30GB. For all Windows AMIs with SQL Server, the root Monthly AMI updates for 2025 (to date) 97 AWS Windows AMIs Reference Release Changes volume size is now 75GB. For all other Windows AMI conﬁgurations, the root volume size is now 50GB. 2024.09.11 All AMIs AWS Tools for Windows PowerShell version 4.1.648 SQL Server CUs installed: SQL_2022: GDR KB5042578 SQL_2019: GDR KB5042749 SQL_2017: GDR KB5042215 • • • • SQL_2016_SP3: GDR KB5042207 • • • Windows Security Updates current to September 10, 2024 Previous versions of Amazon-published AWS Windows AMIs dated June 13, 2024 and earlier will be made private after October 7, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 98 AWS Windows AMIs Reference Release Changes 2024.08.14 All AMIs • • • • • AWS Tools for Windows PowerShell version 4.1.628 EC2Launch v1 version 3.2005008 EC2Launch v2 version 2.0.1981 SQL Server CUs installed: • • • • SQL_2022: CU 14 SQL_2019: CU 28 SQL_2017: GDR KB5040940 SQL_2016_SP3: GDR KB5040946 Windows Security Updates current to August 13, 2024 Previous versions of Amazon-published AWS Windows AMIs dated May 15, 2024 and earlier will be made private after September 9, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 99 AWS Windows AMIs Reference Release Changes 2024.07.10 All AMIs • • • • • • • AWS Tools for Windows PowerShell version 4.1.611 EC2Launch v1 version 3.2004959 EC2Launch v2 version 2.0.1948 SSM Agent version 3.3.551.0 SQL Server CUs installed: • SQL_2019: CU 27 NVIDIA Tesla version 475.14 Windows Security Updates current to July 10, 2024 Previous versions of Amazon-published AWS Windows AMIs dated April 10, 2024 and earlier will be made private after August 12, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 100 AWS Windows AMIs Reference Release Changes 2024.06.13 All AMIs • • • • • • • • • AWS Tools for Windows PowerShell version 4.1.593 EC2Launch v1 version 3.2004891 EC2Launch v2 version 2.0.1924 EC2WinUtil version 3.0.0 Elastic Network Adapter (ENA) version 2.7.0 SSM Agent version 3.3.484.0 SQL Server CUs installed: • SQL_2022: CU 13 NVIDIA Tesla version 475.06 Windows Security Updates current to June 11, 2024 Previous versions of Amazon-published AWS Windows AMIs dated March 13, 2024 and earlier will be made private after July 8, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 101 AWS Windows AMIs Reference Release Changes 2024.05.15 All AMIs • • • • • AWS Tools for Windows PowerShell version 4.1.575 EC2Launch v2 version 2.0.1881 SSM Agent version 3.3.380.0 SQL Server CUs installed: • • SQL_2022: GDR KB5036343 SQL_2019: CU26 Windows Security Updates current to May 14, 2024 Previous versions of Amazon-published AWS Windows AMIs dated February 14, 2024 and earlier will be made private after June 10, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 102 AWS Windows AMIs Reference Release Changes 2024.04.10 All AMIs • • • • Windows Security Updates current to April 9, 2024
windows-ami-reference-019	windows-ami-reference.pdf	19	Windows AMIs Reference Release Changes 2024.05.15 All AMIs • • • • • AWS Tools for Windows PowerShell version 4.1.575 EC2Launch v2 version 2.0.1881 SSM Agent version 3.3.380.0 SQL Server CUs installed: • • SQL_2022: GDR KB5036343 SQL_2019: CU26 Windows Security Updates current to May 14, 2024 Previous versions of Amazon-published AWS Windows AMIs dated February 14, 2024 and earlier will be made private after June 10, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 102 AWS Windows AMIs Reference Release Changes 2024.04.10 All AMIs • • • • Windows Security Updates current to April 9, 2024 AWS Tools for Windows PowerShell version 4.1.551 SSM Agent version 3.3.131.0 SQL Server CUs installed: • SQL_2022: CU12 Previous versions of Amazon-published AWS Windows AMIs dated January 16, 2024 and earlier will be made private after May 13, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 103 AWS Windows AMIs Reference Release Changes 2024.03.13 All AMIs • • • • • • • Windows Security Updates current to March 12, 2024 AWS Tools for Windows PowerShell version 4.1.530 EC2Launch v2 version 2.0.1815 SSM Agent version 3.2.2303.0 NVIDIA GRID Driver version 538.33 NVIDIA Tesla Driver version 474.82 SQL Server CUs installed: • SQL_2019: CU25 Note To ensure that you always receive valid time from your conﬁgure d Network Time Protocol (NTP) service, Secure Time Seeding (STS) is disabled on all AWS Windows AMIs from this version forward. Amazon Time Sync Service is the default NTP service for all AWS Windows AMIs that Amazon provides. Previous versions of Amazon-published AWS Windows AMIs dated December 13, 2023 and earlier will be made private after April 8, 2024, 10 AM Paciﬁc. Monthly AMI updates for 2025 (to date) 104 AWS Windows AMIs Reference Release Changes 2024.02.14 All AMIs • • • • • Windows Security Updates current to Febuary 13, 2024 AWS Tools for Windows PowerShell version 4.1.512 cfn-init version 2.0.29 SSM Agent version 3.2.2222.0 SQL Server CUs installed: • SQL_2022: CU11 Previous versions of Amazon-published AWS Windows AMIs dated November 15, 2023 and earlier will be made private after March 11, 2024, 10 AM Paciﬁc. 2024.01.16 All AMIs • • EC2Launch v2 version 2.0.1739 EC2Launch v1 v1 version 1.3.2004617 Monthly AMI updates for 2025 (to date) 105 AWS Windows AMIs Reference Release Changes 2024.01.10 (Deprecated) Note Due to functional issues with EC2Launch v1 and EC2Launch v2, this AMI version is marked as deprecated. The AMIs are still available for launch, and are described by directly referencing their AMI ID. However, they will no longer appear in search results for public AMIs. We recommend that you use the latest AMI version, dated 2024.01.1 6. All AMIs • • • • • Windows Security Updates current to January 9, 2024 Note: Due to a known update installation issue, we excluded the standalone Windows update KB5034439 on Windows Server 2022 Core AMIs. The update only applies to Windows installations with a separate WinRE partition. These partitions are not included with our EC2 Windows Server AMIs. For more information, see KB5042322: Windows Recovery Environment update for Windows Server 2022: January 9, 2024 on the Microsoft website. AWS Tools for PowerShell version 4.1.486 EC2Launch v1 v1 version 1.3.2004592 EC2Launch v2 version 2.0.1702 SQL Server CUs installed: • SQL_2019: CU24 Monthly AMI updates for 2025 (to date) 106 AWS Windows AMIs Reference Release Changes Previous versions of Amazon-published AWS Windows AMIs dated October 11, 2023 and earlier will be made private after February 12th 2024, 10 AM Paciﬁc. Monthly AMI updates for 2023 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2023 on the Microsoft website. Release Changes 2023.12.13 All AMIs • • • • • • Windows Security Updates current to December 12, 2023 AWS Tools for PowerShell version 4.1.468 AMD Radeon Pro Driver version 22.10.01.12 NVIDIA GRID Driver version 537.70 NVIDIA Tesla Driver version 474.64 SQL Server CUs installed: • SQL_2022: CU10 Previous versions of Amazon-published AWS Windows AMIs dated Sep tember 13, 2023 and earlier will be made private after January 8th 2024, 10 AM Paciﬁc. 2023.11.15 Monthly AMI updates for 2025 (to date) 107 AWS Windows AMIs Release Changes All AMIs Reference • • • • • • Windows Security Updates current to November 14, 2023 AWS Tools for PowerShell version 4.1.447 EC2Launch v1 version 1.3.2004491 SSM Agent version 3.2.1705.0 SQL Server CUs installed: • • SQL_2022: CU9 SQL_20219: CU23 SQL Server GDRs installed: • • • SQL 2017: KB5029376 SQL 2016: KB5029186 SQL 2014: KB5029185 Previous versions of Amazon-published AWS Windows AMIs dated August 10, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 108 AWS Windows AMIs Reference Release Changes 2023.10.11 All AMIs • • • • • • • Windows Security Updates current to October
windows-ami-reference-020	windows-ami-reference.pdf	20	• • • • • • Windows Security Updates current to November 14, 2023 AWS Tools for PowerShell version 4.1.447 EC2Launch v1 version 1.3.2004491 SSM Agent version 3.2.1705.0 SQL Server CUs installed: • • SQL_2022: CU9 SQL_20219: CU23 SQL Server GDRs installed: • • • SQL 2017: KB5029376 SQL 2016: KB5029186 SQL 2014: KB5029185 Previous versions of Amazon-published AWS Windows AMIs dated August 10, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 108 AWS Windows AMIs Reference Release Changes 2023.10.11 All AMIs • • • • • • • Windows Security Updates current to October 10, 2023 cfn-init version 2.0.28 EC2Launch v1 version 1.3.2004438 EC2Launch v2 version 2.0.1643 SSM version 3.2.1630.0 AWS Tools for PowerShell version 4.1.426 SQL Server CUs installed: • SQL_2022: CU8 Previous versions of Amazon-published AWS Windows AMIs dated July 12, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 109 AWS Windows AMIs Reference Release Changes 2023.09.13 All AMIs • • • • • • Windows Security Updates current to September 12, 2023 EC2Launch v2 version 2.0.1580 SSM version 3.2.1377.0 AWS Tools for PowerShell version 4.1.407 AWS NVMe driver version 1.5.0 SQL Server CUs installed: • • SQL_2022: CU7 SQL_2019: CU22 Windows Server 2012 RTM and Window Server 2012 R2 will reach End of Support (EOS) on October 10, 2023 and will no longer receive regular security updates from Microsoft. On this date, AWS will no longer publish or distribute Windows Server 2012 RTM or Windows Server 2012 R2 AMIs. Existing instances running Windows Server 2012 RTM and Windows Server 2012 R2 will not be impacted. Custom AMIs in your account will also not be impacted. You can continue to use them normally after the EOS date. Previous versions of Amazon-published AWS Windows AMIs dated June 14, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 110 AWS Windows AMIs Reference Release Changes 2023.08.10 All AMIs • • • • • • • Windows Security Updates current to August 8, 2023 AWS Tools for PowerShell version 4.1.383 EC2Conﬁg version 4.9.5467 SSM version 3.1.2282.0 AWS ENA version 2.6.0 cfn-init version 2.0.26 SQL Server CUs installed: • SQL_2022: CU6 Windows Server 2012 RTM and Window Server 2012 R2 will reach End of Support (EOS) on October 10, 2023 and will no longer receive regular security updates from Microsoft. On this date, AWS will no longer publish or distribute Windows Server 2012 RTM or Windows Server 2012 R2 AMIs. Existing instances running Windows Server 2012 RTM and Windows Server 2012 R2 will not be impacted. Custom AMIs in your account will also not be impacted. You can continue to use them normally after the EOS date. Previous versions of Amazon-published AWS Windows AMIs dated May 10, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 111 AWS Windows AMIs Reference Release Changes 2023.07.12 All AMIs • • • • • Windows Security Updates current to July 11, 2023 AWS Tools for Windows PowerShell version 4.1.366 EC2Launch v1 version 1.3.2004256 EC2Launch v2 version 2.0.1521 SQL Server CUs installed: • • SQL_2022: CU5 SQL_2019: CU21 .NET Framework 3.5 is now enabled in Windows Server 2012 R2 AMIs due to Microsoft security updates. If these updates are applied before .NET 3.5 is enabled, it is no longer possible to enable the feature. If you prefer to disable .NET 3.5, you can do so through Server Manager or dism commands. Previous versions of Amazon-published AWS Windows AMIs dated April 12, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 112 AWS Windows AMIs Reference Release Changes 2023.06.14 All AMIs Windows Security Updates current to June 13, 2023 AWS Tools for Windows PowerShell version 4.1.346 • • • SQL Server CUs installed: • SQL_2022: CU4 The AWS Tools for Windows installation package has been deprecated, and no longer appears as an installed program in AWS Windows AMIs provided by AWS. The AWSPowerShell Module is now installed at C:\Progra . mFiles\WindowsPowerShell\Modules\AWSPowerShell The .NET SDK remains located at C:\ProgramFiles (x86)\AWS SDK for .NET. For more information see the blog announcement. Windows Server 2012 RTM and Windows Server 2012 R2 will reach End of Support (EOS) on October 10, 2023 and will no longer receive regular security updates from Microsoft. On this date, AWS will no longer publish or distribute Windows Server 2012 RTM or Windows Server 2012 R2 AMIs. Existing RTM/R2 instances and custom AMIs in your account will not be impacted, and you can continue to use them after the EOS date. For more information about Microsoft End of Support on AWS, including upgrade and import options, as well as a full list of AMIs that will no longer be published or distributed on October 10, 2023, see the End of Support for Microsoft
windows-ami-reference-021	windows-ami-reference.pdf	21	on October 10, 2023 and will no longer receive regular security updates from Microsoft. On this date, AWS will no longer publish or distribute Windows Server 2012 RTM or Windows Server 2012 R2 AMIs. Existing RTM/R2 instances and custom AMIs in your account will not be impacted, and you can continue to use them after the EOS date. For more information about Microsoft End of Support on AWS, including upgrade and import options, as well as a full list of AMIs that will no longer be published or distributed on October 10, 2023, see the End of Support for Microsoft Products FAQ. Previous versions of Amazon-published AWS Windows AMIs dated March 15, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 113 AWS Windows AMIs Reference Release Changes 2023.05.10 All AMIs • • • • • Windows Security Updates current to May 9, 2023 AWS Tools for Windows PowerShell version 3.15.2072 EC2Launch v2 version 2.0.1303 cfn-init version 2.0.25 SQL Server CUs installed: • • SQL_2022: CU3 SQL_2019: CU20 Previous versions of Amazon-published AWS Windows AMIs dated February 15, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 114 AWS Windows AMIs Reference Release Changes 2023.04.12 All AMIs • • • • • Windows Security Updates current to April 11, 2023 AWS Tools for Windows PowerShell version 3.15.2035 AWS NVMe driver version 1.4.2 SQL Server CUs installed: • SQL_2022: CU 2 SSM version 3.1.2144.0 Windows Server 2016, 2019, and 2022 • Intel 82599 VF driver version 2.1.249.0 Windows Server 2012 R2 • Intel 82599 VF driver version 1.2.317.0 Previous versions of Amazon-published AWS Windows AMIs dated January 19, 2023 and earlier were made private. Monthly AMI updates for 2025 (to date) 115 AWS Windows AMIs Reference Release Changes 2023.03.15 All AMIs • • • • • • • • Windows Security Updates current to March 14, 2023 AWS Tools for Windows PowerShell version 3.15.1998 EC2Conﬁg version 4.9.5288 EC2Launch v1 version 1.3.2004052 EC2Launch v2 version 2.0.1245 cfn-init version 2.0.24 SQL Server CUs installed: • • SQL_2022: CU 1 SQL_2019: CU 19 SQL Server GDRs installed: • • • SQL_2017: KB5021126 SQL_2016: KB5021129 SQL_2014: KB5021045 Previous versions of Amazon-published AWS Windows AMIs dated Dec ember 28, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 116 AWS Windows AMIs Reference Release Changes 2023.02.15 All AMIs Windows Security Updates current to February 14, 2023 AWS Tools for Windows PowerShell version 3.15.1958 • • • AWS PV version 8.4.3 New AWS Windows AMIs • • • • TPM-Windows_Server-2019-English-Full-SQL_2019_Enterprise TPM-Windows_Server-2019-English-Full-SQL_2019_Standard TPM-Windows_Server-2022-English-Full-SQL_2022_Enterprise TPM-Windows_Server-2022-English-Full-SQL_2022_Standard New AWS Windows AMIs with Microsoft SQL Server with support for NitroTPM and UEFI Secure Boot have been released. The images include Windows Server 2019 or Windows Server 2022 with SQL Server 2019 or SQL Server 2022. Each SQL Server version is available in Standard and Enterprise editions. Previous versions of Amazon-published AWS Windows AMIs dated November 21, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 117 AWS Windows AMIs Reference Release Changes 2023.01.19 All AMIs • cfn-init version 2.0.21 Previous versions of Amazon-published AWS Windows AMIs dated October 27, 2022 and earlier were made private. 2023.01.11 All AMIs • • • • Windows Security updates current to January 10, 2023 AWS Tools for Windows PowerShell version 3.15.1919 EC2Launch v1 version 1.3.2003975 EC2Launch v2 version 2.0.1121 Monthly AMI updates for 2022 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2022 on the Microsoft website. Release Changes 2022.12.28 Windows Server 2016 and 2019 AMIs • EC2Launch v1 version 1.3.2003975 2022.12.14 All AMIs • Windows Security updates current to December 13th, 2022 Monthly AMI updates for 2025 (to date) 118 AWS Windows AMIs Reference Release Changes • • • • • • AWS Tools for Windows PowerShell version 3.15.1886 EC2Conﬁg version 4.9.5103 EC2Launch v1 version 1.3.2003961 EC2Launch v2 version 2.0.1082 SSM version 3.1.1856.0 cfn-init version 2.0.19 Monthly AMI updates for 2025 (to date) 119 AWS Windows AMIs Reference Release Changes 2022.11.21 New AWS Windows AMIs • • • • • • • • • • • • • • Windows_Server-2019-English-Full-SQL_2022_Enterprise Windows_Server-2019-English-Full-SQL_2022_Express Windows_Server-2019-English-Full-SQL_2022_Standard Windows_Server-2019-English-Full-SQL_2022_Web Windows_Server-2019-Japanese-Full-SQL_2022_Enterprise Windows_Server-2019-Japanese-Full-SQL_2022_Standard Windows_Server-2019-Japanese-Full-SQL_2022_Web Windows_Server-2022-English-Full-SQL_2022_Enterprise Windows_Server-2022-English-Full-SQL_2022_Express Windows_Server-2022-English-Full-SQL_2022_Standard Windows_Server-2022-English-Full-SQL_2022_Web Windows_Server-2022-Japanese-Full-SQL_2022_Enterprise Windows_Server-2022-Japanese-Full-SQL_2022_Standard Windows_Server-2022-Japanese-Full-SQL_2022_Web Previous versions of Amazon-published AWS Windows AMIs dated August 10, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 120 AWS Windows AMIs Reference Release Changes 2022.11.17 All AMIs • EC2Conﬁg version 4.9.5064. This is an out of band release for images that use EC2Conﬁg as the default launch agent. This includes all Windows Server 2012 RTM and Windows Server 2012 R2 AMIs. This release updates EC2Conﬁg to the latest version to improve support for our newest EC2 instance types. 2022.11.10 All AMIs • • • • • • Windows Security updates
windows-ami-reference-022	windows-ami-reference.pdf	22	Windows_Server-2022-English-Full-SQL_2022_Web Windows_Server-2022-Japanese-Full-SQL_2022_Enterprise Windows_Server-2022-Japanese-Full-SQL_2022_Standard Windows_Server-2022-Japanese-Full-SQL_2022_Web Previous versions of Amazon-published AWS Windows AMIs dated August 10, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 120 AWS Windows AMIs Reference Release Changes 2022.11.17 All AMIs • EC2Conﬁg version 4.9.5064. This is an out of band release for images that use EC2Conﬁg as the default launch agent. This includes all Windows Server 2012 RTM and Windows Server 2012 R2 AMIs. This release updates EC2Conﬁg to the latest version to improve support for our newest EC2 instance types. 2022.11.10 All AMIs • • • • • • Windows Security updates current to November 8th, 2022 AWS Tools for Windows PowerShell version 3.15.1846 EC2Launch v1 version 1.3.2003923 EC2Launch v2 version 2.0.1011 SQL Server CUs installed: • • SQL_2019: CU 18 SQL_2017: CU 31 cfn-init version 2.0.18 Monthly AMI updates for 2025 (to date) 121 AWS Windows AMIs Reference Release Changes 2022.10.27 All AMIs • Out-of-band updates applied to resolve issues resulting from October patches. For more information, see Windows release health on the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated July 13, 2022 and earlier were made private. 2022.10.12 All AMIs • • • • • Windows Security updates current to October 11th, 2022 AWS Tools for Windows PowerShell version 3.15.1809 EC2Launch v1 version 1.3.2003857 SSM version 3.1.1732.0 cfn-init version 2.0.16 Monthly AMI updates for 2025 (to date) 122 AWS Windows AMIs Reference Release Changes 2022.09.14 All AMIs • • • • Windows Security updates current to September 13th, 2022 AWS Tools for Windows PowerShell version 3.15.1772 EC2Launch v1 version 1.3.2003824 SQL Server CU installed: • SQL_2019: CU17 Previous versions of Amazon-published AWS Windows AMIs dated June 15, 2022 and earlier were made private. 2022.08.10 All AMIs Windows Security updates current to August 9th, 2022 AWS Tools for Windows PowerShell version 3.15.1737 cfn-init version 2.0.15 SSM version 3.1.1634.0 (only AMIs that include EC2Launch v1 v1 or v2) • • • • • SQL Server CU installed: • SQL_2017: CU30 Previous versions of Amazon-published AWS Windows AMIs dated May 25, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 123 AWS Windows AMIs Reference Release Changes 2022.07.13 All AMIs • • • • • • Windows Security updates current to July 12th, 2022 AWS Tools for Windows PowerShell version 3.15.1706 cfn-init version 2.0.12 EC2Launch v1 version 1.3.2003691 EC2Launch v2 version 2.0.863 SQL Server GDRs installed: • • • • SQL_2019: KB5014353 SQL_2017: KB5014553 SQL_2016: KB5014355 SQL_2014: KB5014164 Windows Server version 20H2 will reach end-of-support on August 9, 2022. Existing instances and custom images owned by your account that are based on Windows Server version 20H2 will not be impacted. If you would like to retain access to Windows Server version 20H2, create a custom image in your account prior to August 9, 2022. All public versions of the following images will be made private on the end-of-support date. • • Windows_Server-20H2-English-Core-Base Windows_Server-20H2-English-Core-ContainersLatest Monthly AMI updates for 2025 (to date) 124 AWS Windows AMIs Reference Release Changes Previous versions of Amazon-published AWS Windows AMIs dated April 13, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 125 AWS Windows AMIs Reference Release Changes 2022.06.15 All AMIs • • • • • • Windows Security updates current to June 14th, 2022 AWS Tools for Windows PowerShell version 3.15.1678 AWS NVMe version 1.4.1 EC2Conﬁg version 4.9.4588 EC2Launch v1 version 1.3.2003639 SSM version 3.1.1188.0 Microsoft SQL Server 2012 is reaching end-of-support on July 12th, 2022. All public versions of the following images have been made private. Existing instances and custom images owned by your account that are based on Windows Server images containing SQL Server 2012 will not be impacted. • • • • • • • • Windows_Server-2012-R2_RTM-English-64Bit-SQL_2012_SP4_Enterpris e-* Windows_Server-2012-RTM-English-64Bit-SQL_2012_SP4_Enterprise-* Windows_Server-2012-RTM-English-64Bit-SQL_2012_SP4_Express-* Windows_Server-2012-RTM-English-64Bit-SQL_2012_SP4_Standard-* Windows_Server-2012-RTM-English-64Bit-SQL_2012_SP4_Web-* Windows_Server-2012-RTM-Japanese-64Bit-SQL_2012_SP4_Express-* Windows_Server-2012-RTM-Japanese-64Bit-SQL_2012_SP4_Standard-* Windows_Server-2012-RTM-Japanese-64Bit-SQL_2012_SP4_Web-* Monthly AMI updates for 2025 (to date) 126 AWS Windows AMIs Reference Release Changes • • Windows_Server-2016-English-64Bit-SQL_2012_SP4_Enterprise-* Windows_Server-2016-English-Full-SQL_2012_SP4_Standard-* For more information on Windows Server product lifecycles, please consult the following Microsoft documentation and AWS Microsoft FAQ: Microsoft SQL Server 2012 • • End-of-Support for Microsoft Products 2022.05.25 All AMIs • Out-of-band updates applied to resolve issues resulting from May patches. For more information, see Windows release health on the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated February 10, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 127 AWS Windows AMIs Reference Release Changes 2022.05.11 All AMIs • • • • • Windows Security updates current to May 10th, 2022 AWS Tools for Windows PowerShell version 3.15.1643 AWS PV version 8.4.2 AWS ENA version 2.4.0 SQL Server CUs installed: • • SQL_2019: CU 16 SQL_2017: CU 29 2022.05.05 New AWS Windows AMIs New AWS Windows AMIs with support for NitroTPM and UEFI Secure Boot have been released. These images feature EC2Launch
windows-ami-reference-023	windows-ami-reference.pdf	23	the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated February 10, 2022 and earlier were made private. Monthly AMI updates for 2025 (to date) 127 AWS Windows AMIs Reference Release Changes 2022.05.11 All AMIs • • • • • Windows Security updates current to May 10th, 2022 AWS Tools for Windows PowerShell version 3.15.1643 AWS PV version 8.4.2 AWS ENA version 2.4.0 SQL Server CUs installed: • • SQL_2019: CU 16 SQL_2017: CU 29 2022.05.05 New AWS Windows AMIs New AWS Windows AMIs with support for NitroTPM and UEFI Secure Boot have been released. These images feature EC2Launch v2 as the default launch agent. They are available to launch on any instance type that supp orts NitroTPM and UEFI boot mode. • • • • • • TPM-Windows_Server-2022-English-Core-Base-2022.05.05 TPM-Windows_Server-2022-English-Full-Base-2022.05.05 TPM-Windows_Server-2019-English-Core-Base-2022.05.05 TPM-Windows_Server-2019-English-Full-Base-2022.05.05 TPM-Windows_Server-2016-English-Core-Base-2022.05.05 TPM-Windows_Server-2016-English-Full-Base-2022.05.05 Monthly AMI updates for 2025 (to date) 128 AWS Windows AMIs Reference Release Changes 2022.04.13 All AMIs • • Windows Security updates current to April 12th, 2022 AWS Tools for Windows PowerShell version 3.15.1620 Previous versions of Amazon-published AWS Windows AMIs dated January 21, 2022 and earlier were made private. After June 2022, we will no longer release updated versions of the following images that include SQL Server 2016 SP2. SQL Server SP3 AMIs are available and will continue to be updated and released monthly. Windows_Server-2019-English-Full-SQL_2016_SP2_Web Windows_Server-2019-English-Full-SQL_2016_SP2_Standard Windows_Server-2019-English-Full-SQL_2016_SP2_Express Windows_Server-2019-English-Full-SQL_2016_SP2_Enterprise Windows_Server-2016-Korean-Full-SQL_2016_SP2_Standard Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Web Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Standard Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Express Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Enterprise Windows_Server-2016-English-Full-SQL_2016_SP2_Web Windows_Server-2016-English-Full-SQL_2016_SP2_Standard • • • • • • • • • • • • Monthly AMI updates for 2025 (to date) 129 AWS Windows AMIs Reference Release Changes Windows_Server-2016-English-Full-SQL_2016_SP2_Express Windows_Server-2016-English-Full-SQL_2016_SP2_Enterprise Windows_Server-2016-English-Core-SQL_2016_SP2_Web Windows_Server-2016-English-Core-SQL_2016_SP2_Standard Windows_Server-2016-English-Core-SQL_2016_SP2_Express Windows_Server-2016-English-Core-SQL_2016_SP2_Enterprise Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2_Web Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2 _Standard Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2_Express Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2_Enterpri se Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Web Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Standard Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Express Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Enterprise • • • • • • • • • • • • • Monthly AMI updates for 2025 (to date) 130 AWS Windows AMIs Reference Release Changes 2022.03.09 All AMIs • • • • • • Windows Security updates current to March 8th, 2022 AWS Tools for Windows PowerShell version 3.15.1583 AWS ENA version 2.2.3 (reverted due to potential performance degradati on on 6th generation EC2 instances) EC2Conﬁg version 4.9.4556 SSM version 3.1.1045.0 SQL Server CUs installed: • SQL_2019: CU 15 Previous versions of Amazon-published AWS Windows AMIs dated Dece mber 12, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 131 AWS Windows AMIs Reference Release Changes 2022.02.10 All AMIs • • • • • • • • Windows Security updates current to February 8th, 2022 AWS Tools for Windows PowerShell version 3.15.1546 cfn-init version 2.0.10 EC2Conﬁg version 4.9.4536 EC2Launch v1 version 1.3.2003498 EC2Launch v2 version 2.0.698 SSM version 3.1.804.0 SQL Server CUs installed: • SQL_2017: CU 28 Previous versions of Amazon-published AWS Windows AMIs dated Nove mber 16, 2021 and earlier were made private. 2022.01.19 All AMIs • Out-of-band updates applied to resolve issues resulting from January patches. For more information, see Windows release health on the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated October 13, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 132 AWS Windows AMIs Reference Release Changes 2022.01.12 All AMIs • • • • Windows Security updates current to January 11th, 2022 AWS Tools for Windows PowerShell version 3.15.1511 AWS PV version 8.4.1 SQL Server CUs installed: • SQL_2019: CU 14 Monthly AMI updates for 2021 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2021 on the Microsoft website. Release Changes 2021.12.15 All AMIs • • • • Windows Security updates current to December 14th, 2021 AWS Tools for Windows PowerShell version 3.15.1494 AWS NVMe version 1.4.0 SQL Server CUs installed: • • SQL_2017: CU 27 SQL_2019: CU 13 Monthly AMI updates for 2025 (to date) 133 AWS Windows AMIs Reference Release Changes Previous versions of Amazon-published AWS Windows AMIs dated Sep tember 15, 2021 and earlier were made private. 2021.11.16 Windows Server 2022 and EC2Launch v1V2-* AMIs • EC2Launch v2 version 2.0.674 Windows Server 2004 reached End-of-support on December 14, 2021. All public versions of the following images have been made private. Existing instances and custom images owned by your account that are based on Windows Server 2004 will not be impacted. • • Windows_Server-2004-English-Core-Base Windows_Server-2004-English-Core-ContainersLatest Monthly AMI updates for 2025 (to date) 134 AWS Windows AMIs Reference Release Changes 2021.11.10 All AMIs • • • • Windows Security updates current to November 9th, 2021 AWS Tools for Windows PowerShell version 3.15.1451 AWS ENA version 2.2.4 SQL Server CUs installed: • SQL_2017: CU 26 New AWS Windows AMIs • • • • • • Windows_Server-2022-Japanese-Full-SQL_2019_Enterprise-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2019_Standard-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2019_Web-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Enterprise-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Standard-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Web-2021.11.10 Monthly AMI updates for 2025 (to date) 135 AWS Windows AMIs Reference Release Changes 2021.10.13 All AMIs • • • Windows Security updates current to October 12, 2021 AWS Tools for Windows PowerShell version 3.15.1421 SSM version 3.1.338.0
windows-ami-reference-024	windows-ami-reference.pdf	24	updates for 2025 (to date) 134 AWS Windows AMIs Reference Release Changes 2021.11.10 All AMIs • • • • Windows Security updates current to November 9th, 2021 AWS Tools for Windows PowerShell version 3.15.1451 AWS ENA version 2.2.4 SQL Server CUs installed: • SQL_2017: CU 26 New AWS Windows AMIs • • • • • • Windows_Server-2022-Japanese-Full-SQL_2019_Enterprise-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2019_Standard-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2019_Web-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Enterprise-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Standard-2021.11.10 Windows_Server-2022-Japanese-Full-SQL_2017_Web-2021.11.10 Monthly AMI updates for 2025 (to date) 135 AWS Windows AMIs Reference Release Changes 2021.10.13 All AMIs • • • Windows Security updates current to October 12, 2021 AWS Tools for Windows PowerShell version 3.15.1421 SSM version 3.1.338.0 Windows Server 2022 and EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.651 Windows Server 2012 RTM and R2 AMIs • EC2Conﬁg version 4.9.4508 New AWS Windows AMIs Windows_Server-2022-English-Full-SQL_2019_Enterprise-2021.10.13 Windows_Server-2022-English-Full-SQL_2019_Standard-2021.10.13 Windows_Server-2022-English-Full-SQL_2019_Web-2021.10.13 Windows_Server-2022-English-Full-SQL_2019_Express-2021.10.13 Windows_Server-2022-English-Full-SQL_2017_Enterprise-2021.10.13 Windows_Server-2022-English-Full-SQL_2017_Standard-2021.10.13 • • • • • • • Monthly AMI updates for 2025 (to date) 136 AWS Windows AMIs Reference Release Changes Windows_Server-2022-English-Full-SQL_2017_Web-2021.10.13 • Windows_Server-2022-English-Full-SQL_2017_Express-2021.10.13 New EC2Launch v2 AMIs The following AMIs with EC2Launch v2 long-term support are now available . The following AMIs include EC2Launch v1 v2 as the default launch agent and will be updated with new versions each month. • • • • • • • EC2Launch v1V2-Windows_Server-2019-English-Full-Base-2021.10.13 EC2Launch v1V2-Windows_Server-2019-English-Core-Base-2021.10.13 EC2Launch v1V2-Windows_Server-2019-English-Full-ContainersLatest -2021.10.13 EC2Launch v1V2-Windows_Server-2016-English-Full-Base-2021.10.13 EC2Launch v1V2-Windows_Server-2016-English-Core-Base-2021.10.13 EC2Launch v1V2-Windows_Server-2012_R2_RTM-English-Full-Base-2021 .10.13 EC2Launch v1V2-Windows_Server-2012_RTM-English-Full-Base-2021.10 .13 EC2Launch v1V2_Preview AMIs are discontinued, and will not be update d with new versions. However, earlier versions will continue to be available until January 2022. Existing images and custom images based on EC2Launch v1V2_Preview AMIs will not be impacted, and you can continue to use them in your account. We recommend that you use the new EC2Launch v2 AMIs going forward to receive security and software updates. Monthly AMI updates for 2025 (to date) 137 AWS Windows AMIs Reference Release Changes Windows Server 2004 will reach End-of-support on December 14, 2021. All public versions of the following images will be made private on December 14, 2021. Existing instances and custom images owned by your account that are based on Windows Server 2004 will not be impacted. If you want to retain access to Windows Server 2004, create a custom image in your account prior to December 14th. • • Windows_Server-2004-English-Core-Base Windows_Server-2004-English-Core-ContainersLatest Previous versions of Amazon-published AWS Windows AMIs dated July 14, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 138 AWS Windows AMIs Reference Release Changes 2021.09.15 All AMIs • • • • Windows Security updates current to September 14, 2021 AWS Tools for Windows PowerShell version 3.15.1398 SSM version 3.1.282.0 SQL Server CUs installed: • • SQL_2019: CU12 SQL_2017: CU 25 Windows Server 2022 and EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.592 Windows Server 2012 RTM and R2 AMIs • EC2Conﬁg version 4.9.4500 Previous versions of Amazon-published AWS Windows AMIs dated June 9, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 139 AWS Windows AMIs Reference Release Changes 2021.09.01 New AWS Windows AMIs • • • • • • • • • • • • • • • • • Windows_Server-2022-English-Full-Base-2021.08.25 Windows_Server-2022-English-Full-ContainersLatest-2021.08.25 Windows_Server-2022-English-Core-Base-2021.08.25 Windows_Server-2022-English-Core-ContainersLatest-2021.08.25 Windows_Server-2022-Chinese_Simpliﬁed-Full-Base-2021.08.25 Windows_Server-2022-Chinese_Traditional-Full-Base-2021.08.25 Windows_Server-2022-Czech-Full-Base-2021.08.25 Windows_Server-2022-Dutch-Full-Base-2021.08.25 Windows_Server-2022-French-Full-Base-2021.08.25 Windows_Server-2022-German-Full-Base-2021.08.25 Windows_Server-2022-Hungarian-Full-Base-2021.08.25 Windows_Server-2022-Italian-Full-Base-2021.08.25 Windows_Server-2022-Japanese-Full-Base-2021.08.25 Windows_Server-2022-Korean-Full-Base-2021.08.25 Windows_Server-2022-Polish-Full-Base-2021.08.25 Windows_Server-2022-Portuguese_Brazil-Full-Base-2021.08.25 Windows_Server-2022-Portuguese_Portugal-Full-Base-2021.08.25 Monthly AMI updates for 2025 (to date) 140 AWS Windows AMIs Reference Release Changes • • • • Windows_Server-2022-Russian-Full-Base-2021.08.25 Windows_Server-2022-Spanish-Full-Base-2021.08.25 Windows_Server-2022-Swedish-Full-Base-2021.08.25 Windows_Server-2022-Turkish-Full-Base-2021.08.25 Windows Server 2022 AMIs include EC2Launch v2 by default. For more information, see EC2Launch v2. EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.592 Previous versions of Amazon-published AWS Windows AMIs dated May 12, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 141 AWS Windows AMIs Reference Release Changes 2021.08.11 All AMIs • • • • • Windows Security updates current to August 10th, 2021 AWS Tools for Windows PowerShell version 3.15.13571 EC2Launch v1 version 1.3.2003411 SSM version 3.0.1181.0 SQL Server CUs installed: • SQL_2019: CU11 EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.548 Previous versions of Amazon-published AWS Windows AMIs dated April 14, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 142 AWS Windows AMIs Reference Release Changes 2021.07.14 All AMIs • • • • Windows Security updates current to July 13th, 2021 AWS Tools for Windows PowerShell version 3.15.1350 EC2Launch v1 version 1.3.2003364 SQL Server CUs installed: • SQL_2017: CU24 2021.07.07 All AMIs Out-of-band AMI release that applies the July out-of-band security update recently released by Microsoft as an additional mitigation to CVE-34527. Note HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft \Windows NT\Printers\PointAndPrint on AWS Windows AMIs provided by AWS, which is the default state. is not deﬁned • For more information, see CVE-2021-34527 on the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated March 10, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 143 AWS Windows AMIs Reference Release Changes 2021.06.09 All AMIs • • • Windows Security
windows-ami-reference-025	windows-ami-reference.pdf	25	v1 version 1.3.2003364 SQL Server CUs installed: • SQL_2017: CU24 2021.07.07 All AMIs Out-of-band AMI release that applies the July out-of-band security update recently released by Microsoft as an additional mitigation to CVE-34527. Note HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft \Windows NT\Printers\PointAndPrint on AWS Windows AMIs provided by AWS, which is the default state. is not deﬁned • For more information, see CVE-2021-34527 on the Microsoft website. Previous versions of Amazon-published AWS Windows AMIs dated March 10, 2021 and earlier were made private. Monthly AMI updates for 2025 (to date) 143 AWS Windows AMIs Reference Release Changes 2021.06.09 All AMIs • • • Windows Security updates current to June 8th, 2021 AWS Tools for Windows PowerShell version 3.15.1326 SSM version 3.0.1124.0 Windows Server 2012RTM/2012 R2 AMIs • EC2Conﬁg version 4.9.4419 Monthly AMI updates for 2025 (to date) 144 AWS Windows AMIs Reference Release Changes 2021.05.12 All AMIs Windows Security updates current to May 11th, 2021 AWS Tools for Windows PowerShell version 3.15.1302 EC2Launch v1 version 1.3.2003312 SQL Server CUs installed: • SQL_2019: CU10 • • • • • Previous versions of Amazon-published AWS Windows AMIs dated February 10, 2021 and earlier were made private. Windows Server 2012RTM/2012 R2 AMIs • • EC2Conﬁg version 4.9.4381 SSM version 3.0.529.0 NVIDIA GPU AMIs • • GRID version 462.31 Tesla version 462.31 Radeon GPU AMIs • Radeon version 20.10.25.04 Monthly AMI updates for 2025 (to date) 145 AWS Windows AMIs Reference Release Changes 2021.04.14 All AMIs • • • • • • • • • Windows Security updates current to April 13th, 2021 AWS Tools for Windows PowerShell version 3.15.1280 AWS PV version 8.4.0 cfn-init version 2.0.6. This package includes Microsoft Visual C++ 2015-2019 Redistributable version 14.28.29913.0 as a dependency. AWS ENA version 2.2.3 EC2Launch v1 version 1.3.2003284 SQL Server CUs installed: • SQL_2017: CU23 Previous versions of Amazon-published AWS Windows AMIs dated January 13, 2021 and earlier were made private. Note Windows Server 1909 reaches End of Support on May 11, 2021. All public versions of the following images will be made private on May 11th, 2021. Existing instances and custom images owned by your account that are based on Windows Server 1909 will not be impacted. To retain access to Windows Server 1909, create a custom image in your account prior to May 11, 2021. Windows_Server-1909-English-Core-Base • • Monthly AMI updates for 2025 (to date) 146 AWS Windows AMIs Reference Release Changes Windows_Server-1909-English-Core-ContainersLatest EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.285 Monthly AMI updates for 2025 (to date) 147 AWS Windows AMIs Reference Release Changes 2021.03.11 All AMIs Windows Security updates current to March 9th, 2021 AWS Tools for Windows PowerShell version 3.15.1248 cfn-init version 2.0.5. This package includes Microsoft Visual C++ 2015-2019 Redistributable version 14.28.29910.0 as a dependency. EC2Launch v1 version 1.3.2003236 SSM Agent version 3.0.529.0 NVIDIA GRID version 461.33 SQL Server CUs installed: • • SQL 2016_SP2: CU16 SQL 2019: CU9 • • • • • • • • KB4577586 update for the removal of Adobe Flash Player installed on all applicable images (Adobe Flash player is not enabled by default on all images). Note Amazon Root CAs have been added to the Trusted Root Certiﬁcatio n Authorities certiﬁcate store on all AMIs. For more information, see https://www.amazontrust.com/repository/#rootcas. Monthly AMI updates for 2025 (to date) 148 AWS Windows AMIs Reference Release Changes Windows Server 2016 and 2019 AMIs • Updated from default .NET framework versions to version 4.8. Windows Server 2012RTM/2012 R2 AMIs • • EC2Conﬁg version 4.9.4326 SSM Agent version 3.0.431.0 Monthly AMI updates for 2025 (to date) 149 AWS Windows AMIs Reference Release Changes 2021.02.10 All AMIs • • • Windows Security updates current to February 9th, 2021 AWS Tools for Windows PowerShell version 3.15.1224 NVIDIA GRID version 461.09 Beginning in March 2021, AWS Windows AMIs provided by AWS include Amazon Root CAs in the certiﬁcate store to minimize potential disruptio n from the upcoming S3 and CloudFront certiﬁcate migration, which is scheduled for March 23rd, 2021. For more information, see the following: • • How to Prepare for the AWS Move to Its Own Certiﬁcate Authority [Announcement] CloudFront & S3 migrating default certiﬁcates to Amazon Trust Services March 23rd 2021 Additionally, AWS will apply "update for Removal of Adobe Flash Player" (KB4577586) to all AWS Windows AMIs in March to remove the built-in Adobe Flash player, which ended support on December 31, 2020. If your use case requires the built-in Adobe Flash player, we recommend creating a custom image based on AMIs with version 2021.02.10 or earlier. For more information about the End of Support of Adobe Flash Player, see Update on Adobe Flash Player End of Support EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.207 Monthly AMI updates for 2025 (to date) 150 AWS Windows AMIs Reference Release Changes New AWS Windows AMIs • • • • • • Windows_Server-2016-Japanese-Full-SQL_2019_Enterprise-2021.02.10 Windows_Server-2016-Japanese-Full-SQL_2019_Standard-2021.02.10
windows-ami-reference-026	windows-ami-reference.pdf	26	to all AWS Windows AMIs in March to remove the built-in Adobe Flash player, which ended support on December 31, 2020. If your use case requires the built-in Adobe Flash player, we recommend creating a custom image based on AMIs with version 2021.02.10 or earlier. For more information about the End of Support of Adobe Flash Player, see Update on Adobe Flash Player End of Support EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.207 Monthly AMI updates for 2025 (to date) 150 AWS Windows AMIs Reference Release Changes New AWS Windows AMIs • • • • • • Windows_Server-2016-Japanese-Full-SQL_2019_Enterprise-2021.02.10 Windows_Server-2016-Japanese-Full-SQL_2019_Standard-2021.02.10 Windows_Server-2016-Japanese-Full-SQL_2019_Web-2021.02.10 Windows_Server-2019-Japanese-Full-SQL_2019_Enterprise-2021.02.10 Windows_Server-2019-Japanese-Full-SQL_2019_Standard-2021.02.10 Windows_Server-2019-Japanese-Full-SQL_2019_Web-2021.02.10 2021.01.13 All AMIs • • • • Windows Security updates current to January 12th, 2021 AWS Tools for Windows PowerShell version 3.15.1204 AWS ENA version 2.2.2 EC2Launch v1 v1 version 1.3.2003210 Windows Server SAC/2019/2016 AMIs • SSM Agent version 3.0.431.0 Monthly AMI updates for 2020 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2020 on the Microsoft website. Monthly AMI updates for 2025 (to date) 151 AWS Windows AMIs Reference Release Changes 2020.12.09 All AMIs • • • • • Windows Security updates current to December 8th, 2020 AWS Tools for Windows PowerShell version 3.15.1181 All SQL Server Enterprise, Standard, and Web AMIs now include SQL Server installation media at C:\SQLServerSetup EC2Launch v1 v1 version 1.3.2003189 Previous versions of Amazon-published AWS Windows AMIs dated September 9, 2020 and earlier were made private. Windows Server 2012/2012 R2 AMIs • • EC2Conﬁg version 4.9.4279 SSM Agent version 2.3.871.0 EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.160 2020.11.11 All AMIs • • • Windows Security updates current to November 10th, 2020 AWS Tools for Windows PowerShell version 3.15.1160 SQL Server CUs installed: Monthly AMI updates for 2025 (to date) 152 AWS Windows AMIs Reference Release Changes • • • SQL 2016 SP2: CU15 SQL 2017: CU22 SQL 2019: CU8 SSM Agent version 2.3.1644.0 EC2Launch v2 Preview AMIs: EC2Launch v1 version 2.0.153 Previous versions of Amazon-published AWS Windows AMIs dated August 12, 2020 and earlier were made private. • • • New AWS Windows AMIs • • Windows_Server-20H2-English-Core-Base-2020.11.11 Windows_Server-20H2-English-Core-ContainersLatest-2020.11.11 Monthly AMI updates for 2025 (to date) 153 AWS Windows AMIs Reference Release Changes 2020.10.14 All AMIs Windows Security updates current to October 13th, 2020 AWS Tools for Windows PowerShell version 3.15.1140 NVIDIA GRID version 452.39 EC2Launch v2 Preview AMIs: EC2Launch v1 version 2.0.146 AWS ENA version 2.2.1 cfn-init version 1.4.34 • • • • • • • Previous versions of Amazon-published AWS Windows AMIs dated July 15, 2020 and earlier were made private. Monthly AMI updates for 2025 (to date) 154 AWS Windows AMIs Reference Release Changes 2020.9.25 A new version of Amazon Machine Images with SQL Server 2019 dated 2020.09.25 has been released. This release includes the same software components as the previous release dated 2020.09.09 but does not include CU7 for SQL 2019, which has recently been removed from public av ailability by Microsoft due to a known issue with reliability of the database snapshot feature. For more information, see the following Microsoft blog post: Cumulative update 7 for SQL Server 2019 RTM on the Microsoft website. New AWS Windows AMIs • • • • • • • • Windows_Server-2016-English-Full-SQL_2019_Enterprise-2020.09.25 Windows_Server-2016-English-Full-SQL_2019_Express-2020.09.25 Windows_Server-2016-English-Full-SQL_2019_Standard-2020.09.25 Windows_Server-2016-English-Full-SQL_2019_Web-2020.09.25 Windows_Server-2019-English-Full-SQL_2019_Enterprise-2020.09.25 Windows_Server-2019-English-Full-SQL_2019_Express-2020.09.25 Windows_Server-2019-English-Full-SQL_2019_Standard-2020.09.25 Windows_Server-2019-English-Full-SQL_2019_Web-2020.09.25 EC2Launch v1V2_Preview AMIs • EC2Launch v1V2_Preview-Windows_Server-2019-English-Full-SQL_2019 _Express-2020.09.25 Monthly AMI updates for 2025 (to date) 155 AWS Windows AMIs Reference Release Changes 2020.9.9 All AMIs Windows Security updates current to September 8th, 2020 AWS PV drivers version 8.3.4 AWS ENA version 2.2.0 AWS Tools for Windows PowerShell version 3.15.1110 SQL Server CUs installed • • SQL_2016_SP2: CU14 SQL_2019: CU7 • • • • • • Previous versions of Amazon-published AWS Windows AMIs dated June 10, 2020 and earlier were made private. Windows Server 2016/2019/1809/1903/1909/2004 AMIs • • EC2Launch v1 version 1.3.2003155 SSM Agent version 2.3.1319.0 EC2Launch v1V2_Preview AMIs • EC2Launch v2 version 2.0.124 Monthly AMI updates for 2025 (to date) 156 AWS Windows AMIs Reference Release Changes 2020.8.12 All AMIs Windows Security updates current to August 11th, 2020 AWS Tools for Windows PowerShell version 3.15.1084 G3 AMIs: NVIDIA GRID version 451.48 EC2Launch v2 Preview AMIs: EC2Launch v1 version 2.0.104 SQL CUs installed • SQL_2019: CU6 • • • • • • Previous versions of Amazon-published AWS Windows AMIs dated May 13, 2020 and earlier were made private. 2020.7.15 All AMIs Windows Security updates current to July 14th, 2020 AWS Tools for Windows PowerShell version 3.15.1064 ENA version 2.1.5 SQL Server CUs installed • • SQL_2017: CU21 SQL_2019: CU5 • • • • • Previous versions of Amazon-published AWS Windows AMIs dated April 15, 2020 and earlier were made private. Monthly AMI updates for 2025 (to date) 157 AWS Windows AMIs Reference Release Changes 2020.7.01 A new version of Amazon Machine Images has
windows-ami-reference-027	windows-ami-reference.pdf	27	• SQL_2019: CU6 • • • • • • Previous versions of Amazon-published AWS Windows AMIs dated May 13, 2020 and earlier were made private. 2020.7.15 All AMIs Windows Security updates current to July 14th, 2020 AWS Tools for Windows PowerShell version 3.15.1064 ENA version 2.1.5 SQL Server CUs installed • • SQL_2017: CU21 SQL_2019: CU5 • • • • • Previous versions of Amazon-published AWS Windows AMIs dated April 15, 2020 and earlier were made private. Monthly AMI updates for 2025 (to date) 157 AWS Windows AMIs Reference Release Changes 2020.7.01 A new version of Amazon Machine Images has been released. These images include EC2Launch v2 and serve as a functional preview of the new launch agent in advance of it being included by default on all AWS Windows AMIs currently provided by AWS later this year. Note that some SSM documents and dependent services, such as EC2 Image Builder, may require updates to support EC2 Launch v2. These updates will follow in the coming weeks. These images are not recommended for use in production environments. You can read more about EC2Launch v2 at https://aws.amazon.com/about- aws/whats-new/2020/07/introducing-ec2-launch-v2-simplify-customizing- windows-instances/ and Conﬁgure a Windows instance using EC2Launch v2. All current Windows Server AMIs will continue to be provided without changes to the current launch agent, either EC2Conﬁg (Server 2012 RTM or 2012 R2) or EC2Launch v1 v1 (Server 2016 or later), for the next several months. In the near future, all Windows Server AMIs currently provided by AWS will be migrated to use EC2Launch v2 by default as part of the monthly release. EC2Launch v1V2_Preview AMIs will be updated monthly and remain available until this migration occurs. New AWS Windows AMIs • • • • • EC2Launch v1V2_Preview-Windows_Server-2004-English-Core-Base-202 0.06.30 EC2Launch v1V2_Preview-Windows_Server-2019-English-Full-Base-202 0.06.30 EC2Launch v1V2_Preview-Windows_Server-2019-English-Core-Base-202 0.06.30 EC2Launch v1V2_Preview-Windows_Server-2016-English-Full-Base-202 0.06.30 EC2Launch v1V2_Preview-Windows_Server-2016-English-Core-Base-202 0.06.30 Monthly AMI updates for 2025 (to date) 158 AWS Windows AMIs Reference Release Changes • • • • • EC2Launch v1V2_Preview-Windows_Server-2012_R2_RTM-English-Full-B ase-2020.06.30 EC2Launch v1V2_Preview-Windows_Server-2012_R2_RTM-English-Core-B ase-2020.06.30 EC2Launch v1V2_Preview-Windows_Server-2012_RTM-English-Full-Base -2020.06.30 EC2Launch v1V2_Preview-Windows_Server-2019-English-Full-SQL_2019 _Express-2020.06.30 EC2Launch v1V2_Preview-Windows_Server-2016-English-Full-SQL_2017 _Express-2020.06.30 2020.6.10 All AMIs • • • • Windows Security updates current to June 9th, 2020 AWS Tools for Windows PowerShell version 3.15.1034 cfn-init version 1.4.33 SQL CU installed: SQL_2016_SP2: CU13 2020.5.27 New AWS Windows AMIs • • Windows_Server-2004-English-Core-Base-2020.05.27 Windows_Server-2004-English-Core-ContainersLatest-2020.05.27 Monthly AMI updates for 2025 (to date) 159 AWS Windows AMIs Reference Release Changes 2020.5.13 All AMIs • • • Windows Security updates current to May 12th, 2020 AWS Tools for Windows PowerShell version 3.15.1013 EC2Launch v1 version 1.3.2003150 2020.4.15 All AMIs • • • • • • Windows Security updates current to April 14th, 2020 AWS Tools for Windows PowerShell version 3.15.998 EC2Conﬁg version 4.9.4222 EC2Launch v1 version 1.3.2003040 SSM Agent version 2.3.842.0 SQL Server CUs installed: • • SQL_2017: CU 20 SQL_2019: CU 4 2020.3.18 Windows Server 2019 AMIs Resolves an intermittent issue discovered in the 2020.3.11 release in which the Background Intelligent Transfer Service (BITS) may not start within the expected time after initial OS boot, potentially resulting in timeouts, BITS errors in the event log, or failures of cmdlets involving BITS invoked quickly after the initial boot. Other Windows Server AMIs are not aﬀected by this issue, and their latest version remains 2020.03.11. Monthly AMI updates for 2025 (to date) 160 AWS Windows AMIs Reference Release Changes 2020.3.11 All AMIs • • • • • • • Windows Security updates current to March 10th, 2020 AWS Tools for Windows PowerShell version 3.15.969 EC2Conﬁg version 4.9.4122 EC2Launch v1 version 1.3.2002730 SSM Agent version 2.3.814.0 SQL Server CUs installed: SQL_2016_SP2: CU 12 SQL_2017: CU 19 • • • SQL_2019: CU 2 not applied due to known issue with SQL Agent Out of band security update (KB4551762) for server core 1909 and 1903 applied to mitigate CVE-2020-0796. Other Windows Server versions are not impacted by this issue. Monthly AMI updates for 2025 (to date) 161 AWS Windows AMIs Reference Release Changes 2020.2.12 All AMIs • • • • Windows Security updates current to February 11th, 2020 AWS Tools for Windows PowerShell version 3.15.945 Intel SRIOV driver updates • • • 2019/1903/1909: version 2.1.185.0 2016/1809: version 2.1.186.0 2012 R2: version 1.2.199.0 SQL Server CUs installed: SQL_2019: CU 1 SQL_2017: CU 18 • • • SQL_2016_SP2: CU 11 Windows Server 2008 SP2 and Windows Server 2008 R2 Windows Server 2008 SP2 and Window Server 2008 R2 reached End of Support (EOS) on 01/14/20 and will no longer receive regular security updates from Microsoft. AWS will no longer publish or distribute Windows Server 2008 SP2 or Windows Server 2008 R2 AMIs. Existing 2008 SP2/R2 instances and custom AMIs in your account are not impacted, and you can continue to use them after the EOS date. For more information about Microsoft End of Service on AWS, including upgrade and import options, as well as a full list of AMIs that are
windows-ami-reference-028	windows-ami-reference.pdf	28	Server 2008 SP2 and Windows Server 2008 R2 Windows Server 2008 SP2 and Window Server 2008 R2 reached End of Support (EOS) on 01/14/20 and will no longer receive regular security updates from Microsoft. AWS will no longer publish or distribute Windows Server 2008 SP2 or Windows Server 2008 R2 AMIs. Existing 2008 SP2/R2 instances and custom AMIs in your account are not impacted, and you can continue to use them after the EOS date. For more information about Microsoft End of Service on AWS, including upgrade and import options, as well as a full list of AMIs that are no longer Monthly AMI updates for 2025 (to date) 162 AWS Windows AMIs Reference Release Changes published as of 01/14/2020, see End of Support (EOS) for Microsoft 2020.1.15 Products. All AMIs • • • Microsoft security updates current to January 14, 2020 AWS Tools for Windows PowerShell version 3.15.925 ENA version 2.1.4 Windows Server 2008 SP2 and Windows Server 2008 R2 Windows Server 2008 SP2 and Window Server 2008 R2 reached End of Support (EOS) on 01/14/20 and will no longer receive regular security updates from Microsoft. AWS will no longer publish or distribute Windows Server 2008 SP2 or Windows Server 2008 R2 AMIs. Existing 2008 SP2/R2 instances and custom AMIs in your account are not impacted, and you can continue to use them after the EOS date. For more information about Microsoft End of Service on AWS, including upgrade and import options, as well as a full list of AMIs that are no longer published as of 01/14/2020, see End of Support (EOS) for Microsoft Products. Monthly AMI updates for 2019 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2019 on the Microsoft website. Release Changes 2019.12.16 Monthly AMI updates for 2025 (to date) 163 AWS Windows AMIs Release Changes All AMIs Reference • • Microsoft security updates current to December 10, 2019 AWS Tools for Windows PowerShell version 3.15.903 Windows Server 2008 SP2 and Windows Server 2008 R2 Microsoft will end mainstream support for Windows Server 2008 SP2 and Windows Server 2008 R2 on January 14, 2020. On this date, AWS will no longer publish or distribute Windows Server 2008 SP2 or Windows Server 2008 R2 AMIs. Existing 2008 SP2/R2 instances and custom AMIs in your account will not be impacted and you can continue to use them after the end-of-service (EOS) date. For more information about Microsoft EOS on AWS, including upgrade and import options, along with a full list of AMIs that will no longer be published or distributed on January 14, 2020, see End of Support (EOS) for Microsoft Products. Monthly AMI updates for 2025 (to date) 164 AWS Windows AMIs Reference Release Changes 2019.11.13 All AMIs • • • • • AWS Tools for Windows PowerShell version 3.15.876 Windows Security updates current to November 12th, 2019 EC2 Conﬁg version 4.9.3865 EC2 Launch version 1.3.2002240 SSM Agent v2.3.722.0 Previous versions of AMIs have been marked private. New AWS Windows AMIs Windows_Server-1909-English-Core-Base-2019.11.13 Windows_Server-1909-English-Core-ContainersLatest-2019.11.13 Windows_Server-2016-English-Full-SQL_2019_Enterprise-2019.11.13 Windows_Server-2016-English-Full-SQL_2019_Express-2019.11.13 Windows_Server-2016-English-Full-SQL_2019_Standard-2019.11.13 Windows_Server-2016-English-Full-SQL_2019_Web-2019.11.13 Windows_Server-2019-English-Full-SQL_2019_Enterprise-2019.11.13 Windows_Server-2019-English-Full-SQL_2019_Express-2019.11.13 Windows_Server-2019-English-Full-SQL_2019_Standard-2019.11.13 • • • • • • • • • • Monthly AMI updates for 2025 (to date) 165 AWS Windows AMIs Reference Release Changes Windows_Server-2019-English-Full-SQL_2019_Web-2019.11.13 2019.11.05 New AWS Windows AMIs New SQL AMIs available: • • • • • • • • Windows_Server-2016-English-Full-SQL_2019_Enterprise-2019.11.05 Windows_Server-2016-English-Full-SQL_2019_Express-2019.11.05 Windows_Server-2016-English-Full-SQL_2019_Standard-2019.11.05 Windows_Server-2016-English-Full-SQL_2019_Web-2019.11.05 Windows_Server-2019-English-Full-SQL_2019_Enterprise-2019.11.05 Windows_Server-2019-English-Full-SQL_2019_Express-2019.11.05 Windows_Server-2019-English-Full-SQL_2019_Standard-2019.11.05 Windows_Server-2019-English-Full-SQL_2019_Web-2019.11.05 Monthly AMI updates for 2025 (to date) 166 AWS Windows AMIs Reference Release Changes 2019.10.09 All AMIs AWS Tools for Windows PowerShell version 3.15.846 Windows Security updates current to October 8th, 2019 • • • Windows Defender platform updates current and update block via registry removed. For more information, see SFC incorrectly ﬂags Windows Defender PowerShell module ﬁles as corrupted on the Microsoft website. New AWS Windows AMIs New ECS-optimized AMI available: • Windows_Server-2019-English-Core-ECS_Optimized-2019.10.09 2019.09.12 New AWS Windows AMI • amzn2-ami-hvm-2.0.20190618-x86_64-gp2-mono .NET Core 2.2, Mono 5.18, and PowerShell 6.2 pre-installed to run your .NET applications on Amazon Linux 2 with Long Term Support (LTS) Monthly AMI updates for 2025 (to date) 167 AWS Windows AMIs Reference Release Changes 2019.09.11 All AMIs • • • • • • • AWS PV driver version 8.3.2 AWS NVMe driver version 1.3.2 AWS Tools for Windows PowerShell version 3.15.826 NLA enabled on all OS 2012 RTM to 2019 AMIs Intel 82599 VF driver reverted to version 2.0.210.0 (Server 2016) or version 2.1.138.0 (Server 2019) due to customer reported issues. Engagement with Intel concerning these issues ongoing. Windows Security updates current to September 10, 2019 Windows Defender platform update blocked via registry due to SFC failures introduced by latest client. Will be reenabled when patch available. For more information, see SFC incorrectly ﬂags Windows Defender PowerShell module ﬁles as corrupted on the Microsoft website. Platform update block: HKLM:\SOFTWARE\Microsoft\Windows Defender \Miscellaneous Conﬁguration\PreventPlatformUpdate
windows-ami-reference-029	windows-ami-reference.pdf	29	version 1.3.2 AWS Tools for Windows PowerShell version 3.15.826 NLA enabled on all OS 2012 RTM to 2019 AMIs Intel 82599 VF driver reverted to version 2.0.210.0 (Server 2016) or version 2.1.138.0 (Server 2019) due to customer reported issues. Engagement with Intel concerning these issues ongoing. Windows Security updates current to September 10, 2019 Windows Defender platform update blocked via registry due to SFC failures introduced by latest client. Will be reenabled when patch available. For more information, see SFC incorrectly ﬂags Windows Defender PowerShell module ﬁles as corrupted on the Microsoft website. Platform update block: HKLM:\SOFTWARE\Microsoft\Windows Defender \Miscellaneous Conﬁguration\PreventPlatformUpdate type=DWORD, value=1 Previous versions of AMIs have been marked private. New AWS Windows AMIs New STIG-compliant AMIs available: • • Windows_Server-2012-R2-English-STIG-Full Windows_Server-2012-R2-English-STIG-Core Monthly AMI updates for 2025 (to date) 168 AWS Windows AMIs Reference Release Changes • • • • Windows_Server-2016-English-STIG-Full Windows_Server-2016-English-STIG-Core Windows_Server-2019-English-STIG-Full Windows_Server-2019-English-STIG-Core Windows Server 2008 R2 SP1 Includes the following updates, which are required for Microsoft Extended Security (ESU) updates. • • • KB4490628 KB4474419 KB4516655 Windows Server 2008 SP2 Includes the following updates, which are required for Microsoft Extended Security (ESU) updates. • • • KB4493730 KB4474419 KB4517134 Monthly AMI updates for 2025 (to date) 169 AWS Windows AMIs Reference Release Changes Note NLA is now enabled on all 2012 RTM, 2012 R2, and 2016 AMIs to increase default RDP security posture. NLA remains enabled on 2019 AMIs. 2019.08.16 All AMIs • • • • • Microsoft security updates current to August 13th, 2019. Includes KBs addressing CVE-2019-1181, CVE-2019-1182, CVE-2019-1222, and CVE -2019-1226. EC2Conﬁg version 4.9.3519 SSM Agent version 2.3.634.0 AWS Tools for Windows PowerShell version 3.15.802 Windows Defender platform update blocked via registry due to SFC failures introduced by update. Update will be re-enabled when new patch is available. Note Starting in September, NLA will be enabled on all 2012 RTM, 2012 R2, and 2016 AMIs to increase default RDP security posture. Monthly AMI updates for 2025 (to date) 170 AWS Windows AMIs Reference Release Changes 2019.07.19 New AWS Windows AMIs • • Windows_Server-2016-English-Full-ECS_Optimized-2019.07.19 Windows_Server-2019-English-Full-ECS_Optimized-2019.07.19 2019.07.12 All AMIs • Microsoft security updates current to July 9th, 2019 Monthly AMI updates for 2025 (to date) 171 AWS Windows AMIs Reference Release Changes 2019.06.12 All AMIs Microsoft security updates current to June 11th, 2019 AWS SDK version 3.15.756 AWS PV driver version 8.2.7 AWS NVMe driver version 1.3.1 • • • • • The following "P3" AMIs will be renamed as "Tesla" AMIs. These AMIs will support all GPU-backed AWS instances using the Tesla driver. P3 AMIs will no longer be updated after this release and will be removed as part of our regular cycle. • • Windows_Server-2012-R2_RTM-English-P3-2019.06.12 replaced with Windows_Server-2012-R2_RTM-English-Tesla-2019.06.12 Windows_Server-2016-English-P3-2016.06.12 replaced with Windows_Server-2016-English-Tesla-2019.06.12 New AWS Windows AMIs • Windows_Server-2019-English-Tesla-2019.06.12 Previous versions of AMIs have been marked private. 2019.05.21 Windows Server, version 1903 • AMIs are now available Monthly AMI updates for 2025 (to date) 172 AWS Windows AMIs Reference Release Changes 2019.05.15 All AMIs • • • • Microsoft security updates current to May 14th, 2019 EC2Conﬁg version 4.9.3429 SSM Agent version 2.3.542.0 AWS SDK version 3.15.735 2019.04.26 All AMIs • Fixed AMIs for Windows Server 2019 with SQL to address edge cases where the ﬁrst launch of an instance may result in Instance Impairmen t and Windows displays the message "Please wait for the User Proﬁle 2019.04.21 Service". All AMIs • AWS PV Driver rollback to version 8.2.6 from version 8.3.0 Monthly AMI updates for 2025 (to date) 173 AWS Windows AMIs Reference Release Changes 2019.04.10 All AMIs • • • • Microsoft security updates current to April 9, 2019 AWS SDK version 3.15.715 AWS PV Driver version 8.3.0 EC2Launch v1 version 1.3.2001360 New AWS Windows AMIs • • • Windows_Server-2016-English-Full-SQL_2012_SP4_Standard-2019.04.10 Windows_Server-2016-English-Full-SQL_2014_SP3_Standard-2019.04.10 Windows_Server-2016-English-Full-SQL_2014_SP3_Enterprise-2019.0 2019.03.13 4.10 All AMIs Microsoft security updates current to March 12, 2019 AWS SDK version 3.15.693 EC2Launch v1 version 1.3.2001220 • • • • NVIDIA Tesla driver version 412.29 for Deep Learning and P3 AMIs (https://nvidia.custhelp.com/app/answers/detail/a_id/4772) Previous versions of AMIs have been marked private Monthly AMI updates for 2025 (to date) 174 AWS Windows AMIs Reference Release Changes 2019.02.13 All AMIs • • • • • • • Microsoft security updates current to February 12, 2019 SSM Agent version 2.3.444.0 AWS SDK version 3.15.666 EC2Launch v1 version 1.3.2001040 EC2Conﬁg version 4.9.3289 AWS PV driver 8.2.6 EBS NVMe tool SQL 2014 with Service Pack 2 and SQL 2016 with Service Pack 1 will no longer be updated after this release. 2019.02.09 All AMIs • AWS Windows AMIs have been updated. New AMIs can be found with the following date versions: November "2018.11.29" December "2018.12.13" January "2019.02.09" Previous versions of AMIs have been marked private Monthly AMI updates for 2025 (to date) 175 AWS Windows AMIs Reference Release Changes 2019.01.10 All AMIs • • • • • Microsoft security updates current to January 10,
windows-ami-reference-030	windows-ami-reference.pdf	30	version 3.15.666 EC2Launch v1 version 1.3.2001040 EC2Conﬁg version 4.9.3289 AWS PV driver 8.2.6 EBS NVMe tool SQL 2014 with Service Pack 2 and SQL 2016 with Service Pack 1 will no longer be updated after this release. 2019.02.09 All AMIs • AWS Windows AMIs have been updated. New AMIs can be found with the following date versions: November "2018.11.29" December "2018.12.13" January "2019.02.09" Previous versions of AMIs have been marked private Monthly AMI updates for 2025 (to date) 175 AWS Windows AMIs Reference Release Changes 2019.01.10 All AMIs • • • • • Microsoft security updates current to January 10, 2019 SSM Agent version 2.3.344.0 AWS SDK version 3.15.647 EC2Launch v1 version 1.3.2000930 EC2Conﬁg version 4.9.3160 All AMIs with SQL Server • Latest cumulative updates Monthly AMI updates for 2018 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2018 on the Microsoft website. Release Changes 2018.12.12 All AMIs • • • • Microsoft security updates current to December 12, 2018 SSM Agent version 2.3.274.0 AWS SDK version 3.15.629 EC2Launch v1 version 1.3.2000760 Monthly AMI updates for 2025 (to date) 176 AWS Windows AMIs Reference Release Changes New AWS Windows AMIs Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2014_SP3 _Standard-2018.12.12 Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2014_SP3_Express- 2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2014_SP3_Enterpris e-2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2014_SP3_Standard- 2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2014_SP3_Express-2 018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2014_SP3_ Web-2018.12.12 Windows_Server-2012-RTM-Japanese-64Bit-SQL_2014_SP3_Express-201 8.12.12 Windows_Server-2012-RTM-Japanese-64Bit-SQL_2014_SP3_Standard-20 18.12.12 Windows_Server-2012-RTM-Japanese-64Bit-SQL_2014_SP3_We b-2018.12.12 Windows_Server-2012-RTM-English-64Bit-SQL_2014_SP3_Standard-201 8.12.12 Windows_Server-2012-RTM-English-64Bit-SQL_2014_SP3_Express-2018 .12.12 • • • • • • • • • • • • Monthly AMI updates for 2025 (to date) 177 AWS Windows AMIs Reference Release Changes Windows_Server-2012-RTM-English-64Bit-SQL_2014_SP3_Web-2018.12. 12 Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2 _Web-2018.12.12 Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2_Express- 2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Enterpris e-2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Standard- 2018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_Express-2 018.12.12 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP2_ Web-2018.12.12 Windows_Server-2012-R2_RTM-Japanese-64Bit-SQL_2016_SP2 _Standard-2018.12.12 Windows_Server-2016-Korean-Full-SQL_2016_SP2_Standard-2018.12.12 Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Enterprise-2018. 12.12 Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Web-2018.12.12 Windows_Server-2016-English-Full-SQL_2016_SP2_Web-2018.12.12 Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Standard-2018.12 .12 • • • • • • • • • • • • Monthly AMI updates for 2025 (to date) 178 AWS Windows AMIs Reference Release Changes • • • • • • • • • • • • • • • • • Windows_Server-2016-English-Full-SQL_2016_SP2_Express-2018.12.12 Windows_Server-2016-English-Full-SQL_2016_SP2_Standard-2018.12.12 Windows_Server-2016-English-Core-SQL_2016_SP2_Enterprise-2018.1 2.12 Windows_Server-2016-English-Core-SQL_2016_SP2_Web-2018.12.12 Windows_Server-2016-English-Core-SQL_2016_SP2_Express-2018.12.12 Windows_Server-2016-English-Core-SQL_2016_SP2_Standard-2018.12. 12 Windows_Server-2016-Japanese-Full-SQL_2016_SP2_Standard-2018.12 .12 Windows_Server-2016-Korean-Full-SQL_2016_SP2_Standard-2018.12.12 Windows_Server-2019-Spanish-Full-Base-2018.12.12 Windows_Server-2019-Japanese-Full-Base-2018.12.12 Windows_Server-2019-Portuguese_Portugal-Full-Base-2018.12.12 Windows_Server-2019-Chinese_Traditional-Full-Base-2018.12.12 Windows_Server-2019-Italian-Full-Base-2018.12.12 Windows_Server-2019-Swedish-Full-Base-2018.12.12 Windows_Server-2019-English-Core-Base-2018.12.12 Windows_Server-2019-Hungarian-Full-Base-2018.12.12 Windows_Server-2019-Polish-Full-Base-2018.12.12 Monthly AMI updates for 2025 (to date) 179 AWS Windows AMIs Reference Release Changes • • • • • • • • • • • • • • • • • • Windows_Server-2019-Turkish-Full-Base-2018.12.12 Windows_Server-2019-Korean-Full-Base-2018.12.12 Windows_Server-2019-Dutch-Full-Base-2018.12.12 Windows_Server-2019-German-Full-Base-2018.12.12 Windows_Server-2019-Russian-Full-Base-2018.12.12 Windows_Server-2019-Czech-Full-Base-2018.12.12 Windows_Server-2019-English-Full-Base-2018.12.12 Windows_Server-2019-French-Full-Base-2018.12.12 Windows_Server-2019-Portuguese_Brazil-Full-Base-2018.12.12 Windows_Server-2019-Chinese_Simpliﬁed-Full-Base-2018.12.12 Windows_Server-2019-English-Full-HyperV-2018.12.12 Windows_Server-2019-English-Full-ContainersLatest-2018.12.12 Windows_Server-2019-English-Core-ContainersLatest-2018.12.12 Windows_Server-2019-English-Full-SQL_2017_Enterprise-2018.12.12 Windows_Server-2019-English-Full-SQL_2017_Standard-2018.12.12 Windows_Server-2019-English-Full-SQL_2017_Web-2018.12.12 Windows_Server-2019-English-Full-SQL_2017_Express-2018.12.12 Windows_Server-2019-English-Full-SQL_2016_SP2_Enterprise-2018.1 2.12 Monthly AMI updates for 2025 (to date) 180 AWS Windows AMIs Reference Release Changes • • • Windows_Server-2019-English-Full-SQL_2016_SP2_Standard-2018.12.12 Windows_Server-2019-English-Full-SQL_2016_SP2_Web-2018.12.12 Windows_Server-2019-English-Full-SQL_2016_SP2_Express-2018.12.12 Updated Linux AMI • amzn2-ami-hvm-2.0.20180622.1-x86_64-gp2-dotnetcore-2018.12.12 2018.11.28 All AMIs SSM Agent version 2.3.235.0 • • Changes in all power schemes to set the display to never turn oﬀ 2018.11.20 Windows_Server-2016-English-Deep-Learning Windows_Server-2016-English-Deep-Learning • • • TensorFlow version 1.12 MXNet version 1.3 NVIDIA version 392.05 Monthly AMI updates for 2025 (to date) 181 AWS Windows AMIs Reference Release Changes 2018.11.19 All AMIs • • • • • Microsoft security updates current to November 19, 2018 AWS SDK version 3.15.602.0 SSM Agent version 2.3.193.0 EC2Conﬁg version 4.9.3067 Intel Chipset INF conﬁgurations to support new instance types Windows Server, version 1809 • AMIs are now available. Monthly AMI updates for 2025 (to date) 182 AWS Windows AMIs Reference Release Changes 2018.10.14 All AMIs • • • • • • Microsoft security updates current to October 9, 2018 AWS Tools for Windows PowerShell version 3.3.365.0 CloudFormation version 1.4.31 AWS PV Driver version 8.2.4 AWS PCI Serial Driver version 1.0.0.0 (support for Windows 2008R2 and 2012 on Bare Metal instances ENA Driver version 1.5.0 Windows Server 2016 Datacenter and Standard Editions for Nano Server Microsoft ended mainstream support for Windows Server 2016 Datacenter and Standard Editions for Nano Server installation options as of April 10, 2018. Monthly AMI updates for 2025 (to date) 183 AWS Windows AMIs Reference Release Changes 2018.09.15 All AMIs • • • • • Microsoft security updates current to September 12, 2018 AWS Tools for Windows PowerShell version 3.3.343 EC2Launch v1 version 1.3.2000430 AWS NVMe Driver version 1.3 0 EC2 WinUtil Driver version 2.0.0 Windows Server 2016 Base Nano Access to all public versions of Windows_Server-2016-English-Nano-Base will be removed in September 2018. For more information about Nano Server lifecycle, including details on launching Nano Server as a Container, see https://learn.microsoft.com/en-us/previous-versions/windows-server/ it-pro/windows-server-2016/get-started/nano-in-semi-annual-channel on the Microsoft website. Monthly AMI updates for 2025 (to date) 184 AWS Windows AMIs Reference Release Changes 2018.08.15 All AMIs Microsoft security updates current to August 14, 2018 AWS Tools for Windows PowerShell version 3.3.335 • • • AMIs now default to use Amazon's NTP service at IP 169.254.169.123 for time synchronization. For more information, see Set the time for your Windows instance. Windows Server 2016 Base Nano Access to all public versions of Windows_Server-2016-English-Nano-Base will be removed in September 2018. For more information about Nano Server lifecycle, including details on launching Nano Server as a Container, see https://learn.microsoft.com/en-us/previous-versions/windows-server/ it-pro/windows-server-2016/get-started/nano-in-semi-annual-channel on the Microsoft website. 2018.07.11 All
windows-ami-reference-031	windows-ami-reference.pdf	31	for 2025 (to date) 184 AWS Windows AMIs Reference Release Changes 2018.08.15 All AMIs Microsoft security updates current to August 14, 2018 AWS Tools for Windows PowerShell version 3.3.335 • • • AMIs now default to use Amazon's NTP service at IP 169.254.169.123 for time synchronization. For more information, see Set the time for your Windows instance. Windows Server 2016 Base Nano Access to all public versions of Windows_Server-2016-English-Nano-Base will be removed in September 2018. For more information about Nano Server lifecycle, including details on launching Nano Server as a Container, see https://learn.microsoft.com/en-us/previous-versions/windows-server/ it-pro/windows-server-2016/get-started/nano-in-semi-annual-channel on the Microsoft website. 2018.07.11 All AMIs • • • Microsoft security updates current to July 10, 2018 EC2Conﬁg version 4.9.2756 SSM Agent 2.2.800.0 2018.06.22 Windows Server 2008 R2 • Resolves an issue with the 2018.06.13 AMIs when changing an instance from a previous generation to a current generation (for example, M4 to M5). Monthly AMI updates for 2025 (to date) 185 AWS Windows AMIs Reference Release Changes 2018.06.13 All AMIs • • • • • • Microsoft security updates current to June 12, 2018 EC2Conﬁg version 4.9.2688 SSM Agent 2.2.619.0 AWS Tools for Windows PowerShell 3.3.283.0 AWS NVMe driver 1.2.0 AWS PV driver 8.2.3 2018.05.09 All AMIs • • • • Microsoft security updates current to May 9, 2018 EC2Conﬁg version 4.9.2644 SSM Agent 2.2.493.0 AWS Tools for Windows PowerShell 3.3.270.0 Windows Server, version 1709 and Windows Server, version 1803 • AMIs are now available. For more information, see Windows Server version 1709 and 1803 AMIs for Amazon EC2. Monthly AMI updates for 2025 (to date) 186 AWS Windows AMIs Reference Release Changes 2018.04.11 All AMIs Microsoft security updates current to April 10, 2018 EC2Conﬁg version 4.9.2586 SSM Agent 2.2.392.0 AWS Tools for Windows PowerShell 3.3.256.0 AWS CloudFormation templates 1.4.30 • • • • • • Serial INF and Intel Chipset INF conﬁgurations to support new instance types SQL Server 2017 • Cumulative update 5 (CU5) SQL Server 2016 SP1 • Cumulative update 8 (CU8) Monthly AMI updates for 2025 (to date) 187 AWS Windows AMIs Reference Release Changes 2018.03.24 All AMIs • • • • • • • • Microsoft security updates current to March 13, 2018 EC2Conﬁg version 4.9.2565 SSM Agent 2.2.355.0 AWS Tools for Windows PowerShell 3.3.245.0 AWS PV driver 8.2 AWS ENA driver 1.2.3.0 Amazon EC2 Hibernate Agent 1.0 (rollback from 2.1.0 in the 2018.03.16 AMI release) AWS EC2WinUtilDriver 1.0.1 (for troubleshooting) Windows Server 2016 • EC2Launch v1 1.3.2000080 2018.03.16 AWS has removed all AWS Windows AMIs dated 2018.03.16 due to an issue with an unquoted path in the conﬁguration for the Amazon EC2 Hibernate Agent. 2018.03.06 All AMIs • AWS PV driver 8.2.1 Monthly AMI updates for 2025 (to date) 188 AWS Windows AMIs Reference Release Changes 2018.02.23 All AMIs • AWS PV driver 7.4.6 (rollback from 8.2 in the 2018.02.13 AMI release) 2018.02.13 All AMIs • • • • • • • • Microsoft security updates current to February 13, 2018 EC2Conﬁg version 4.9.2400 SSM Agent 2.2.160.0 AWS Tools for Windows PowerShell 3.3.225.1 AWS PV driver 8.2 AWS ENA driver 1.2.3.0 AWS NVMe driver 1.0.0.146 Amazon EC2 HibernateAgent 1.0.0 Windows Server 2016 • EC2Launch v1 1.3.740 2018.01.12 All AMIs • Microsoft security updates current to January 9, 2018 Monthly AMI updates for 2025 (to date) 189 AWS Windows AMIs Reference Release Changes 2018.01.05 All AMIs • • • • Microsoft security updates current to January 2018 Registry settings to enable mitigations for the Spectre and Meltdown exploits AWS Tools for Windows PowerShell 3.3.215 EC2Conﬁg version 4.9.2262 Monthly AMI updates for 2017 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2017 on the Microsoft website. Release Changes 2017.12.13 All AMIs • • • • • • Microsoft security updates current to December 12, 2017 EC2Conﬁg version 4.9.2218 AWS CloudFormation templates 1.4.27 AWS NVMe driver 1.02 SSM Agent 2.2.93.0 AWS Tools for Windows PowerShell 3.3.201 2017.11.29 Monthly AMI updates for 2025 (to date) 190 AWS Windows AMIs Release Changes All AMIs • Reference Removed components for Volume Shadow Copy Service (VSS) included in 2017.11.18 and 2017.11.19 due to a compatibility issue with Windows 2017.11.19 Backup. All AMIs • EC2 Hibernate Agent 1.0 (supports hibernation for Spot Instances) 2017.11.18 All AMIs • • • • • • Microsoft security updates current to November 14, 2017 EC2Conﬁg version 4.9.2218 SSM Agent 2.2.64.0 AWS Tools for Windows PowerShell 3.3.182 Elastic Network Adapter (ENA) driver 1.08 (rollback from 1.2.2 in the 2017.10.13 AMI release) Query for the latest AWS Windows AMI using Systems Manager Parameter Store Windows Server 2016 • EC2Launch v1 1.3.640 Monthly AMI updates for 2025 (to date) 191 AWS Windows AMIs Reference Release Changes 2017.10.13 All AMIs Microsoft security updates current to October 11, 2017 EC2Conﬁg version 4.9.2188 SSM Agent 2.2.30.0 AWS
windows-ami-reference-032	windows-ami-reference.pdf	32	1.0 (supports hibernation for Spot Instances) 2017.11.18 All AMIs • • • • • • Microsoft security updates current to November 14, 2017 EC2Conﬁg version 4.9.2218 SSM Agent 2.2.64.0 AWS Tools for Windows PowerShell 3.3.182 Elastic Network Adapter (ENA) driver 1.08 (rollback from 1.2.2 in the 2017.10.13 AMI release) Query for the latest AWS Windows AMI using Systems Manager Parameter Store Windows Server 2016 • EC2Launch v1 1.3.640 Monthly AMI updates for 2025 (to date) 191 AWS Windows AMIs Reference Release Changes 2017.10.13 All AMIs Microsoft security updates current to October 11, 2017 EC2Conﬁg version 4.9.2188 SSM Agent 2.2.30.0 AWS CloudFormation templates 1.4.24 • • • • • Elastic Network Adapter (ENA) driver 1.2.2. (Windows Server 2008 R2 through Windows Server 2016) Monthly AMI updates for 2025 (to date) 192 AWS Windows AMIs Reference Release Changes 2017.10.04 Microsoft SQL Server Windows Server 2016 with Microsoft SQL Server 2017 AMIs are now public in all regions. • • • • Windows_Server-2016-English-Full-SQL_2017_Enterprise-2017.10.04 Windows_Server-2016-English-Full-SQL_2017_Standard-2017.10.04 Windows_Server-2016-English-Full-SQL_2017_Web-2017.10.04 Windows_Server-2016-English-Full-SQL_2017_Express-2017.10.04 Microsoft SQL Server 2017 supports the following features: Machine Learning Services with Python (ML and AI) and R language support Automatic database tuning Clusterless Availability Groups Runs on Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), and Ubuntu. For more information, see Installation guidance for SQL Server on Linux on the Microsoft website. Not supported on Amazon Linux. Windows-Linux cross-OS migrations Resumable online index rebuild Improved adaptive query processing • • • • • • • • Monthly AMI updates for 2025 (to date) 193 AWS Windows AMIs Reference Release Changes Graph data support 2017.09.13 All AMIs • • • • • Microsoft security updates current to September 13, 2017 EC2Conﬁg version 4.9.2106 SSM Agent 2.0.952.0 AWS Tools for Windows PowerShell 3.3.143 AWS CloudFormation templates 1.4.21 2017.08.09 All AMIs • • • Microsoft security updates current to August 9, 2017 EC2Conﬁg version 4.9.2016 SSM Agent 2.0.879.0 Windows Server 2012 R2 • Due to an internal error, these AMIs were released with an older version of AWS Tools for Windows PowerShell, 3.3.58.0. Monthly AMI updates for 2025 (to date) 194 AWS Windows AMIs Reference Release Changes 2017.07.13 All AMIs • • • Microsoft security updates current to July 13, 2017 EC2Conﬁg version 4.9.1981 SSM Agent 2.0.847.0 Windows Server 2016 • Intel SRIOV Driver 2.0.210.0 Monthly AMI updates for 2025 (to date) 195 AWS Windows AMIs Reference Release Changes 2017.06.14 All AMIs • • • • • • • Microsoft security updates current to June 14, 2017 Updates for .NET Framework 4.7 installed from Windows Update Microsoft updates to address the "privilege not held" error using the PowerShell Stop-Computer cmdlet. For more information, see Privilege not held error on the Microsoft website. EC2Conﬁg version 4.9.1900 SSM Agent 2.0.805.0 AWS Tools for Windows PowerShell 3.3.99.0 Internet Explorer 11 for the desktop is the default, instead of the immersive Internet Explorer Windows Server 2016 • EC2Launch v1 1.3.610 2017.05.30 2017.05.22 The Windows_Server-2008-SP2-English-32Bit-Base-2017.05.10 AMI was updated to the Windows_Server-2008-SP2-English-32Bit-Base-2017.05.30 AMI to resolve an issue with password generation. The Windows_Server-2016-English-Full-Base-2017.05.10 AMI was updated to the Windows_Server-2016-English-Full-Base-2017.05.22 AMI after som e log cleaning. Monthly AMI updates for 2025 (to date) 196 AWS Windows AMIs Reference Release Changes 2017.05.10 All AMIs • • • Microsoft security updates current to May 9, 2017 AWS PV Driver v7.4.6 AWS Tools for Windows PowerShell 3.3.83.0 Windows Server 2016 • SSM Agent 2.0.767 2017.04.12 All AMIs • • • Microsoft security updates current to April 11, 2017 AWS Tools for Windows PowerShell 3.3.71.0 AWS CloudFormation templates 1.4.18 Windows Server 2003 to Windows Server 2012 • • EC2Conﬁg version 4.9.1775 SSM Agent 2.0.761.0 Windows Server 2016 • SSM Agent 2.0.730.0 Monthly AMI updates for 2025 (to date) 197 AWS Windows AMIs Reference Release Changes 2017.03.15 All AMIs • • • Microsoft security updates current to March 14, 2017 Current AWS Tools for Windows PowerShell Current AWS CloudFormation templates Windows Server 2003 to Windows Server 2012 • • EC2Conﬁg version 4.7.1631 SSM Agent 2.0.682.0 Windows Server 2016 • • SSM Agent 2.0.706.0 EC2Launch v1 v1.3.540 2017.02.21 Microsoft recently announced that they will not release monthly patches or security updates for the month of February. 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. Monthly AMI updates for 2025 (to date) 198 AWS Windows AMIs Reference Release Changes 2017.01.11 All AMIs • • • Microsoft security updates current to January 10, 2017 Current AWS Tools for Windows PowerShell Current AWS CloudFormation templates Windows Server 2003 to Windows Server 2012 • • EC2Conﬁg version 4.2.1442 SSM Agent 2.0.599.0 Monthly AMI updates for 2016 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2016 on the Microsoft website. Release Changes 2016.12.14 All AMIs • • Microsoft security
windows-ami-reference-033	windows-ami-reference.pdf	33	Services did not release updated Windows Server AMIs in February. Monthly AMI updates for 2025 (to date) 198 AWS Windows AMIs Reference Release Changes 2017.01.11 All AMIs • • • Microsoft security updates current to January 10, 2017 Current AWS Tools for Windows PowerShell Current AWS CloudFormation templates Windows Server 2003 to Windows Server 2012 • • EC2Conﬁg version 4.2.1442 SSM Agent 2.0.599.0 Monthly AMI updates for 2016 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2016 on the Microsoft website. Release Changes 2016.12.14 All AMIs • • Microsoft security updates current to December 13, 2016 Current AWS Tools for Windows PowerShell Windows Server 2003 to Windows Server 2012 • Released EC2Conﬁg version 4.1.1396 Monthly AMI updates for 2025 (to date) 199 AWS Windows AMIs Reference Release Changes • Elastic Network Adapter (ENA) driver 1.0.9.0 (Windows Server 2008 R2 only) Windows Server 2016 New AMIs available in all regions: • Windows_Server-2016-English-Core-Base Microsoft SQL Server All Microsoft SQL Server AMIs with the latest service pack are now public in all regions. These new AMIs replace old SQL Service Pack AMIs going forward. Windows_Server-2008-R2_SP1-English-64Bit-SQL_2012_SP3_ edition-2016.12.14 Windows_Server-2012-RTM-English-64Bit-SQL_201 2_SP3_edition-2016.12.14 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2014_SP2_ edition-2016.12.14 Windows_Server-2012-RTM-English-64Bit-SQL_201 4_SP2_edition-2016.12.14 Windows_Server-2012-R2_RTM-English-64Bit-SQL_2016_SP1_ edition-2016.12.14 • • • • • • Windows_Server-2016-English-Full-SQL_2016_SP1_edition-2016.12.14 Monthly AMI updates for 2025 (to date) 200 AWS Windows AMIs Reference Release Changes SQL Server 2016 SP1 is a major release. 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: • • • • • • • • • Row-level security Dynamic Data Masking Change Data Capture Database snapshot Column store Partitioning Compression In Memory OLTP Always Encrypted 2016.11.23 Windows Server 2003 to Windows Server 2012 • • Released EC2Conﬁg version 4.1.1378 The AMIs released this month, and going forward, use the EC2Conﬁg service to process boot-time conﬁgurations and SSM Agent to process AWS Systems Manager Run Command and Conﬁg requests. EC2Conﬁg no longer processes requests for Systems Manager Run Command and State Manager. The latest EC2Conﬁg installer installs SSM Agent side-by- side with the EC2Conﬁg service. For more information, see Conﬁgure a Windows instance using the EC2Conﬁg service (legacy). Monthly AMI updates for 2025 (to date) 201 AWS Windows AMIs Reference Release Changes 2016.11.09 All AMIs • • • Microsoft security updates current to November 8 2016 Released AWS PV driver, version 7.4.3.0 for Windows 2008 R2 and later Current AWS Tools for Windows PowerShell 2016.10.18 All AMIs • • Microsoft security updates current to October 12, 2016 Current AWS Tools for Windows PowerShell Windows Server 2016 • Released AMIs for Windows Server 2016. These AMIs include signiﬁcant changes. For example, they don't include the EC2Conﬁg service. 2016.9.14 All AMIs • • • Microsoft security updates current to September 13, 2016 Current AWS Tools for Windows PowerShell Renamed AMI Windows_Server-2012-RTM-Japanese-64Bit-SQL_20 08_R3_SP2_Standard to Windows_Server-2012-RTM-Japanese-64Bit- SQL_2008_R2_SP3_Standard 2016.8.26 All Windows Server 2008 R2 AMIs dated 2016.08.11 were updated to ﬁx a known issue. New AMIs are dated 2016.08.25. Monthly AMI updates for 2025 (to date) 202 AWS Windows AMIs Reference Release Changes 2016.8.11 All AMIs EC2Conﬁg v3.19.1153 Microsoft security updates current to August 10, 2016 • • • Enabled the registry key User32 exception handler hardening feature in Internet Explorer for MS15-124 Windows Server 2008 R2, Windows Server 2012 RTM, and Windows Server 2012 R2 Elastic Network Adapter (ENA) Driver 1.0.8.0 ENA AMI property set to enabled • • • AWS PV Driver for Windows Server 2008 R2 was re-released this month because of a known issue. Windows Server 2008 R2 AMI's were removed in July because of this issue. All Windows Server 2008 R2 AMIs for July were removed and rolled back to AMIs dated 2016.06.15, because of an issue discovered in the AWS PV driver. The AWS PV driver issue has been ﬁxed. The August AMI release will include Windows Server 2008 R2 AMIs with the ﬁxed AWS PV driver and July/August Windows updates. 2016.8.2 Monthly AMI updates for 2025 (to date) 203 AWS Windows AMIs Reference Release Changes 2016.7.26 All AMIs EC2Conﬁg v3.18.1118 • • 2016.07.13 AMIs were missing security patches. AMIs were re-patched. Additional processes were put in place to verify successful patch installat ions going forward. 2016.7.13 All AMIs • • • • Microsoft security updates current to July 2016 Current AWS Tools for Windows PowerShell Updated AWS PV Driver 7.4.2.0 AWS PV Driver for Windows Server 2008 R2 Monthly AMI updates for 2025 (to date) 204 AWS Windows AMIs Reference Release Changes 2016.6.16 All AMIs • • • Microsoft security updates current to June 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.17.1032 Microsoft SQL Server • Released 10 AMIs that include 64-bit versions of Microsoft SQL Server 2016. If using the Amazon EC2 console, navigate to Images, AMIs,
windows-ami-reference-034	windows-ami-reference.pdf	34	installat ions going forward. 2016.7.13 All AMIs • • • • Microsoft security updates current to July 2016 Current AWS Tools for Windows PowerShell Updated AWS PV Driver 7.4.2.0 AWS PV Driver for Windows Server 2008 R2 Monthly AMI updates for 2025 (to date) 204 AWS Windows AMIs Reference Release Changes 2016.6.16 All AMIs • • • Microsoft security updates current to June 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.17.1032 Microsoft SQL Server • Released 10 AMIs that include 64-bit versions of Microsoft SQL Server 2016. If using the Amazon EC2 console, navigate to Images, AMIs, Public Images, and type Windows_Server-2012-R2_RTM-English-6 4Bit-SQL_2016_Standard in the search bar. 2016.5.11 All AMIs • • • • Microsoft security updates current to May 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.16.930 MS15-011 Active Directory patch installed Windows Server 2012 R2 • Intel SRIOV Driver 1.0.16.1 Monthly AMI updates for 2025 (to date) 205 AWS Windows AMIs Reference Release Changes 2016.4.13 All AMIs • • • Microsoft security updates current to April 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.15.880 2016.3.9 All AMIs • • • Microsoft security updates current to March 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.14.786 2016.2.10 All AMIs • • • Microsoft security updates current to February 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.13.727 2016.1.25 All AMIs • • • Microsoft security updates current to January 2016 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.12.649 Monthly AMI updates for 2025 (to date) 206 AWS Windows AMIs Reference Release Changes 2016.1.5 All AMIs • Current AWS Tools for Windows PowerShell Monthly AMI updates for 2015 For more information, see Description of Software Update Services and Windows Server Update Services changes in content for 2015 on the Microsoft website. Release Changes 2015.12.15 All AMIs • • Microsoft security updates current to December 2015 Current AWS Tools for Windows PowerShell 2015.11.11 All AMIs • • • • Microsoft security updates current to November 2015 Current AWS Tools for Windows PowerShell EC2Conﬁg service version 3.11.521 CFN Agent updated to latest version 2015.10.26 2015.10.14 Corrected boot volume sizes of base AMIs to be 30GB instead of 35GB All AMIs • Monthly AMI updates for 2025 (to date) 207 AWS Windows AMIs Reference Release Changes • • • • • Microsoft security updates current to October 2015 EC2Conﬁg service version 3.10.442 Current AWS Tools for Windows PowerShell Updated SQL Service Packs to latest versions for all SQL variants Removed old entries in Event Logs AMI Names have been changed to reﬂect the latest service pack. For example, the latest AMI with Server 2012 and SQL 2014 Standard is named “Windows_Server-2012-RTM-English-64Bit-SQL_2014_SP1_Sta ndard-2015.10.26“, not “Windows_Server-2012-RTM-English-64Bit- SQL_2014_RTM_Standard-2015.10.26“. 2015.9.9 All AMIs • • • • Microsoft security updates current to September 2015 EC2Conﬁg service version 3.9.359 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts Monthly AMI updates for 2025 (to date) 208 AWS Windows AMIs Reference Release Changes 2015.8.18 All AMIs • • • Microsoft security updates current to August 2015 EC2Conﬁg service version 3.8.294 Current AWS Tools for Windows PowerShell Only AMIs with Windows Server 2012 and Windows Server 2012 R2 • AWS PV Driver 7.3.2 2015.7.21 All AMIs Microsoft security updates current to July 2015 EC2Conﬁg service version 3.7.308 Current AWS Tools for Windows PowerShell • • • • Modiﬁed AMI descriptions of SQL images for consistency Monthly AMI updates for 2025 (to date) 209 AWS Windows AMIs Reference Release Changes 2015.6.10 All AMIs • • • • Microsoft security updates current to June 2015 EC2Conﬁg service version 3.6.269 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts Only AMIs with Windows Server 2012 R2 • AWS PV Driver 7.3.1 2015.5.13 All AMIs • • • Microsoft security updates current to May 2015 EC2Conﬁg service version 3.5.228 Current AWS Tools for Windows PowerShell 2015.04.15 All AMIs • • • Microsoft security updates current to April 2015 EC2Conﬁg service version 3.3.174 Current AWS Tools for Windows PowerShell Monthly AMI updates for 2025 (to date) 210 AWS Windows AMIs Reference Release Changes 2015.03.11 All AMIs • • • Microsoft security updates current to March 2015 EC2Conﬁg service version 3.2.97 Current AWS Tools for Windows PowerShell Only AMIs with Windows Server 2012 R2 • AWS PV Driver 7.3.0 2015.02.11 All AMIs • • • • Microsoft security updates current to February 2015 EC2Conﬁg service version 3.0.54 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts 2015.01.14 All AMIs • • • • Microsoft security updates current to January 2015 EC2Conﬁg service version 2.3.313 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts Monthly AMI updates for 2025 (to date) 211 AWS Windows AMIs Reference Subscribe to AWS Windows AMI notiﬁcations Whenever AWS Windows
windows-ami-reference-035	windows-ami-reference.pdf	35	service version 3.2.97 Current AWS Tools for Windows PowerShell Only AMIs with Windows Server 2012 R2 • AWS PV Driver 7.3.0 2015.02.11 All AMIs • • • • Microsoft security updates current to February 2015 EC2Conﬁg service version 3.0.54 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts 2015.01.14 All AMIs • • • • Microsoft security updates current to January 2015 EC2Conﬁg service version 2.3.313 Current AWS Tools for Windows PowerShell Current AWS CloudFormation helper scripts Monthly AMI updates for 2025 (to date) 211 AWS Windows AMIs Reference Subscribe to AWS Windows AMI notiﬁcations Whenever AWS Windows AMIs are released, we send notiﬁcations to the subscribers of the ec2- windows-ami-update topic. Whenever released AWS Windows AMIs are made private, we send notiﬁcations to the subscribers of the ec2-windows-ami-private topic. If you no longer want to receive these notiﬁcations, use the following procedure to unsubscribe. To be notiﬁed when new AMIs are released or when previously released AMIs are made private, subscribe to notiﬁcations using Amazon SNS. To subscribe to AWS Windows AMI notiﬁcations 1. Open the Amazon SNS console at https://console.aws.amazon.com/sns/v3/home. 2. In the navigation bar, change the Region to US East (N. Virginia), if necessary. You must use this Region because the Amazon SNS notiﬁcations that you are subscribing to were created in this Region. 3. In the navigation pane, choose Subscriptions. 4. Choose Create subscription. 5. For the Create subscription dialog box, do the following: a. For Topic ARN, copy and paste one of the following Amazon Resource Names (ARNs): • arn:aws:sns:us-east-1:801119661308:ec2-windows-ami-update • arn:aws:sns:us-east-1:801119661308:ec2-windows-ami-private For AWS GovCloud (US) Regions: arn:aws-us-gov:sns:us-gov-west-1:077303321853:ec2-windows-ami-update b. c. For Protocol, choose Email. For Endpoint, enter an email address that you can use to receive the notiﬁcations. d. Choose Create subscription. 6. You'll receive a conﬁrmation email with the subject line AWS Notification - Subscription Confirmation. Open the email and choose Conﬁrm subscription to complete your subscription. 212 AWS Windows AMIs Reference To unsubscribe from AWS Windows AMI notiﬁcations 1. Open the Amazon SNS console at https://console.aws.amazon.com/sns/v3/home. 2. 3. 4. In the navigation bar, change the Region to US East (N. Virginia), if necessary. You must use this Region because the Amazon SNS notiﬁcations were created in this Region. In the navigation pane, choose Subscriptions. Select the subscriptions and then choose Delete. When prompted for conﬁrmation, choose Delete. 213 AWS Windows AMIs Reference Security in AWS Windows AMI Cloud security at AWS is the highest priority. As an AWS customer, you beneﬁt from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations. Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud: • Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third- party auditors regularly test and verify the eﬀectiveness of our security as part of the AWS Compliance Programs. To learn about the compliance programs that apply to Windows AMI, see AWS Services in Scope by Compliance Program. • Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations For detailed information about how to conﬁgure Amazon EC2 to meet your security and compliance objectives, see Security in Amazon EC2 in the User Guide for Windows Instances. 214 AWS Windows AMIs Reference Document history for the AWS Windows AMI reference The following table describes documentation changes for the AWS Windows AMI reference content. For monthly AMI version release notes, see AWS Windows AMI version history. Change Description Date Archive 2014 release notes Yearly archive of release notes more than ten years old. January 21, 2025 Add support for Windows Server 2025 Release AMIs for Windows Server 2025. November 4, 2024 Initial release Initial release of the AWS Windows AMI reference. April 30, 2024 215
WindowsGuide-001	WindowsGuide.pdf	1	Windows User Guide Amazon FSx for Windows File Server Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. Amazon FSx for Windows File Server Windows User Guide Amazon FSx for Windows File Server: Windows User Guide Copyright © 2025 Amazon Web Services, Inc. and/or its aﬃliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon. Amazon FSx for Windows File Server Table of Contents Windows User Guide What is FSx for Windows File Server? ............................................................................................ 1 Amazon FSx resources ................................................................................................................................. 1 Accessing ﬁle shares ............................................................................................................................... 2 Security and data protection ..................................................................................................................... 2 Availability and durability ........................................................................................................................... 3 Managing ﬁle systems ................................................................................................................................. 3 Price and performance ﬂexibility .............................................................................................................. 3 Pricing for Amazon FSx ............................................................................................................................... 4 Assumptions ................................................................................................................................................... 4 Prerequisites ............................................................................................................................................. 4 Amazon FSx for Windows File Server forums ........................................................................................ 5 Are you a ﬁrst-time user of Amazon FSx? .............................................................................................. 5 FSx for Windows best practices ...................................................................................................... 6 General best practices ................................................................................................................................. 6 Creating a monitoring plan ................................................................................................................... 6 Ensuring that your ﬁle systems have suﬃcient resources .............................................................. 6 Security best practices ................................................................................................................................ 6 Network security ..................................................................................................................................... 7 Active Directory ............................................................................................................................................. 7 Avoid losing availability due to Active Directory misconﬁguration .............................................. 8 Windows ACLs .......................................................................................................................................... 9 Conﬁguring and right-sizing your ﬁle system ........................................................................................ 9 Selecting a deployment type ............................................................................................................... 9 Selecting a throughput capacity .......................................................................................................... 9 Increasing storage capacity and throughput capacity .................................................................. 10 Modifying throughput capacity during idle periods ...................................................................... 10 Getting started .............................................................................................................................. 11 Setting up your AWS account ................................................................................................................. 11 .................................................................................................................................................................. 12 Step 1. Setting up an Active Directory .................................................................................................. 13 Step 2: Launch a Windows instance in the Amazon EC2 console .................................................... 15 Step 3: Connect to your instance ........................................................................................................... 16 Step 4: Join your instance to your AWS Directory Service directory ............................................... 19 Step 5. Create your ﬁle system ............................................................................................................... 20 iii Amazon FSx for Windows File Server Windows User Guide Step 6. Map your ﬁle share to an EC2 instance running Windows Server ...................................... 26 Step 7. Write data to your ﬁle share ..................................................................................................... 27 Step 8. Back up your ﬁle system ............................................................................................................ 27 Step 9. Clean up resources ...................................................................................................................... 28 Accessing your data ....................................................................................................................... 30 Supported clients ....................................................................................................................................... 30 Accessing data from within the AWS Cloud ......................................................................................... 31 Accessing data from a diﬀerent VPC, AWS account, or AWS Region .......................................... 32 Accessing data from on-premises ........................................................................................................... 33 Accessing data using default DNS names ............................................................................................. 34 Using Kerberos authentication with DNS names ........................................................................... 35 Support for Distributed File System (DFS) namespaces .................................................................... 35 Accessing data using DNS aliases ........................................................................................................... 35 Using Kerberos authentication and encryption with DNS aliases ............................................... 36 Associate DNS aliases with your ﬁle system ................................................................................... 37 Conﬁgure service principal names (SPNs) for Kerberos ................................................................ 38 Update or create a DNS CNAME record ........................................................................................... 41 Enforcing Kerberos authentication using Group Policy Objects (GPOs) .................................... 43 Accessing data using ﬁle shares .............................................................................................................. 44 Mapping ﬁle shares .............................................................................................................................. 44 Mapping a ﬁle share on an Amazon EC2 Windows instance ....................................................... 45 Mounting a ﬁle share on an Amazon EC2 Mac instance ............................................................... 47 Mounting a ﬁle share on an Amazon EC2 Linux instance ............................................................ 50 Automatically mount ﬁle shares on an Amazon EC2 Linux instance ......................................... 55 Managing ﬁle shares ................................................................................................................................. 58 New-FSxSmbShare command fails with a one-way trust ............................................................. 64 Availability and durability ............................................................................................................ 65 Choosing Single-AZ or Multi-AZ ﬁle system deployment type ........................................................ 65 Feature support by deployment type .............................................................................................. 66 Failing over process ................................................................................................................................... 66 Failover experience on Windows clients .......................................................................................... 67 Failover experience on Linux clients ................................................................................................. 67 Testing failover on a ﬁle system ....................................................................................................... 68 Single-AZ and Multi-AZ ﬁle system resources ..................................................................................... 68 Subnets ................................................................................................................................................... 68 File system elastic network interfaces ............................................................................................. 69 iv Amazon FSx for Windows File Server Windows User Guide Working with Active Directory ..................................................................................................... 70 Using AWS Managed Microsoft AD ........................................................................................................ 71 Networking prerequisites .................................................................................................................... 72 Using a resource forest isolation model .......................................................................................... 77 Test your Active Directory conﬁguration ......................................................................................... 77 Using AWS Managed Microsoft AD in diﬀerent VPC or account ................................................. 78 Validating connectivity to your Active Directory domain controllers ......................................... 79 Using a self-managed Active Directory ................................................................................................. 82 Prerequisites ........................................................................................................................................... 83 Best practices when using a self-managed Active Directory ....................................................... 89 Amazon FSx service account .............................................................................................................. 90 Delegating privileges to Amazon FSx ............................................................................................... 91 Validating your Active Directory conﬁguration .............................................................................. 92 Join FSx to a self-managed Active Directory .................................................................................. 97 Getting IP addresses for manual DNS entries .............................................................................. 106 Update self-managed Active Directory .......................................................................................... 107 Changing the Amazon FSx
WindowsGuide-002	WindowsGuide.pdf	2	model .......................................................................................... 77 Test your Active Directory conﬁguration ......................................................................................... 77 Using AWS Managed Microsoft AD in diﬀerent VPC or account ................................................. 78 Validating connectivity to your Active Directory domain controllers ......................................... 79 Using a self-managed Active Directory ................................................................................................. 82 Prerequisites ........................................................................................................................................... 83 Best practices when using a self-managed Active Directory ....................................................... 89 Amazon FSx service account .............................................................................................................. 90 Delegating privileges to Amazon FSx ............................................................................................... 91 Validating your Active Directory conﬁguration .............................................................................. 92 Join FSx to a self-managed Active Directory .................................................................................. 97 Getting IP addresses for manual DNS entries .............................................................................. 106 Update self-managed Active Directory .......................................................................................... 107 Changing the Amazon FSx service account .................................................................................. 109 Monitoring self-managed Active Directory updates ................................................................... 110 Performance ................................................................................................................................. 114 File system performance ........................................................................................................................ 114 Additional performance considerations .............................................................................................. 115 Latency .................................................................................................................................................. 116 Throughput and IOPS ........................................................................................................................ 116 Single-client performance ................................................................................................................ 116 Burst performance .............................................................................................................................. 116 Throughput capacity & performance .................................................................................................. 117 Choosing throughput capacity .............................................................................................................. 119 Storage conﬁguration & performance ................................................................................................ 121 HDD burst performance .................................................................................................................... 121 Example: storage capacity and throughput capacity ....................................................................... 122 Measuring performance using CloudWatch metrics ......................................................................... 123 Troubleshooting performance ............................................................................................................... 123 Determine ﬁle system throughput and IOPS limits .................................................................... 123 What is network I/O vs. disk I/O? Why are they diﬀerent? ....................................................... 124 Why is CPU or memory usage high when network I/O is low? ................................................ 124 v Amazon FSx for Windows File Server Windows User Guide What is bursting? How much bursting is my ﬁle system using? What happens when burst credits run out? ................................................................................................................................... 125 I see a warning on the Monitoring & performance page – do I need to change my ﬁle system’s conﬁguration? ..................................................................................................................... 125 My metrics were temporarily missing, should I be concerned? ................................................. 126 Administering ﬁle systems .......................................................................................................... 127 Amazon FSx ﬁle system status ............................................................................................................. 128 Using the Amazon FSx CLI for PowerShell ......................................................................................... 129 Starting an Amazon FSx remote PowerShell session ....................................................................... 131 One-time ﬁle system setup tasks ......................................................................................................... 132 Managing storage consumption ...................................................................................................... 132 Turning on shadow copies to enable end-users to recover ﬁles and folders to previous versions ................................................................................................................................................. 133 Enforcing encryption in transit ........................................................................................................ 133 Troubleshooting access to the Amazon FSx CLI on PowerShell ..................................................... 133 The ﬁle system's security group lacks the required inbound rules to allow a remote PowerShell connection ...................................................................................................................... 134 You have an external trust conﬁgured between the AWS managed Microsoft Active Directory and your on-premises Active Directory ........................................................................ 134 A language localization error occurs when trying to initiate a remote PowerShell session . 134 Maintenance window .............................................................................................................................. 134 Changing the weekly maintenance window ...................................................................................... 135 DNS aliases ................................................................................................................................................ 136 DNS alias status .................................................................................................................................. 138 Using DNS aliases with Kerberos .................................................................................................... 138 Viewing existing DNS aliases ........................................................................................................... 139 Associating DNS aliases with ﬁle systems ..................................................................................... 139 Managing DNS aliases on existing ﬁle systems ........................................................................... 141 User sessions and open ﬁles ................................................................................................................. 143 Using the GUI to manage users and sessions .............................................................................. 144 Using PowerShell to manage user sessions and open ﬁles ....................................................... 147 Managing storage .................................................................................................................................... 147 Optimizing storage costs .................................................................................................................. 148 Managing storage capacity ............................................................................................................... 149 Managing storage types .................................................................................................................... 152 Managing SSD IOPS ........................................................................................................................... 153 vi Amazon FSx for Windows File Server Windows User Guide Data deduplication ............................................................................................................................. 154 Managing storage quotas ................................................................................................................. 158 Increasing storage capacity .............................................................................................................. 160 Monitoring storage increases ........................................................................................................... 161 Increasing storage capacity dynamically ....................................................................................... 164 Updating storage type ...................................................................................................................... 170 Monitoring storage type updates ................................................................................................... 171 Updating the SSD IOPS .................................................................................................................... 172 Monitoring provisioned SSD IOPS updates ................................................................................... 173 Managing data deduplication .......................................................................................................... 174 Troubleshooting data deduplication .............................................................................................. 178 Using DFS Namespaces .......................................................................................................................... 180 Using DFS Namespaces ..................................................................................................................... 180 Improving performance with shards .............................................................................................. 181 Group ﬁle systems into one namespace ........................................................................................ 181 Sharding data using DFS Namespaces for scale-out performance ........................................... 183 Managing throughput capacity ............................................................................................................. 185 How throughput scaling works ....................................................................................................... 185 Knowing when to modify throughput capacity ........................................................................... 186 Modifying throughput capacity ....................................................................................................... 187 Monitoring throughput capacity updates ..................................................................................... 188 Tagging resources .................................................................................................................................... 191 Tag basics ............................................................................................................................................. 191 Tagging your resources ..................................................................................................................... 192 Tag restrictions .................................................................................................................................... 193 Permissions required to tag resources ........................................................................................... 193 Update a ﬁle system using the AWS CLI ............................................................................................ 194 Protecting your data ................................................................................................................... 196 Protecting your data with backups ...................................................................................................... 196 Working with automatic daily backups ......................................................................................... 198 Working with user-initiated backups ............................................................................................. 198 Using AWS Backup with Amazon FSx ............................................................................................ 199 Copying backups ................................................................................................................................. 200 Restoring backups to new ﬁle system ........................................................................................... 202 Creating user-initiated backups ....................................................................................................... 203 Deleting backups ................................................................................................................................ 203 vii Amazon FSx for Windows File Server Windows User Guide Size of backups ................................................................................................................................... 204 Copying backups ................................................................................................................................. 205 Restoring a backup ............................................................................................................................ 206 Protecting data with shadow copies ................................................................................................... 207 Best practices ...................................................................................................................................... 208 Setting up shadow copies ................................................................................................................ 209 Conﬁgure shadow copies to use default settings ........................................................................ 213 Setting the maximum amount of shadow copy storage ............................................................ 215 Viewing shadow copy storage ......................................................................................................... 217 Creating a
WindowsGuide-003	WindowsGuide.pdf	3	backups ............................................................................................. 198 Using AWS Backup with Amazon FSx ............................................................................................ 199 Copying backups ................................................................................................................................. 200 Restoring backups to new ﬁle system ........................................................................................... 202 Creating user-initiated backups ....................................................................................................... 203 Deleting backups ................................................................................................................................ 203 vii Amazon FSx for Windows File Server Windows User Guide Size of backups ................................................................................................................................... 204 Copying backups ................................................................................................................................. 205 Restoring a backup ............................................................................................................................ 206 Protecting data with shadow copies ................................................................................................... 207 Best practices ...................................................................................................................................... 208 Setting up shadow copies ................................................................................................................ 209 Conﬁgure shadow copies to use default settings ........................................................................ 213 Setting the maximum amount of shadow copy storage ............................................................ 215 Viewing shadow copy storage ......................................................................................................... 217 Creating a custom shadow copy schedule .................................................................................... 218 Viewing the shadow copy schedule ................................................................................................ 219 Creating a shadow copy .................................................................................................................... 220 Viewing existing shadow copies ...................................................................................................... 220 Deleting shadow copies .................................................................................................................... 220 Deleting a shadow copy schedule ................................................................................................... 222 Deleting a shadow copy conﬁguration .......................................................................................... 222 Troubleshooting shadow copies ...................................................................................................... 223 Scheduled replication .............................................................................................................................. 224 Using FSx for Windows File Server with Microsoft SQL Server ................................................ 225 Using Amazon FSx for Active SQL Server Data Files ........................................................................ 225 Create a Continuously Available Share .......................................................................................... 226 Conﬁgure SMB timeout settings ..................................................................................................... 226 Using Amazon FSx as an SMB File Share Witness ............................................................................ 226 Migrating to Amazon FSx ........................................................................................................... 227 Migrating ﬁles to FSx for Windows File Server ................................................................................. 227 Migrating best practices .................................................................................................................... 228 Migrating ﬁles using AWS DataSync .............................................................................................. 228 Migrating ﬁles using Robocopy ....................................................................................................... 231 Migrating ﬁle share conﬁgurations ...................................................................................................... 235 Migrating your on-premises DNS conﬁguration to FSx for Windows File Server ........................ 237 Cutting over to FSx for Windows File Server ..................................................................................... 240 Preparing for the cutover to Amazon FSx .................................................................................... 241 Conﬁgure SPNs for Kerberos authentication ................................................................................ 241 Update the DNS CNAME records for the Amazon FSx ﬁle system ........................................... 245 Monitoring ﬁle systems ............................................................................................................... 247 Automated and manual monitoring .................................................................................................... 247 viii Amazon FSx for Windows File Server Windows User Guide Automated tools ................................................................................................................................. 247 Manual monitoring tools .................................................................................................................. 248 Monitoring with Amazon CloudWatch ................................................................................................ 249 Metrics and dimensions .................................................................................................................... 250 Using CloudWatch metrics ............................................................................................................... 256 Performance warnings and recommendations ............................................................................. 260 Accessing ﬁle system metrics ........................................................................................................... 261 Creating CloudWatch alarms ............................................................................................................ 266 CloudTrail logs .......................................................................................................................................... 268 Amazon FSx information in CloudTrail .......................................................................................... 269 Understanding Amazon FSx log ﬁle entries ................................................................................. 270 Security ........................................................................................................................................ 272 Data protection ........................................................................................................................................ 273 Data encryption .................................................................................................................................. 274 Encryption at rest ............................................................................................................................... 274 Encryption in transit .......................................................................................................................... 276 Windows ACLs .......................................................................................................................................... 278 Related Links ....................................................................................................................................... 279 File system access control with Amazon VPC .................................................................................... 279 Amazon VPC Security Groups .......................................................................................................... 279 Amazon VPC Network ACLs ............................................................................................................. 283 Logging end user access ........................................................................................................................ 284 Audit event log destinations ............................................................................................................ 285 Migrating your audit controls .......................................................................................................... 287 Viewing event logs ............................................................................................................................. 287 Setting ﬁle and folder auditing controls ....................................................................................... 294 Managing ﬁle access auditing .......................................................................................................... 296 Identity and access management ......................................................................................................... 301 Audience ............................................................................................................................................... 301 Authenticating with identities ......................................................................................................... 302 Managing access using policies ....................................................................................................... 305 How Amazon FSx for Windows File Server works with IAM ...................................................... 308 Identity-based policy examples ....................................................................................................... 314 AWS managed policies ...................................................................................................................... 317 Troubleshooting .................................................................................................................................. 331 Using tags with Amazon FSx ........................................................................................................... 332 ix Amazon FSx for Windows File Server Windows User Guide Using service-linked roles ................................................................................................................. 337 Compliance Validation ............................................................................................................................ 343 Interface VPC endpoints ......................................................................................................................... 344 Considerations for Amazon FSx interface VPC endpoints ......................................................... 345 Creating an interface VPC endpoint for Amazon FSx API .......................................................... 345 Creating a VPC endpoint policy for Amazon FSx ........................................................................ 346 Working with other services ....................................................................................................... 347 Using Amazon FSx with Amazon AppStream 2.0 ............................................................................. 347 Providing personal persistent storage to each user .................................................................... 348 Providing a shared folder across users .......................................................................................... 350 Using FSx for Windows File Server with Amazon Kendra ............................................................... 351 File system performance ................................................................................................................... 352 Quotas .......................................................................................................................................... 353 Quotas that you can increase ............................................................................................................... 353 Resource quotas for each ﬁle system .................................................................................................. 354 Additional considerations ....................................................................................................................... 355 Quotas speciﬁc to Microsoft Windows ................................................................................................ 356 Troubleshooting ........................................................................................................................... 357 You can't access your ﬁle system ......................................................................................................... 357 The ﬁle system elastic network interface was modiﬁed or deleted ......................................... 358 The Elastic IP address attached to the ﬁle system elastic network interface was deleted ... 358 The ﬁle system security group lacks the required inbound or outbound rules. ..................... 358 The compute instance's security group lacks the required outbound rules ............................ 358 Compute instance not joined to an Active Directory .................................................................. 358 The ﬁle share doesn't exist .............................................................................................................. 359 Active Directory user lacks required permissions ........................................................................ 359 Allow Full control NTFS ACL permissions removed ..................................................................... 359 Can't access a ﬁle system using an on-premises client .............................................................. 359 New ﬁle system is not registered in DNS ...................................................................................... 360 Can't access the ﬁle system using a DNS alias ............................................................................. 360 Can't access the ﬁle system using an IP address ......................................................................... 362 Creating ﬁle system fails ........................................................................................................................ 362 Misconﬁgured VPC security group .................................................................................................. 363 Duplicate ﬁle
WindowsGuide-004	WindowsGuide.pdf	4	security group lacks the required outbound rules ............................ 358 Compute instance not joined to an Active Directory .................................................................. 358 The ﬁle share doesn't exist .............................................................................................................. 359 Active Directory user lacks required permissions ........................................................................ 359 Allow Full control NTFS ACL permissions removed ..................................................................... 359 Can't access a ﬁle system using an on-premises client .............................................................. 359 New ﬁle system is not registered in DNS ...................................................................................... 360 Can't access the ﬁle system using a DNS alias ............................................................................. 360 Can't access the ﬁle system using an IP address ......................................................................... 362 Creating ﬁle system fails ........................................................................................................................ 362 Misconﬁgured VPC security group .................................................................................................. 363 Duplicate ﬁle system administrators group names ..................................................................... 363 DNS servers or domain controllers unreachable ......................................................................... 364 Invalid service account credentials ................................................................................................. 365 x Amazon FSx for Windows File Server Windows User Guide Insuﬃcient service account permissions ........................................................................................ 366 Service account capacity exceeded ................................................................................................. 367 Can't access the OU ........................................................................................................................... 367 Bad ﬁle system admin group ........................................................................................................... 368 Amazon FSx lost connectivity in domain ...................................................................................... 369 Service account does not have correct permissions .................................................................... 369 Unicode characters used in creation parameters ......................................................................... 370 Switching storage type to HDD while restoring a backup fails ................................................. 371 File system is in a misconﬁgured state ............................................................................................... 371 Misconﬁgured ﬁle system: Amazon FSx can't reach either the DNS servers or domain controllers for your domain. ............................................................................................................ 373 Misconﬁgured ﬁle system: The service account credentials are invalid ................................... 374 Misconﬁgured ﬁle system: The service account provided doesn't have permission to join the ﬁle system to the domain ......................................................................................................... 374 Misconﬁgured ﬁle system: The service account can't join any more computers to domain . 375 Misconﬁgured ﬁle system: The service account doesn't have access to the OU .................... 375 You can't conﬁgure DFS-R on a Multi-AZ or Single-AZ 2 ﬁle system ............................................ 376 Storage or throughput capacity updates fail ..................................................................................... 376 Storage capacity increase fails because Amazon FSx can't access the ﬁle system's AWS KMS key .......................................................................................................................................................... 376 Storage or throughput capacity update fails because the self-managed Active Directory is misconﬁgured ...................................................................................................................................... 377 Storage capacity increase fails because of insuﬃcient throughput capacity ......................... 377 Throughput capacity update to 8 MBps fails ............................................................................... 377 Document history ........................................................................................................................ 379 xi Amazon FSx for Windows File Server Windows User Guide What is FSx for Windows File Server? Amazon FSx for Windows File Server provides fully managed Microsoft Windows ﬁle servers, backed by a fully native Windows ﬁle system. FSx for Windows File Server has the features, performance, and compatibility to easily lift and shift enterprise applications to the AWS Cloud. Amazon FSx supports a broad set of enterprise Windows workloads with fully managed ﬁle storage built on Microsoft Windows Server. Amazon FSx has native support for Windows ﬁle system features and for the industry-standard Server Message Block (SMB) protocol to access ﬁle storage over a network. Amazon FSx is optimized for enterprise applications in the AWS Cloud, with native Windows compatibility, enterprise performance and features, and consistent sub-millisecond latencies. With ﬁle storage on Amazon FSx, the code, applications, and tools that Windows developers and administrators use today can continue to work unchanged. Windows applications and workloads ideal for Amazon FSx include business applications, home directories, web serving, content management, data analytics, software build setups, and media processing workloads. As a fully managed service, FSx for Windows File Server eliminates the administrative overhead of setting up and provisioning ﬁle servers and storage volumes. Additionally, Amazon FSx keeps Windows software up to date, detects and addresses hardware failures, and performs backups. It also provides rich integration with other AWS services like AWS IAM, AWS Directory Service for Microsoft Active Directory, Amazon WorkSpaces, AWS Key Management Service, and AWS CloudTrail. FSx for Windows File Server resources: ﬁle systems, backups, and ﬁle shares The primary resources in Amazon FSx are ﬁle systems and backups. A ﬁle system is where you store and access your ﬁles and folders. A ﬁle system is made up of one or more Windows ﬁle servers and storage volumes. When you create a ﬁle system, you specify an amount of storage capacity (in GiB), SSD IOPS, and throughput capacity (in MBps). You can modify these properties as your needs change after you create the ﬁle system. For more information, see Managing storage capacity, Managing SSD IOPS, and Managing throughput capacity. FSx for Windows File Server backups are ﬁle-system-consistent, highly durable, and incremental. To ensure ﬁle system consistency, Amazon FSx uses the Volume Shadow Copy Service (VSS) in Amazon FSx resources 1 Amazon FSx for Windows File Server Windows User Guide Microsoft Windows. Automatic daily backups are turned on by default when you create a ﬁle system, and you can also take additional manual backups at any time. For more information, see Protecting your data with backups. A Windows ﬁle share is a speciﬁc folder (and its subfolders) within your ﬁle system that
WindowsGuide-005	WindowsGuide.pdf	5	capacity, Managing SSD IOPS, and Managing throughput capacity. FSx for Windows File Server backups are ﬁle-system-consistent, highly durable, and incremental. To ensure ﬁle system consistency, Amazon FSx uses the Volume Shadow Copy Service (VSS) in Amazon FSx resources 1 Amazon FSx for Windows File Server Windows User Guide Microsoft Windows. Automatic daily backups are turned on by default when you create a ﬁle system, and you can also take additional manual backups at any time. For more information, see Protecting your data with backups. A Windows ﬁle share is a speciﬁc folder (and its subfolders) within your ﬁle system that you make accessible to your compute instances with SMB. Your ﬁle system already comes with a default Windows ﬁle share called \share. You can create and manage as many other Windows ﬁle shares as you want by using the Shared Folders graphical user interface (GUI) tool on Windows. For more information, see Accessing data using ﬁle shares. File shares are accessed using either the ﬁle system's DNS name or DNS aliases that you associate with the ﬁle system. For more information, see Managing DNS aliases. Accessing ﬁle shares Amazon FSx is accessible from compute instances with the SMB protocol (supporting versions 2.0 to 3.1.1). You can access your shares from all Windows versions starting from Windows Server 2008 and Windows 7, and also from current versions of Linux. You can map your Amazon FSx ﬁle shares on Amazon Elastic Compute Cloud (Amazon EC2) instances, and on WorkSpaces instances, Amazon AppStream 2.0 instances, and VMware Cloud on AWS VMs. You can access your ﬁle shares from on-premises compute instances using AWS Direct Connect or AWS VPN. In addition to accessing ﬁle shares that are in the same VPC, AWS account, and AWS Region as the ﬁle system, you can also access your shares from compute instances that are in a diﬀerent Amazon VPC, account, or AWS Region. You do so using VPC peering or transit gateways. For more information, see Accessing data from within the AWS Cloud. Security and data protection Amazon FSx provides multiple levels of security and compliance to help ensure that your data is protected. It automatically encrypts data at rest (for both ﬁle systems and backups) using keys that you manage in AWS Key Management Service (AWS KMS). Data in transit is also automatically encrypted using SMB Kerberos session keys. It has been assessed to comply with ISO, PCI-DSS, and SOC certiﬁcations, and is HIPAA eligible. Amazon FSx provides access control at the ﬁle and folder level with Windows access control lists (ACLs). It provides access control at the ﬁle system level using Amazon Virtual Private Cloud (Amazon VPC) security groups. In addition, it provides access control at the API level using AWS Identity and Access Management (IAM) access policies. Users accessing ﬁle systems Accessing ﬁle shares 2 Amazon FSx for Windows File Server Windows User Guide are authenticated with Microsoft Active Directory. Amazon FSx integrates with AWS CloudTrail to monitor and log your API calls letting you see actions taken by users on your Amazon FSx resources. Additionally, it protects your data by taking highly durable backups of your ﬁle system automatically on a daily basis and allows you to take additional backups at any point. For more information, see Security in Amazon FSx. Availability and durability FSx for Windows File Server oﬀers ﬁle systems with two levels of availability and durability. Single- AZ ﬁles ensure high availability within a single Availability Zone (AZ) by automatically detecting and addressing component failures. In addition, Multi-AZ ﬁle systems provide high availability and failover support across multiple Availability Zones by provisioning and maintaining a standby ﬁle server in a separate Availability Zone within an AWS Region. To learn more about Single-AZ and Multi-AZ ﬁle system deployments, see Availability and durability: Single-AZ and Multi-AZ ﬁle systems. Managing ﬁle systems You can administer your FSx for Windows File Server ﬁle systems using custom remote management PowerShell commands, or using the Windows-native GUI in some cases. To learn more about managing Amazon FSx ﬁle systems, see Administering FSx for Windows ﬁle systems. Price and performance ﬂexibility FSx for Windows File Server gives you the price and performance ﬂexibility by oﬀering both solid state drive (SSD) and hard disk drive (HDD) storage types. HDD storage is designed for a broad spectrum of workloads, including home directories, user and departmental shares, and content management systems. SSD storage is designed for the highest-performance and most latency-sensitive workloads, including databases, media processing workloads, and data analytics applications. With FSx for Windows File Server, you can provision ﬁle system storage, SSD IOPS, and throughput independently to achieve the right mix of cost and performance. You can modify your ﬁle system's storage, SSD IOPS, and throughput capacities to meet changing workload needs, so that you pay only for
WindowsGuide-006	WindowsGuide.pdf	6	state drive (SSD) and hard disk drive (HDD) storage types. HDD storage is designed for a broad spectrum of workloads, including home directories, user and departmental shares, and content management systems. SSD storage is designed for the highest-performance and most latency-sensitive workloads, including databases, media processing workloads, and data analytics applications. With FSx for Windows File Server, you can provision ﬁle system storage, SSD IOPS, and throughput independently to achieve the right mix of cost and performance. You can modify your ﬁle system's storage, SSD IOPS, and throughput capacities to meet changing workload needs, so that you pay only for what you need. Availability and durability 3 Amazon FSx for Windows File Server Windows User Guide Pricing for Amazon FSx With Amazon FSx, there are no upfront hardware or software costs. You pay for only the resources used, with no minimum commitments, setup costs, or additional fees. For information about the pricing and fees associated with the service, see Amazon FSx for Windows File Server Pricing. Assumptions To use Amazon FSx, you need an AWS account with an Amazon EC2 instance, WorkSpaces instance, AppStream 2.0 instance, or VM running in VMware Cloud on AWS environments of the supported type. In this guide, we make the following assumptions: • If you're using Amazon EC2, we assume that you're familiar with Amazon EC2. For more information on how to use Amazon EC2, see Amazon Elastic Compute Cloud documentation. • If you're using WorkSpaces, we assume that you're familiar with WorkSpaces. For more information on how to use WorkSpaces, see Amazon WorkSpaces User Guide. • If you're using VMware Cloud on AWS, we assume that you're familiar with it. For more information, see VMware Cloud on AWS. • We assume that you are familiar with Microsoft Active Directory concepts. Prerequisites To create an Amazon FSx ﬁle system, you need the following: • An AWS account with the permissions necessary to create an Amazon FSx ﬁle system and an Amazon EC2 instance. For more information, see Setting up your AWS account. • An Amazon EC2 instance running Microsoft Windows Server in the virtual private cloud (VPC) based on the Amazon VPC service that you want to associate with your Amazon FSx ﬁle system. For information on how to create one, see Getting Started with Amazon EC2 Windows Instances in the Amazon EC2 User Guide. • Amazon FSx works with Microsoft Active Directory to perform user authentication and access control. You join your Amazon FSx ﬁle system to a Microsoft Active Directory while creating it. For more information, see Working with Microsoft Active Directory. Pricing for Amazon FSx 4 Amazon FSx for Windows File Server Windows User Guide • This guide assumes that you haven't changed the rules on the default security group for your VPC based on the Amazon VPC service. If you have, you need to ensure that you add the necessary rules to allow network traﬃc from your Amazon EC2 instance to your Amazon FSx ﬁle system. For more details, see Security in Amazon FSx. • Install and conﬁgure the AWS Command Line Interface (AWS CLI). Supported versions are 1.9.12 and newer. For more information, see Installing, updating, and uninstalling the AWS CLI in the AWS Command Line Interface User Guide. Note You can check the version of the AWS CLI you're using with the aws --version command. Amazon FSx for Windows File Server forums If you encounter issues while using Amazon FSx, use the forums. Are you a ﬁrst-time user of Amazon FSx? If you are a ﬁrst-time user of Amazon FSx, we recommend that you read the following sections in order: 1. If you're ready to create your ﬁrst Amazon FSx ﬁle system, try the Getting started with Amazon FSx for Windows File Server. 2. For information about performance, see FSx for Windows File Server performance. 3. For Amazon FSx security details, see Security in Amazon FSx. 4. For information about the Amazon FSx API, see Amazon FSx API Reference. Amazon FSx for Windows File Server forums 5 Amazon FSx for Windows File Server Windows User Guide Best practices for FSx for Windows File Server We recommend that you follow these best practices when working with Amazon FSx for Windows File Server. Topics • General best practices • Security best practices • Active Directory • Conﬁguring and right-sizing your ﬁle system General best practices Creating a monitoring plan You can use ﬁle system metrics to monitor your storage and performance usage, understand your usage patterns, and trigger notiﬁcations when your usage approaches your ﬁle system’s storage or performance limits. Monitoring your Amazon FSx ﬁle systems along with the rest of your application environment enables you to quickly debug any issues that may impact performance. Ensuring that your ﬁle systems have suﬃcient resources Having insuﬃcient resources can result in increased latency
WindowsGuide-007	WindowsGuide.pdf	7	File Server. Topics • General best practices • Security best practices • Active Directory • Conﬁguring and right-sizing your ﬁle system General best practices Creating a monitoring plan You can use ﬁle system metrics to monitor your storage and performance usage, understand your usage patterns, and trigger notiﬁcations when your usage approaches your ﬁle system’s storage or performance limits. Monitoring your Amazon FSx ﬁle systems along with the rest of your application environment enables you to quickly debug any issues that may impact performance. Ensuring that your ﬁle systems have suﬃcient resources Having insuﬃcient resources can result in increased latency and queuing for I/O requests, which might appear as complete or partial unavailability of your ﬁle system. For more information about monitoring performance and accessing performance warnings and recommendations, see Performance warnings and recommendations. Security best practices We recommend that you follow these best practices for administering your ﬁle system’s security and access controls. For more detailed information on conﬁguring Amazon FSx to meet your security and compliance objectives, see Security in Amazon FSx. General best practices 6 Amazon FSx for Windows File Server Network security Windows User Guide Don't modify or delete the ENI that's associated with your ﬁle system Your Amazon FSx ﬁle system is accessed through an elastic network interface (ENI) that resides in the virtual private cloud (VPC) that's associated with your ﬁle system. Modifying or deleting the network interface can cause a permanent loss of connection between your VPC and your ﬁle system. Using security groups and network ACLs You can use security groups and network access control lists (ACLs) to limit access to your ﬁle systems. For VPC security groups, the default security group is already added to your ﬁle system in the console. Make sure that the security group and the network ACLs for the subnets where you create your ﬁle system allow traﬃc on the ports. Active Directory When you create an Amazon FSx ﬁle system, you can join it to your Microsoft Active Directory domain to provide user authentication, and share-, ﬁle-, and folder-level access control authorization. Your users can use their existing Active Directory accounts to connect to ﬁle shares and access ﬁles and folders within them. In addition, you can migrate the existing security ACL conﬁguration to Amazon FSx without any modiﬁcations. Amazon FSx provides you with two options for Active Directory: AWS managed Microsoft Active Directory or self-managed Microsoft Active Directory. If you’re using an AWS managed Microsoft Active Directory, we recommend leaving the default settings of your Active Directory security group. If you do modify these settings, ensure that you maintain a network conﬁguration that satisﬁes the network requirements. For more information, see Networking prerequisites. If you’re using a self-managed Microsoft Active Directory, you have additional options for conﬁguring your ﬁle system. We recommend the following best practices for initial conﬁguration when using Amazon FSx with your self-managed Microsoft Active Directory: • Assign subnets to a single Active Directory site: If your Active Directory environment has a large number of domain controllers, use Active Directory Sites and Services to assign the subnets used by your Amazon FSx ﬁle systems to a single Active Directory site with the highest availability and reliability. Make sure that the VPC security group, VPC network ACL, Windows Network security 7 Amazon FSx for Windows File Server Windows User Guide ﬁrewall rules on your DCs, and any other network routing controls you have in your Active Directory infrastructure allow communication from Amazon FSx on the required ports. This allows Windows to revert to other DCs if it can't use the assigned Active Directory site. For more information, see File system access control with Amazon VPC. • Use a separate Organizational Unit (OU): Use an OU for your Amazon FSx ﬁle systems that’s separate from any other organizational units that you might have. • Conﬁgure your service account with minimum privileges required: Conﬁgure or delegate the service account that you provide to Amazon FSx with the minimum privileges required. For more information, see Using a self-managed Microsoft Active Directory. • Continuously verify your Active Directory conﬁguration: Run the Amazon FSx Active Directory validation tool against your Active Directory conﬁguration prior to creating your Amazon FSx ﬁle system to verify that your conﬁguration is valid for use with Amazon FSx, and to discover any warnings and errors that the tool might expose. Avoid losing availability due to Active Directory misconﬁguration When using Amazon FSx with your self-managed Microsoft Active Directory, it's important to have a valid Active Directory conﬁguration not only during the creation of your ﬁle system, but also for ongoing operations and availability. During failure recovery events, routine maintenance events, and throughput capacity update actions, Amazon FSx rejoins ﬁle server resources to your Active Directory. If the Active Directory conﬁguration is not valid
WindowsGuide-008	WindowsGuide.pdf	8	FSx ﬁle system to verify that your conﬁguration is valid for use with Amazon FSx, and to discover any warnings and errors that the tool might expose. Avoid losing availability due to Active Directory misconﬁguration When using Amazon FSx with your self-managed Microsoft Active Directory, it's important to have a valid Active Directory conﬁguration not only during the creation of your ﬁle system, but also for ongoing operations and availability. During failure recovery events, routine maintenance events, and throughput capacity update actions, Amazon FSx rejoins ﬁle server resources to your Active Directory. If the Active Directory conﬁguration is not valid during an event, your ﬁle system changes to a status of Misconﬁgured, and is at risk of becoming unavailable. Here are some ways that you can avoid losing availability: • Keep your Active Directory conﬁguration updated with Amazon FSx: If you make changes, such as resetting the password of your service account, make sure you update the conﬁguration for any ﬁle systems using this service account. • Monitor for Active Directory misconﬁguration: Set Misconﬁgured status notiﬁcations for yourself so that you can reset your ﬁle system’s Active Directory conﬁguration, if necessary. For an example that uses a Lambda-based solution to achieve this, see Monitoring the health of Amazon FSx ﬁle systems using Amazon EventBridge and AWS Lambda. • Validate your Active Directory conﬁguration regularly: If you want to proactively detect an Active Directory misconﬁguration, we recommend that you run the Active Directory Validation tool against your Active Directory conﬁguration on an ongoing basis. If you receive warnings or errors when running the validation tool, it means that your ﬁle system is at risk of becoming misconﬁgured. Avoid losing availability due to Active Directory misconﬁguration 8 Amazon FSx for Windows File Server Windows User Guide • Don't move or modify computer objects created by FSx: Amazon FSx creates and manages computer objects in your Active Directory, using the service account and permissions that you provide. Moving or modifying these computer objects can result in your ﬁle system becoming misconﬁgured. Windows ACLs With Amazon FSx, you use standard Windows access control lists (ACLs) for ﬁne-grained share-, ﬁle-, and folder-level access control. Amazon FSx ﬁle systems automatically verify the credentials of users who access ﬁle system data to enforce these Windows ACLs. • Don’t change the NTFS ACL permissions for the SYSTEM user: Amazon FSx requires that the SYSTEM user have full control NTFS ACL permissions on all folders within your ﬁle system. Changing the NTFS ACL permissions for the SYSTEM user may result in your ﬁle system becoming inaccessible and future ﬁle system backups may become unusable. Conﬁguring and right-sizing your ﬁle system Selecting a deployment type Amazon FSx provides two deployment options: Single-AZ and Multi-AZ. We recommend using Multi-AZ ﬁle systems for most production workloads that require high availability to shared Windows ﬁle data. For more information, see Availability and durability: Single-AZ and Multi-AZ ﬁle systems. Selecting a throughput capacity Conﬁgure your ﬁle system with suﬃcient throughput capacity to meet not only the expected traﬃc of your workload, but also additional performance resources required to support the features you want to enable on your ﬁle system. For example, if you’re running data deduplication, the throughput capacity that you select must provide enough memory to run deduplication based on the storage that you have. If you’re using shadow copies, increase throughput capacity to a value that's at least three times the value that's expected to be driven by your workload to avoid Windows Server deleting your shadow copies. For more information, see Impact of throughput capacity on performance. Windows ACLs 9 Amazon FSx for Windows File Server Windows User Guide Increasing storage capacity and throughput capacity Increase the storage capacity of your ﬁle system when it’s running low on free storage, or when you expect your storage requirements to grow larger than the current storage limit. We recommend maintaining at least 20% of free storage capacity at all times on your ﬁle system. We also recommend increasing throughput capacity by at least 20% before increasing storage capacity to oﬀset any performance impact during a storage increase. You can use the FreeStorageCapacity CloudWatch metric to monitor the amount of free storage available and understand how it trends. For more information, see Managing storage capacity. You should also increase the throughput capacity of your ﬁle system if your workload is constrained by the current performance limits. You can use the Monitoring and performance page on the FSx console to see when workload demands have approached or exceeded performance limits to determine whether your ﬁle system is under-provisioned for your workload. To minimize the duration of storage scaling and avoid reduction in write performance, we recommend increasing your ﬁle system's throughput capacity before increasing storage capacity and then scaling back throughput capacity after the storage
WindowsGuide-009	WindowsGuide.pdf	9	understand how it trends. For more information, see Managing storage capacity. You should also increase the throughput capacity of your ﬁle system if your workload is constrained by the current performance limits. You can use the Monitoring and performance page on the FSx console to see when workload demands have approached or exceeded performance limits to determine whether your ﬁle system is under-provisioned for your workload. To minimize the duration of storage scaling and avoid reduction in write performance, we recommend increasing your ﬁle system's throughput capacity before increasing storage capacity and then scaling back throughput capacity after the storage capacity increase is complete. Most workloads experience minimal performance impact during storage scaling. However, ﬁle systems with HDD storage type and workloads involving large numbers of end users, high levels of I/ O, or datasets with large numbers of small ﬁles could temporarily experience a reduction in performance. For more information, see Storage capacity increases and ﬁle system performance. Modifying throughput capacity during idle periods Updating throughput capacity interrupts availability for a few minutes for Single-AZ ﬁle systems and causes failover and failback for Multi-AZ ﬁle systems. For Multi-AZ ﬁle systems, if there is ongoing traﬃc during failover and failback, any data changes made during this time will need to be synchronized between the ﬁle servers. The data synchronization process can take up to multiple hours for write-heavy and IOPS-heavy workloads. Although your ﬁle system will continue to be available during this time, we recommend scheduling maintenance windows and performing throughput capacity updates during idle periods when there is minimal load on your ﬁle system to reduce the duration of data synchronization. To learn more, see Managing throughput capacity. Increasing storage capacity and throughput capacity 10 Amazon FSx for Windows File Server Windows User Guide Getting started with Amazon FSx for Windows File Server Following, you can learn how to get started using FSx for Windows File Server. This getting started exercise includes the following steps. 1. Sign up for an AWS account and create an administrative user in the account. 2. Create an AWS Managed Microsoft AD Active Directory using the AWS Directory Service. You will join your ﬁle system and compute instance to the Active Directory. 3. Create an Amazon Elastic Compute Cloud compute instance running Microsoft Windows Server. You will use this instance to access your ﬁle system. 4. Create an Amazon FSx for Windows File Server ﬁle system using the Amazon FSx console. 5. Map your ﬁle system to your EC2 instance 6. Write data to your ﬁle system. 7. Back up your ﬁle system. 8. Clean up the resources you created. Topics • Setting up your AWS account • Step 1. Setting up an Active Directory • Step 2: Launch a Windows instance in the Amazon EC2 console • Step 3: Connect to your instance • Step 4: Join your instance to your AWS Directory Service directory • Step 5. Create your ﬁle system • Step 6. Map your ﬁle share to an EC2 instance running Windows Server • Step 7. Write data to your ﬁle share • Step 8. Back up your ﬁle system • Step 9. Clean up resources Setting up your AWS account Before you use Amazon FSx for the ﬁrst time, complete the following tasks: Setting up your AWS account 11 Amazon FSx for Windows File Server 1. Sign up for an AWS account 2. Create a user with administrative access Sign up for an AWS account Windows User Guide If you do not have an AWS account, complete the following steps to create one. To sign up for an AWS account 1. Open https://portal.aws.amazon.com/billing/signup. 2. Follow the online instructions. Part of the sign-up procedure involves receiving a phone call and entering a veriﬁcation code on the phone keypad. When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access. AWS sends you a conﬁrmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account. Create a user with administrative access After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks. Secure your AWS account root user 1. Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. For help signing in by using root
WindowsGuide-010	WindowsGuide.pdf	10	your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account. Create a user with administrative access After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks. Secure your AWS account root user 1. Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide. 2. Turn on multi-factor authentication (MFA) for your root user. 12 Amazon FSx for Windows File Server Windows User Guide For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide. Create a user with administrative access 1. Enable IAM Identity Center. For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide. 2. In IAM Identity Center, grant administrative access to a user. For a tutorial about using the IAM Identity Center directory as your identity source, see Conﬁgure user access with the default IAM Identity Center directory in the AWS IAM Identity Center User Guide. Sign in as the user with administrative access • To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user. For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide. Assign access to additional users 1. In IAM Identity Center, create a permission set that follows the best practice of applying least- privilege permissions. For instructions, see Create a permission set in the AWS IAM Identity Center User Guide. 2. Assign users to a group, and then assign single sign-on access to the group. For instructions, see Add groups in the AWS IAM Identity Center User Guide. Step 1. Setting up an Active Directory With Amazon FSx, you can operate fully managed ﬁle storage for Windows-based workloads. Likewise, AWS Directory Service provides fully managed directories to use in your workload Step 1. Setting up an Active Directory 13 Amazon FSx for Windows File Server Windows User Guide deployment. If you have an existing corporate Active Directory domain running in AWS in a virtual private cloud (VPC) using EC2 instances, you can enable user-based authentication and access control. You do this by establishing a trust relationship between your AWS Managed Microsoft Active Directory and your corporate domain. For Windows authentication in Amazon FSx, you only need a one-way directional forest trust, where the AWS managed forest trusts the corporate domain forest. Your corporate domain takes the role of the trusted domain, and the AWS Directory Service managed domain takes the role of the trusting domain. Validated authentication requests travel between the domains in only one direction—allowing accounts in your corporate domain to authenticate against resources shared in the managed domain. In this case, Amazon FSx interacts only with the managed domain. The managed domain then passes on the authentication requests to your corporate domain. Note You can also use an external trust type with Amazon FSx for trusted domains. Your Active Directory security group must enable inbound access from the Amazon FSx ﬁle system’s security group. To create an AWS Directory Services for Microsoft Active Directory • If you don't already have one, use the AWS Directory Service to create your AWS Managed Microsoft Active Directory directory. For more information, see Create Your AWS Managed Microsoft Active Directory in the AWS Directory Service Administration Guide. Important Remember the password you assign to your Admin user; you need it later in this getting started exercise. If you forget the password, you need to repeat steps in this exercise with the new AWS Directory Service directory and Admin user. • If you have an existing Active Directory, create a trust relationship between your AWS Managed Microsoft Active Directory and your existing Active Directory. For more information, see When to Create a Trust Relationship in the AWS Directory Service Administration Guide. Step 1. Setting up an Active Directory 14 Amazon FSx for Windows File Server Windows User Guide Step 2: Launch a Windows instance in the Amazon EC2 console You can launch a Windows instance using the AWS Management Console as described in the following procedure. This is intended to help you launch your ﬁrst instance quickly, so it doesn't cover all possible options. For more information about the advanced options, see Launching an Instance. To launch an instance 1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/. 2.
WindowsGuide-011	WindowsGuide.pdf	11	When to Create a Trust Relationship in the AWS Directory Service Administration Guide. Step 1. Setting up an Active Directory 14 Amazon FSx for Windows File Server Windows User Guide Step 2: Launch a Windows instance in the Amazon EC2 console You can launch a Windows instance using the AWS Management Console as described in the following procedure. This is intended to help you launch your ﬁrst instance quickly, so it doesn't cover all possible options. For more information about the advanced options, see Launching an Instance. To launch an instance 1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/. 2. 3. From the console dashboard, choose Launch Instance. The Choose an Amazon Machine Image (AMI) page displays a list of basic conﬁgurations, called Amazon Machine Images (AMIs), that serve as templates for your instance. Select the AMI for Windows Server 2016 Base or later. Notice that these AMIs are marked "Free tier eligible." 4. On the Choose an Instance Type page, you can select the hardware conﬁguration of your instance. Select the t2.micro type, which is selected by default. Notice that this instance type is eligible for the free tier. 5. Choose Review and Launch to let the wizard complete the other conﬁguration settings for you. 6. On the Review Instance Launch page, under Security Groups, a security group appears that the wizard created and selected for you. You can use this security group, or you can choose the security group that you created when getting set up using the following steps: a. Choose Edit security groups. b. On the Conﬁgure Security Group page, ensure that Select an existing security group is selected. c. Select your security group from the list of existing security groups, and then choose Review and Launch. 7. On the Review Instance Launch page, choose Launch. 8. When prompted for a key pair, select Choose an existing key pair, then select the key pair that you created when getting set up. Alternatively, you can create a new key pair. Select Create a new key pair, enter a name for the key pair, and then choose Download Key Pair. This is the only chance for you to save the private key ﬁle, so be sure to download it. Save the private key ﬁle in a safe place. You'll need Step 2: Launch a Windows instance in the Amazon EC2 console 15 Amazon FSx for Windows File Server Windows User Guide to provide the name of your key pair when you launch an instance and the corresponding private key each time you connect to the instance. Warning Don't select the Proceed without a key pair option. If you launch your instance without a key pair, then you can't connect to it. When you are ready, select the acknowledgement check box, and then choose Launch Instances. 9. A conﬁrmation page lets you know that your instance is launching. Choose View Instances to close the conﬁrmation page and return to the console. 10. On the Instances screen, you can view the status of the launch. It takes a short time for an instance to launch. When you launch an instance, its initial state is pending. After the instance starts, its state changes to running and it receives a public DNS name. (If the Public DNS (IPv4) column is hidden, choose Show/Hide Columns (the gear-shaped icon) in the top right corner of the page and then select Public DNS (IPv4).) 11. It can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks; you can view this information in the Status Checks column. Important Make a note of the ID of the security group that was created when you launched this instance. You'll need it when you create your Amazon FSx ﬁle system. Now that your instance is launched, you can connect to your instance. Step 3: Connect to your instance To connect to a Windows instance, you must retrieve the initial administrator password and then specify this password when you connect to your instance using Remote Desktop. The name of the administrator account depends on the language of the operating system. For example, for English it's Administrator, for French it's Administrateur, and for Portuguese it's Step 3: Connect to your instance 16 Amazon FSx for Windows File Server Windows User Guide Administrador. For more information, see Localized Names for Administrator Account in Windows in the Microsoft TechNet Wiki. If you joined your instance to a domain, you can connect to your instance using domain credentials you deﬁned in AWS Directory Service. On the Remote Desktop login screen, don't use the local computer name and the generated password. Instead, use the fully qualiﬁed user name for the administrator and the password for this account. An
WindowsGuide-012	WindowsGuide.pdf	12	English it's Administrator, for French it's Administrateur, and for Portuguese it's Step 3: Connect to your instance 16 Amazon FSx for Windows File Server Windows User Guide Administrador. For more information, see Localized Names for Administrator Account in Windows in the Microsoft TechNet Wiki. If you joined your instance to a domain, you can connect to your instance using domain credentials you deﬁned in AWS Directory Service. On the Remote Desktop login screen, don't use the local computer name and the generated password. Instead, use the fully qualiﬁed user name for the administrator and the password for this account. An example is corp.example.com\Admin. The license for the Windows Server operating system (OS) allows two simultaneous remote connections for administrative purposes. The license for Windows Server is included in the price of your Windows instance. If you need more than two simultaneous remote connections, you must purchase a Remote Desktop Services (RDS) license. If you attempt a third connection, an error occurs. For more information, see Conﬁgure the Number of Simultaneous Remote Connections Allowed for a Connection. To connect to your Windows instance using an RDP client 1. 2. In the Amazon EC2 console, select the instance, and then choose Connect. In the Connect to Your Instance dialog box, choose Get Password (it takes a few minutes after the instance is launched before the password is available). 3. Choose Browse and navigate to the private key ﬁle you created when you launched the instance. Select the ﬁle and choose Open to copy the entire contents of the ﬁle into the Contents ﬁeld. 4. Choose Decrypt Password. The console displays the default administrator password for the instance in the Connect to Your Instance dialog box, replacing the link to Get Password shown previously with the actual password. 5. Record the default administrator password, or copy it to the clipboard. You need this password to connect to the instance. 6. Choose Download Remote Desktop File. Your browser prompts you to either open or save the .rdp ﬁle. Either option is ﬁne. When you have ﬁnished, you can choose Close to dismiss the Connect to Your Instance dialog box. • If you opened the .rdp ﬁle, you see the Remote Desktop Connection dialog box. • If you saved the .rdp ﬁle, navigate to your downloads directory, and open the .rdp ﬁle to display the dialog box. 7. You may get a warning that the publisher of the remote connection is unknown. You can continue to connect to your instance. Step 3: Connect to your instance 17 Amazon FSx for Windows File Server Windows User Guide 8. When prompted, log in to the instance, using the administrator account for the operating system and the password that you recorded or copied previously. If your Remote Desktop Connection already has an administrator account set up, you might have to choose the Use another account option and type the user name and password manually. Note Sometimes copying and pasting content can corrupt data. If you encounter a "Password Failed" error when you log in, try typing in the password manually. 9. Due to the nature of self-signed certiﬁcates, you may get a warning that the security certiﬁcate could not be authenticated. Use the following steps to verify the identity of the remote computer, or simply choose Yes or Continue to continue if you trust the certiﬁcate. a. If you are using Remote Desktop Connection from a Windows PC, choose View certiﬁcate. If you are using Microsoft Remote Desktop on a Mac, choose Show Certiﬁcate. b. Choose the Details tab, and scroll down to the Thumbprint entry on a Windows PC, or the SHA1 Fingerprints entry on a Mac. This is the unique identiﬁer for the remote computer's security certiﬁcate. c. d. e. f. In the Amazon EC2 console, select the instance, choose Actions, and then choose Get System Log. In the system log output, look for an entry labeled RDPCERTIFICATE-THUMBPRINT. If this value matches the thumbprint or ﬁngerprint of the certiﬁcate, you have veriﬁed the identity of the remote computer. If you are using Remote Desktop Connection from a Windows PC, return to the Certiﬁcate dialog box and choose OK. If you are using Microsoft Remote Desktop on a Mac, return to the Verify Certiﬁcate and choose Continue. [Windows] Choose Yes in the Remote Desktop Connection window to connect to your instance. Now that you're connected to your instance, you can join the instance to your AWS Directory Service directory. Step 3: Connect to your instance 18 Amazon FSx for Windows File Server Windows User Guide Step 4: Join your instance to your AWS Directory Service directory The following procedure shows you how to manually join an existing Amazon EC2 Windows instance to your AWS Directory Service directory. To join a Windows instance to your AWS Directory Service
WindowsGuide-013	WindowsGuide.pdf	13	a Mac, return to the Verify Certiﬁcate and choose Continue. [Windows] Choose Yes in the Remote Desktop Connection window to connect to your instance. Now that you're connected to your instance, you can join the instance to your AWS Directory Service directory. Step 3: Connect to your instance 18 Amazon FSx for Windows File Server Windows User Guide Step 4: Join your instance to your AWS Directory Service directory The following procedure shows you how to manually join an existing Amazon EC2 Windows instance to your AWS Directory Service directory. To join a Windows instance to your AWS Directory Service directory 1. Connect to the instance using any Remote Desktop Protocol client. 2. Open the TCP/IPv4 properties dialog box on the instance. a. Open Network Connections. Tip You can open Network Connections directly by running the following from a command prompt on the instance. %SystemRoot%\system32\control.exe ncpa.cpl b. Open the context (right-click) menu for any enabled network connection and then choose Properties. c. In the connection properties dialog box, open (double-click) Internet Protocol Version 4. 3. (Optional) Select Use the following DNS server addresses, change the Preferred DNS server and Alternate DNS server addresses to the IP addresses of the AWS Directory Service– provided DNS servers, and choose OK. 4. Open the System Properties dialog box for the instance, choose the Computer Name tab, and choose Change. Tip You can open the System Properties dialog box directly by running the following from a command prompt on the instance. %SystemRoot%\system32\control.exe sysdm.cpl Step 4: Join your instance to your AWS Directory Service directory 19 Amazon FSx for Windows File Server Windows User Guide 5. In the Member of box, choose Domain, enter the fully qualiﬁed name of your AWS Directory Service directory, and choose OK. 6. When prompted for the name and password for the domain administrator, enter the user name and password of the Admin account. Note You can enter either the fully qualiﬁed name of your domain or the NetBios name, followed by a backslash (\), and then the user name, in this case, Admin. For example, corp.example.com\Admin or corp\Admin. 7. After you receive the message welcoming you to the domain, restart the instance to have the changes take eﬀect. 8. Reconnect to your instance over RDP, and sign into the instance using the user name and password for your AWS Directory Service directory's Admin user. Now that your instance has been joined to the domain, you're ready to create your Amazon FSx ﬁle system. Step 5. Create your ﬁle system To create your ﬁle system (console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. On the dashboard, choose Create ﬁle system to start the ﬁle system creation wizard. 3. On the Select ﬁle system type page, choose FSx for Windows File Server, and then choose Next. The Create ﬁle system page appears. 4. For Creation method choose Standard create. File system details 1. In the File system details section, provide a name for your ﬁle system. It's easier to ﬁnd and manage your ﬁle systems when you name them. You can use a maximum of 256 Unicode letters, white space, and numbers, plus the special characters + - = . _ : / 2. For Deployment type choose Multi-AZ or Single-AZ. Step 5. Create your ﬁle system 20 Amazon FSx for Windows File Server Windows User Guide • Choose Multi-AZ to deploy a ﬁle system that is tolerant to Availability Zone unavailability. This option supports SSD and HDD storage. • Choose Single-AZ to deploy a ﬁle system that is deployed in a single Availability Zone. Single-AZ 2 is the latest generation of single Availability Zone ﬁle systems, and it supports SSD and HDD storage. For more information, see Availability and durability: Single-AZ and Multi-AZ ﬁle systems. 3. For Storage type, you can choose either SSD or HDD. FSx for Windows File Server oﬀers solid state drive (SSD) and hard disk drive (HDD) storage types. SSD storage is designed for the highest-performance and most latency-sensitive workloads, including databases, media processing workloads, and data analytics applications. HDD storage is designed for a broad spectrum of workloads, including home directories, user and departmental ﬁle shares, and content management systems. For more information, see About storage types. 4. For Provisioned SSD IOPS, you can choose either Automatic or User-provisioned mode. If you choose Automatic mode, FSx for Windows File Server automatically scales your SSD IOPS to maintain 3 SSD IOPS per GiB of storage capacity. If you choose User-provisioned mode, enter any whole number in the range of 96–400,000. Scaling SSD IOPS above 80,000 is available in US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Singapore). For more information, see Managing SSD IOPS. 5. For Storage capacity, enter the storage capacity of your
WindowsGuide-014	WindowsGuide.pdf	14	see About storage types. 4. For Provisioned SSD IOPS, you can choose either Automatic or User-provisioned mode. If you choose Automatic mode, FSx for Windows File Server automatically scales your SSD IOPS to maintain 3 SSD IOPS per GiB of storage capacity. If you choose User-provisioned mode, enter any whole number in the range of 96–400,000. Scaling SSD IOPS above 80,000 is available in US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Singapore). For more information, see Managing SSD IOPS. 5. For Storage capacity, enter the storage capacity of your ﬁle system, in GiB. If you're using SSD storage, enter any whole number in the range of 32–65,536. If you're using HDD storage, enter any whole number in the range of 2,000–65,536. You can increase the amount of storage capacity as needed at any time after you create the ﬁle system. For more information, see Managing storage capacity. 6. Keep Throughput capacity at its default setting. Throughput capacity is the sustained speed at which the ﬁle server that hosts your ﬁle system can serve data. The Recommended throughput capacity setting is based on the amount of storage capacity you choose. If you need more than the recommended throughput capacity, choose Specify throughput capacity, and then choose a value. For more information, see FSx for Windows File Server performance. Step 5. Create your ﬁle system 21 Amazon FSx for Windows File Server Windows User Guide Note If you are going to enable ﬁle access auditing, you must choose a throughput capacity of 32 MBps or greater. For more information, see Logging end user access with ﬁle access auditing. You can modify the throughput capacity as needed at any time after you create the ﬁle system. For more information, see Managing throughput capacity. Network & security In the Network & security section, choose the Amazon VPC that you want to associate with your ﬁle system. For this getting started exercise, choose the same Amazon VPC that you chose for your AWS Directory Service directory and your Amazon EC2 instance. 1. 2. For VPC Security Groups, the default security group for your default Amazon VPC is already added to your ﬁle system in the console. If you're not using the default security group, make sure that the security group you choose is in the same AWS Region as your ﬁle system. To ensure that you can connect an EC2 instance with your ﬁle system, you will need to add the following rules to your chosen security group: a. Add the following inbound and outbound rules to allow the following ports. Rules UDP TCP Ports 53, 88, 123, 389, 464 53, 88, 135, 389, 445, 464, 636, 3268, 3269, 5985, 9389, 49152-65535 Add from and to IP addresses or security group IDs associated with the client compute instances that you want to access your ﬁle system from. b. Add outbound rules to allow all traﬃc to the Active Directory that you're joining your ﬁle system to. To do this, do one of the following: Step 5. Create your ﬁle system 22 Amazon FSx for Windows File Server Windows User Guide • Allow outbound traﬃc to the security group ID associated with your AWS Managed AD directory. • Allow outbound traﬃc to the IP addresses associated with your self-managed Active Directory domain controllers. Note In some cases, you might have modiﬁed the rules of your AWS Managed Microsoft AD security group from the default settings. If so, make sure that this security group has the required inbound rules to allow traﬃc from your Amazon FSx ﬁle system. For more information about the required inbound rules, see AWS Managed Microsoft AD Prerequisites in the AWS Directory Service Administration Guide. For more information, see File system access control with Amazon VPC. 3. Multi-AZ ﬁle systems have a primary and a standby ﬁle server, each in its own Availability Zone and subnet.If you are creating a Multi-AZ ﬁle system (see step 5), choose a Preferred subnet value for the primary ﬁle server and a Standby subnet value for the standby ﬁle server. If you are creating a Single-AZ ﬁle system, choose the Subnet for your ﬁle system. Windows authentication • For Windows authentication, you have the following options: Choose AWS Managed Microsoft Active Directory if you want to join your ﬁle system to a Microsoft Active Directory domain that is managed by AWS, and then choose your AWS Directory Service directory from the list. For more information, see Working with Microsoft Active Directory. Choose Self-managed Microsoft Active Directory if you want to join your ﬁle system to a self- managed Microsoft Active Directory domain, , and provide the following details for your Active Directory. For more information see Using a self-managed Microsoft Active Directory. • The fully qualiﬁed
WindowsGuide-015	WindowsGuide.pdf	15	authentication • For Windows authentication, you have the following options: Choose AWS Managed Microsoft Active Directory if you want to join your ﬁle system to a Microsoft Active Directory domain that is managed by AWS, and then choose your AWS Directory Service directory from the list. For more information, see Working with Microsoft Active Directory. Choose Self-managed Microsoft Active Directory if you want to join your ﬁle system to a self- managed Microsoft Active Directory domain, , and provide the following details for your Active Directory. For more information see Using a self-managed Microsoft Active Directory. • The fully qualiﬁed domain name of your Active Directory. Step 5. Create your ﬁle system 23 Amazon FSx for Windows File Server Windows User Guide Important For Single-AZ 2 and all Multi-AZ ﬁle systems, the Active Directory domain name cannot exceed 47 characters. This limitation applies to both AWS Directory Service and self-managed Active Directory domain names. Amazon FSx requires a direct connection for internal traﬃc to your DNS IP address. Connection via an internet gateway is not supported. Instead, use AWS Virtual Private Network, VPC peering, AWS Direct Connect, or AWS Transit Gateway association. • DNS server IP addresses—the IPv4 addresses of the DNS servers for your domain Note Your DNS server must have EDNS (Extension Mechanisms for DNS) enabled. If EDNS is disabled, your ﬁle system might fail to create. • Service account username—the user name of the service account in your existing Active Directory. Do not include a domain preﬁx or suﬃx. • Service account password—the password for the service account. • (Optional) Organizational Unit (OU)—the distinguished path name of the organizational unit in which you want to join your ﬁle system. • (Optional) Delegated ﬁle system administrators group— the name of the group in your Active Directory that can administer your ﬁle system. The default group is 'Domain Admins'. For more information, see Amazon FSx service account. Encryption, Auditing, and Access (DNS aliases) 1. For Encryption, choose the AWS KMS key Encryption key used to encrypt the data on your ﬁle system at rest. You can choose the default aws/fsx (default) that is managed by AWS KMS, an existing key, or a customer managed key by specifying the ARN for the key. For more information, see Encryption of data at rest. 2. For Auditing - optional, ﬁle access auditing is disabled by default. For information about enabling and conﬁguring ﬁle access auditing, see Logging end user access with ﬁle access auditing. Step 5. Create your ﬁle system 24 Amazon FSx for Windows File Server Windows User Guide 3. For Access - optional, enter any DNS aliases that you want to associate with the ﬁle system. Each alias name must be formatted as a fully qualiﬁed domain name (FQDN). For more information, see Managing DNS aliases. Backup and maintenance For more information about automatic daily backups and the settings in this section, see Protecting your data with backups. 1. Daily automatic backup is enabled by default. You can disable this setting if you do not want Amazon FSx to take backups of your ﬁle system automatically on a daily basis. 2. 3. If automatic backups are enabled, they occur within a time period known as the backup window. You can use the default window, or choose an Automatic backup window start time that is best for your workﬂow. For Automatic backup retention period, you can use the default setting of 30 days, or set a value between 1 and 90 days that Amazon FSx will retain automatic daily backups of your ﬁle system for. This setting does not apply to user initiated backups, or backups taken by AWS Backup. 4. For Tags - optional, enter a key and value to add tags to your ﬁle system. A tag is a case- sensitive key-value pair that helps you manage, ﬁlter, and search for your ﬁle system. For more information, see Tagging your Amazon FSx resources. Choose Next. Review your conﬁguration and create 1. Review the ﬁle system conﬁguration shown on the Create ﬁle system page. For your reference, you can see which ﬁle system settings you can and can't modify after ﬁle system is created. Choose Create ﬁle system. 2. After Amazon FSx creates the ﬁle system, choose the ﬁle system ID from the list in the File Systems dashboard to view the details. Choose Attach, and note the DNS name for your ﬁle system the Network & security tab. You will need it in the following procedure to map a share to an EC2 instance. Step 5. Create your ﬁle system 25 Amazon FSx for Windows File Server Windows User Guide Step 6. Map your ﬁle share to an EC2 instance running Windows Server You can now mount your Amazon FSx ﬁle system to your Microsoft Windows–based Amazon EC2 instance
WindowsGuide-016	WindowsGuide.pdf	16	Amazon FSx creates the ﬁle system, choose the ﬁle system ID from the list in the File Systems dashboard to view the details. Choose Attach, and note the DNS name for your ﬁle system the Network & security tab. You will need it in the following procedure to map a share to an EC2 instance. Step 5. Create your ﬁle system 25 Amazon FSx for Windows File Server Windows User Guide Step 6. Map your ﬁle share to an EC2 instance running Windows Server You can now mount your Amazon FSx ﬁle system to your Microsoft Windows–based Amazon EC2 instance joined to your AWS Directory Service directory. The name of your ﬁle share is not the same as the name of your ﬁle system. To map a ﬁle share on an Amazon EC2 Windows instance using the GUI 1. Before you can mount a ﬁle share on a Windows instance, you must launch the EC2 instance and join it to the AWS Directory Service for Microsoft Active Directory that your ﬁle system has joined. To perform this action, choose one of the following procedures from the AWS Directory Service Administration Guide: • Seamlessly join a Windows EC2 instance • Manually join a Windows instance 2. Connect to your instance. For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. 3. When you're connected, open File Explorer. 4. From the navigation pane, open the context (right-click) menu for Network and choose Map Network Drive. 5. Choose a drive letter of your choice for Drive. 6. You can map your ﬁle system using either its default DNS name assigned by Amazon FSx, or using a DNS alias of your choosing. This procedure describes mapping a ﬁle share using the default DNS name. If you want to map a ﬁle share using a DNS alias, see Accessing data using DNS aliases. For Folder, enter the ﬁle system DNS name and the share name. The default Amazon FSx share is called \share. You can ﬁnd the DNS name in the Amazon FSx console, https:// console.aws.amazon.com/fsx/, Windows File Server > Network & Security section, or in the response of CreateFileSystem or DescribeFileSystems API command. • For a Single-AZ ﬁle system joined to an AWS Managed Microsoft Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com Step 6. Map your ﬁle share to an EC2 instance running Windows Server 26 Amazon FSx for Windows File Server Windows User Guide • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com For example, enter \\fs-0123456789abcdef0.ad-domain.com\share. 7. Choose whether the ﬁle share should Reconnect at sign-in, and then choose Finish. Step 7. Write data to your ﬁle share Now that you've mapped your ﬁle share to your instance, you can use your ﬁle share like any other directory in your Windows environment. To write data to your ﬁle share 1. Open the Notepad text editor. 2. Write some content in the text editor. For example: Hello, World! 3. Save the ﬁle to your ﬁle share's drive letter. 4. Using File Explorer, navigate to your ﬁle share and ﬁnd the text ﬁle that you just saved. Step 8. Back up your ﬁle system Now that you've had a chance to use your Amazon FSx ﬁle system and its ﬁle shares, you can back it up. By default, daily backups are created automatically during your ﬁle system's 30- minute backup window. However you can create a user-initiated backup at any time. Backups have additional costs associated with them. For more information on backup pricing, see Pricing. To create a backup of your ﬁle system from the console 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. 3. 4. From the console dashboard, choose the name of the ﬁle system you created for this exercise. From the Overview tab for your ﬁle system, choose Create backup. In the Create backup dialog box that opens, provide a name for your backup. This name can contain a maximum of 256 Unicode letters and include white space, numbers, and the following special characters: + - = . _ : / Step 7. Write data to your ﬁle share 27 Amazon FSx for Windows File Server 5. Choose Create backup. Windows User Guide 6. To view all your backups in a list, so you can restore your ﬁle system or delete the backup, choose Backups. When you create a new backup, its status is set to CREATING while it is being created. This can take a few minutes. When the backup is available for use, its status changes to AVAILABLE. Step 9. Clean up resources After you have ﬁnished this exercise, you should follow these steps to clean up your resources and protect your AWS
WindowsGuide-017	WindowsGuide.pdf	17	to your ﬁle share 27 Amazon FSx for Windows File Server 5. Choose Create backup. Windows User Guide 6. To view all your backups in a list, so you can restore your ﬁle system or delete the backup, choose Backups. When you create a new backup, its status is set to CREATING while it is being created. This can take a few minutes. When the backup is available for use, its status changes to AVAILABLE. Step 9. Clean up resources After you have ﬁnished this exercise, you should follow these steps to clean up your resources and protect your AWS account. To clean up resources 1. On the Amazon EC2 console, terminate your instance. For more information, see Terminate Your Instance in the Amazon EC2 User Guide. 2. On the Amazon FSx console, delete your ﬁle system. All automatic backups are deleted automatically. However, you still need to delete the manually created backups. The following steps outline this process: a. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. b. From the console dashboard, choose the name of the ﬁle system you created for this exercise. For Actions, choose Delete ﬁle system. In the Delete ﬁle system dialog box that opens, decide whether you want to create a ﬁnal backup. If you do, provide a name for the ﬁnal backup. Any automatically created backups are also deleted. Important New ﬁle systems can be created from backups. We recommend that you create a ﬁnal backup as a best practice. If you ﬁnd you don't need it after a certain period of time, you can delete this and other manually created backups. Enter the ID of the ﬁle system that you want to delete in the File system ID box. Choose Delete ﬁle system. c. d. e. f. Step 9. Clean up resources 28 Amazon FSx for Windows File Server Windows User Guide g. The ﬁle system is now being deleted, and its status in the dashboard changes to DELETING. When the ﬁle system has been deleted, it no longer appears in the dashboard. h. Now you can delete any manually created backups for your ﬁle system. From the left-side navigation, choose Backups. i. j. From the dashboard, choose any backups that have the same File system ID as the ﬁle system that you deleted, and choose Delete backup. The Delete backups dialog box opens. Leave the check box checked for the ID of the backup you selected, and choose Delete backups. Your Amazon FSx ﬁle system and related automatic backups are now deleted. 3. To delete the AWS Directory Service directory you created for this exercise, see Delete your directory in the AWS Directory Service Administration Guide. Step 9. Clean up resources 29 Amazon FSx for Windows File Server Windows User Guide Accessing your data You can access your Amazon FSx ﬁle systems using a variety of supported clients and methods from both the AWS Cloud and on-premises environments. Topics • Supported clients • Accessing data from within the AWS Cloud • Accessing data from on-premises • Accessing data using default DNS names • Support for Distributed File System (DFS) namespaces • Accessing data using DNS aliases • Accessing data using ﬁle shares • Creating, updating, removing ﬁle shares Supported clients FSx for Windows File Server supports the Server Message Block (SMB) protocol versions 2.0 through 3.1.1, giving you the ﬂexibility to connect to your ﬁle systems using a wide variety of compute instances and operating systems. The following AWS compute instances are supported for use with Amazon FSx: • Amazon Elastic Compute Cloud (Amazon EC2) instances, including Microsoft Windows, Mac, Amazon Linux and Amazon Linux 2 instances. For more information, see Mapping ﬁle shares. • Amazon Elastic Container Service (Amazon ECS) containers. For more information, see FSx for Windows File Server volumes in the Amazon Elastic Container Service Developer Guide. • WorkSpaces instances – To learn more, see the AWS blog post Using FSx for Windows File Server with Amazon WorkSpaces. • Amazon AppStream 2.0 instances – To learn more, see the AWS blog post Using Amazon FSx with Amazon AppStream 2.0. • VMs running in VMware Cloud on AWS environments – To learn more, see the AWS blog post Storing and Sharing Files with FSx for Windows File Server in a VMware Cloud on AWS Environment. Supported clients 30 Amazon FSx for Windows File Server Windows User Guide The following operating systems are supported for use with Amazon FSx: • Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022. • Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10 (including the Windows 7 and Windows 10 desktop experiences of WorkSpaces), and Windows 11. • Linux, using the cifs-utils tool. • macOS Accessing data from within
WindowsGuide-018	WindowsGuide.pdf	18	Sharing Files with FSx for Windows File Server in a VMware Cloud on AWS Environment. Supported clients 30 Amazon FSx for Windows File Server Windows User Guide The following operating systems are supported for use with Amazon FSx: • Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022. • Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10 (including the Windows 7 and Windows 10 desktop experiences of WorkSpaces), and Windows 11. • Linux, using the cifs-utils tool. • macOS Accessing data from within the AWS Cloud Each Amazon FSx ﬁle system is associated with a Virtual Private Cloud (VPC). You can access your FSx for Windows File Server ﬁle system from anywhere in the ﬁle system's VPC, regardless of Availability Zone. You can also access your ﬁle system from VPCs that are in diﬀerent AWS accounts or AWS Regions than the ﬁle system. In addition to the requirements described in the following sections for accessing FSx for Windows File Server resources, you also need to ensure that your ﬁle system's VPC security group is conﬁgured so that data and management traﬃc can ﬂow between your ﬁle system and clients. For more information about conﬁguring security groups with the required ports, see File system access control with Amazon VPC. You can access FSx for Windows File Server ﬁle system from supported clients that are in the same VPC as your ﬁle system. The following table illustrates the environments from which Amazon FSx supports access from clients in each of the supported environments, depending on when the ﬁle system was created. Clients located in... Access to ﬁle systems created before February 22, 2019 Access to ﬁle systems Access to ﬁle systems created created before after December December 17, 17, 2020 2020 Subnets in which the ﬁle system is created ✓ ✓ ✓ Accessing data from within the AWS Cloud 31 Amazon FSx for Windows File Server Windows User Guide Clients located in... Access to ﬁle systems created before February 22, 2019 Access to ﬁle systems Access to ﬁle systems created created before after December December 17, 17, 2020 2020 Primary CIDR blocks of the VPC in which the ﬁle system was created Secondary CIDRs of the VPC in which the ﬁle system was created Other CIDRs or peered networks Note ✓ ✓ ✓ Clients with IP addresses in an RFC 1918 private IP Clients with IP addresses address range: outside the following CIDR block range: 198.19.0.0/16 • 10.0.0.0/8 • 172.16.0.0/12 • 192.168.0 .0/16 In some cases, you might want to access a ﬁle system that was created before December 17, 2020 from on-premises using a non-private IP address range. To do this, create a new ﬁle system from a backup of the ﬁle system. For more information, see Protecting your data with backups. Accessing data from a diﬀerent VPC, AWS account, or AWS Region You can access your FSx for Windows File Server ﬁle system from support clients that are located in a diﬀerent VPC, AWS account, or AWS Region than what is associated with your ﬁle system using VPC peering or transit gateways. When you use a VPC peering connection or transit gateway to Accessing data from a diﬀerent VPC, AWS account, or AWS Region 32 Amazon FSx for Windows File Server Windows User Guide connect VPCs, compute instances that are in one VPC can access Amazon FSx ﬁle systems that are in another VPC. This access is possible even if the VPCs belong to diﬀerent AWS accounts, and even if the VPCs reside in diﬀerent AWS Regions. A VPC peering connection is a networking connection between two VPCs that you can use to route traﬃc between them using private IPv4 or IP version 6 (IPv6) addresses. You can use VPC peering to connect VPCs within the same AWS Region or between AWS Regions. For more information on VPC peering, see What is VPC Peering? in the Amazon VPC Peering Guide. A transit gateway is a network transit hub that you can use to interconnect your VPCs and on- premises networks. For more information about using VPC transit gateways, see Getting Started with Transit Gateways in the Amazon VPC Transit Gateways. After you set up a VPC peering or transit gateway connection, you can access your ﬁle system using its DNS name. You do so just as you do from compute instances within the associated VPC. Accessing data from on-premises FSx for Windows File Server supports the use of AWS Direct Connect or AWS VPN to access your ﬁle systems from your on-premises compute instances. With support for AWS Direct Connect, FSx for Windows File Server enables you to access your ﬁle system over a dedicated network connection from your on-premises environment. With support
WindowsGuide-019	WindowsGuide.pdf	19	Gateways in the Amazon VPC Transit Gateways. After you set up a VPC peering or transit gateway connection, you can access your ﬁle system using its DNS name. You do so just as you do from compute instances within the associated VPC. Accessing data from on-premises FSx for Windows File Server supports the use of AWS Direct Connect or AWS VPN to access your ﬁle systems from your on-premises compute instances. With support for AWS Direct Connect, FSx for Windows File Server enables you to access your ﬁle system over a dedicated network connection from your on-premises environment. With support for AWS VPN, FSx for Windows File Server enables you to access your ﬁle system from your on-premises devices over a secure and private tunnel. After you connect your on-premises environment to the VPC associated with your Amazon FSx ﬁle system, you can access your ﬁle system using its DNS name or a DNS alias. You do so just as you do from compute instances within the VPC. For more information on AWS Direct Connect, see the AWS Direct Connect User Guide. For more information on setting up AWS VPN connections, see VPN Connections in the Amazon VPC User Guide. Note In some cases, you might want to access a ﬁle system that was created before December 17, 2020 from on-premises using a non-private IP address range. To do this, create a new ﬁle system from a backup of the ﬁle system. For more information, see Protecting your data with backups. Accessing data from on-premises 33 Amazon FSx for Windows File Server Windows User Guide FSx for Windows File Server also supports the use of Amazon FSx File Gateway to provide low latency, seamless access to your in-cloud FSx for Windows File Server ﬁle shares from your on- premises compute instances. For more information, see the Amazon FSx File Gateway User Guide. Note Amazon FSx File Gateway is no longer available to new customers. Existing customers of FSx File Gateway can continue to use the service normally. For capabilities similar to FSx File Gateway, visit this blog post. Accessing data using default DNS names FSx for Windows File Server provides a Domain Name System (DNS) name for every ﬁle system. You access your FSx for Windows File Server ﬁle system by mapping a drive letter on your compute instance to your Amazon FSx ﬁle share using this DNS name. To learn more, see Accessing data using ﬁle shares. Important Amazon FSx only registers DNS records for a ﬁle system if you are using Microsoft DNS as the default DNS. If you are using a third-party DNS, you must manually set up DNS entries for your Amazon FSx ﬁle systems. For information about choosing the correct IP addresses to use for the ﬁle system, see Getting the correct ﬁle system IP addresses to use for manual DNS entries. To ﬁnd the DNS name: • In the Amazon FSx console, choose File systems, and then choose Details. View the DNS name in the Network & Security section. • Or, view it in the response of the CreateFileSystem or DescribeFileSystems API command. For all Single-AZ ﬁle systems joined to an AWS Managed Microsoft Active Directory, the DNS name has the following format: fs-0123456789abcdef0.ad-dns-domain-name For all Single-AZ ﬁle systems joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name has the following format: amznfsxaa11bb22.ad-domain.com Accessing data using default DNS names 34 Amazon FSx for Windows File Server Windows User Guide Using Kerberos authentication with DNS names We recommend that you use Kerberos-based authentication and encryption in transit with Amazon FSx. Kerberos provides the most secure authentication for clients accessing your ﬁle system. To enable Kerberos-based authentication and encryption of data in transit for your SMB sessions, use the ﬁle system's DNS name provided by Amazon FSx to access your ﬁle system. If you have an external trust conﬁgured between your AWS Managed Microsoft Active Directory and your on-premises Active Directory, to use the Amazon FSx Remote PowerShell with Kerberos authentication, you must conﬁgure a local group policy on the client for forest search order. For more information, see Conﬁgure Kerberos Forest Search Order (KFSO) in the Microsoft documentation. Support for Distributed File System (DFS) namespaces FSx for Windows File Server supports the use of Microsoft DFS Namespaces. Use DFS Namespaces to organize ﬁle shares that are located on multiple ﬁle systems into one common folder structure (a namespace) that you use to access the entire ﬁle dataset. You can use a name in your DFS Namespace to access your Amazon FSx ﬁle system by conﬁguring its link target to be the ﬁle system's DNS name. For more information, see Group multiple FSx for Windows File Server ﬁle systems with DFS Namespaces. Accessing data using DNS aliases FSx for Windows File
WindowsGuide-020	WindowsGuide.pdf	20	Distributed File System (DFS) namespaces FSx for Windows File Server supports the use of Microsoft DFS Namespaces. Use DFS Namespaces to organize ﬁle shares that are located on multiple ﬁle systems into one common folder structure (a namespace) that you use to access the entire ﬁle dataset. You can use a name in your DFS Namespace to access your Amazon FSx ﬁle system by conﬁguring its link target to be the ﬁle system's DNS name. For more information, see Group multiple FSx for Windows File Server ﬁle systems with DFS Namespaces. Accessing data using DNS aliases FSx for Windows File Server provides a DNS name for every ﬁle system that you can use to access your ﬁle shares. You can also access your ﬁle shares using DNS names other than the default DNS name by registering DNS aliases for your FSx for Windows File Server ﬁle systems. Using DNS aliases, you can move your Windows ﬁle share data to FSx for Windows File Server and continue using the existing DNS names to access data on Amazon FSx. DNS aliases also allow you to use meaningful names that make it easier to administer tools and applications to connect to your Amazon FSx ﬁle systems. You can associate up to 50 DNS aliases with a ﬁle system at any one time. For more information about associating and disassociating DNS aliases with an FSx for Windows File Server ﬁle system, see Managing DNS aliases. To conﬁgure access to your FSx for Windows File Server ﬁle systems using DNS aliases, you must perform the following steps: Using Kerberos authentication with DNS names 35 Amazon FSx for Windows File Server Windows User Guide 1. Associate DNS aliases with your ﬁle system. 2. Create a DNS CNAME record for the ﬁle system and the DNS aliases associated with it. For more information about using DNS aliases with FSx for Windows File Server ﬁle systems, see Managing DNS aliases. Using Kerberos authentication and encryption with DNS aliases We recommend that you use Kerberos-based authentication and encryption in transit with Amazon FSx. Kerberos provides the most secure authentication for clients accessing your ﬁle system. To enable Kerberos authentication for clients that access Amazon FSx using a DNS alias, you must add service principal names (SPNs) that correspond to the DNS alias on your Amazon FSx ﬁle system’s Active Directory computer object. To set up Kerberos authentication and encryption when accessing your ﬁle system using DNS aliases, see Conﬁgure service principal names (SPNs) for Kerberos. You can optionally enforce clients that access the ﬁle system using a DNS alias to use Kerberos authentication and encryption by setting the following Group Policy Objects (GPOs) in your Active Directory: • Restrict NTLM: Outgoing NTLM traﬃc to remote servers - Use this policy setting to deny or audit outgoing NTLM traﬃc from a computer to any remote server running the Windows operating system. • Restrict NTLM: Add remote server exceptions for NTLM authentication - Use this policy setting to create an exception list of remote servers to which client devices are allowed to use NTLM authentication if the Network security: Restrict NTLM: Outgoing NTLM traﬃc to remote servers policy setting is conﬁgured. To enforce Kerberos authentication and encryption when accessing your ﬁle system using DNS aliases, see Enforcing Kerberos authentication using Group Policy Objects (GPOs). For more information about conﬁgure your ﬁle system to use DNS aliases, see the following procedures: • Associate DNS aliases with your ﬁle system • Conﬁgure service principal names (SPNs) for Kerberos • Update or create a DNS CNAME record Using Kerberos authentication and encryption with DNS aliases 36 Amazon FSx for Windows File Server Windows User Guide • Enforcing Kerberos authentication using Group Policy Objects (GPOs) Associate DNS aliases with your ﬁle system You can associate DNS aliases with existing FSx for Windows File Server ﬁle systems, when you create new ﬁle systems, and when you create a new ﬁle system from a backup using the Amazon FSx console, CLI, and API. If you are creating an alias with a diﬀerent domain name, input the full name, including parent domain, to associate an alias. This procedure describes how to associate DNS aliases when creating a new ﬁle system using the Amazon FSx console. For information about associating DNS aliases with existing ﬁle systems, and details about using the CLI and API, see Managing DNS aliases. To associate DNS aliases when creating a new ﬁle system 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. Follow the procedure for creating a new ﬁle system as described in Step 5. Create your ﬁle system of the Getting Started section. 3. In the Access - optional section of the Create ﬁle system wizard, enter the DNS aliases that you want to associate with your ﬁle system. Use the following
WindowsGuide-021	WindowsGuide.pdf	21	ﬁle system using the Amazon FSx console. For information about associating DNS aliases with existing ﬁle systems, and details about using the CLI and API, see Managing DNS aliases. To associate DNS aliases when creating a new ﬁle system 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. Follow the procedure for creating a new ﬁle system as described in Step 5. Create your ﬁle system of the Getting Started section. 3. In the Access - optional section of the Create ﬁle system wizard, enter the DNS aliases that you want to associate with your ﬁle system. Use the following guidelines when specifying DNS aliases: • Must be formatted as a fully qualiﬁed domain name (FQDN) hostname.domain, for example, accounting.example.com. • Can contain alphanumeric characters and hyphens (‐). • Cannot start or end with a hyphen. • Can start with a numeric. For DNS alias names, Amazon FSx stores alphabetic characters as lowercase letters (a- z), regardless of how you specify them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes. For Maintenance preferences, make any changes that you want. In the Tags - optional section, add any tags that you need, and then choose Next. 4. 5. 6. Review the ﬁle system conﬁguration shown on the Create ﬁle system page. Choose Create ﬁle system to create the ﬁle system. Associate DNS aliases with your ﬁle system 37 Amazon FSx for Windows File Server Windows User Guide Conﬁgure service principal names (SPNs) for Kerberos We recommend that you use Kerberos-based authentication and encryption in transit with Amazon FSx. Kerberos provides the most secure authentication for clients that access your ﬁle system. To enable Kerberos authentication for clients that access Amazon FSx using a DNS alias, you must add service principal names (SPNs) that correspond to the DNS alias on your Amazon FSx ﬁle system’s Active Directory computer object. An SPN can only be associated with a single Active Directory computer object at a time. If you have existing SPNs for the DNS name conﬁgured for your original ﬁle system's Active Directory computer object, you must delete them ﬁrst. There are two required SPNs for Kerberos authentication: HOST/alias HOST/alias.domain If the alias is finance.domain.com, the following are the two required SPNs: HOST/finance HOST/finance.domain.com Note You will need to delete any existing HOST SPNs that correspond to the DNS alias on the Active Directory computer object before you create new HOST SPNs for your Amazon FSx ﬁle system's Active Directory (AD) computer object. Attempts to set SPNs for your Amazon FSx ﬁle system will fail if an SPN for the DNS alias exists in the AD. The following procedures describes how to do the following: • Find any existing DNS alias SPNs on the original ﬁle system's Active Directory computer object. • Delete the existing SPNs found, if any. • Create new DNS alias SPNs for your Amazon FSx ﬁle system's Active Directory computer object. Conﬁgure service principal names (SPNs) for Kerberos 38 Amazon FSx for Windows File Server Windows User Guide To install the required PowerShell Active Directory module 1. Log on to a Windows instance joined to the Active Directory to which your Amazon FSx ﬁle system is joined. 2. Open PowerShell as administrator. 3. Install the PowerShell Active Directory module using the following command. Install-WindowsFeature RSAT-AD-PowerShell To ﬁnd and delete existing DNS alias SPNs on the original ﬁle system's Active Directory computer object If you have SPNs conﬁgured for the DNS alias that you've assigned to another ﬁle system on a computer object in your Active Directory, you must ﬁrst remove those SPNs before adding SPNs to your ﬁle system’s computer object. 1. Find any existing SPNs by using the following commands. Replace alias_fqdn with the DNS alias that you associated with the ﬁle system in Step 1. ## Find SPNs for original file system's AD computer object $ALIAS = "alias_fqdn" SetSPN /Q ("HOST/" + $ALIAS) SetSPN /Q ("HOST/" + $ALIAS.Split(".")[0]) 2. Delete the existing HOST SPNs returned in the previous step by using the following example script. • Replace alias_fqdn with the full DNS alias that you associated with the ﬁle system in Step 1. • Replace file_system_DNS_name with the original ﬁle system's DNS name. ## Delete SPNs for original file system's AD computer object $Alias = "alias_fqdn" $FileSystemDnsName = "file_system_dns_name" $FileSystemHost = (Resolve-DnsName ${FileSystemDnsName} \| Where Type -eq 'A') [0].Name.Split(".")[0] $FSxAdComputer = (Get-AdComputer -Identity ${FileSystemHost}) Conﬁgure service principal names (SPNs) for Kerberos 39 Amazon FSx for Windows File Server Windows User Guide SetSPN /D ("HOST/" + ${Alias}) ${FSxAdComputer}.Name SetSPN /D ("HOST/" + ${Alias}.Split(".")[0]) ${FSxAdComputer}.Name 3. Repeat the previous steps for each DNS alias that you've associated with the ﬁle system in Step 1. To set SPNs on your Amazon FSx ﬁle system’s Active Directory computer object 1. Set new SPNs for your Amazon FSx
WindowsGuide-022	WindowsGuide.pdf	22	## Delete SPNs for original file system's AD computer object $Alias = "alias_fqdn" $FileSystemDnsName = "file_system_dns_name" $FileSystemHost = (Resolve-DnsName ${FileSystemDnsName} \| Where Type -eq 'A') [0].Name.Split(".")[0] $FSxAdComputer = (Get-AdComputer -Identity ${FileSystemHost}) Conﬁgure service principal names (SPNs) for Kerberos 39 Amazon FSx for Windows File Server Windows User Guide SetSPN /D ("HOST/" + ${Alias}) ${FSxAdComputer}.Name SetSPN /D ("HOST/" + ${Alias}.Split(".")[0]) ${FSxAdComputer}.Name 3. Repeat the previous steps for each DNS alias that you've associated with the ﬁle system in Step 1. To set SPNs on your Amazon FSx ﬁle system’s Active Directory computer object 1. Set new SPNs for your Amazon FSx ﬁle system by running the following commands. • Replace file_system_DNS_name with the DNS name that Amazon FSx assigned to the ﬁle system. To ﬁnd your ﬁle system's DNS name on the Amazon FSx console, choose File systems, choose your ﬁle system, and then choose the Network & security pane on the ﬁle system details page. You can also get the DNS name in the response of the DescribeFileSystems API operation. • Replace alias_fqdn with the full DNS alias that you associated with the ﬁle system in Step 1. ## Set SPNs for FSx file system AD computer object $FSxDnsName = "file_system_DNS_name" $Alias = "alias_fqdn" $FileSystemHost = (Resolve-DnsName $FSxDnsName \| Where Type -eq 'A') [0].Name.Split(".")[0] $FSxAdComputer = (Get-AdComputer -Identity $FileSystemHost) ##Use the following command to set both the full FQDN and Alias SPNs Set-AdComputer -Identity $FSxAdComputer -Add @{"msDS-AdditionalDnsHostname" = @($Alias, $Alias.Split(".")[0])} Note Setting an SPN for your Amazon FSx ﬁle system will fail if an SPN for the DNS alias exists in the AD for the original ﬁle system's computer object. For information about ﬁnding and deleting existing SPNs, see To ﬁnd and delete existing DNS alias SPNs on the original ﬁle system's Active Directory computer object. Conﬁgure service principal names (SPNs) for Kerberos 40 Amazon FSx for Windows File Server Windows User Guide 2. Verify that the new SPNs are conﬁgured for the DNS alias using the following example script. Ensure that the response includes two HOST SPNs, HOST/alias and HOST/alias_fqdn, as described previously in this procedure. Replace file_system_DNS_name with the DNS name that Amazon FSx assigned to your ﬁle system. To ﬁnd your ﬁle system's DNS name on the Amazon FSx console, choose File systems, choose your ﬁle system, and then choose the Network & security pane on the ﬁle system details page. You can also get the DNS name in the response of the DescribeFileSystems API operation. ## Verify SPNs on FSx file system AD computer object $FileSystemDnsName = "file_system_dns_name" $FileSystemHost = (Resolve-DnsName ${FileSystemDnsName} \| Where Type -eq 'A') [0].Name.Split(".")[0] $FSxAdComputer = (Get-AdComputer -Identity ${FileSystemHost}) SetSpn /L ${FSxAdComputer}.Name 3. Repeat the previous steps for each DNS alias that you've associated with the ﬁle system in Step 1. Update or create a DNS CNAME record After you properly conﬁgure SPNs for your ﬁle system, you can cut over to Amazon FSx by replacing each DNS record that resolved to the original ﬁle system with a DNS record that resolves to the default DNS name of the Amazon FSx ﬁle system. The dnsserver and activedirectory Windows modules are required to run the commands presented in this section. To install the required PowerShell modules 1. Log on to a Windows instance joined to the same Active Directory that your Amazon FSx ﬁle system is joined to as a user that is a member of a group that has DNS administration permissions (AWS Delegated Domain Name System Administrators in AWS Managed Microsoft AD, and Domain Admins or another group to which you've delegated DNS administration permissions in your self-managed Active Directory). For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. Update or create a DNS CNAME record 41 Amazon FSx for Windows File Server Windows User Guide 2. Open PowerShell as administrator. 3. The PowerShell DNS Server module is required to perform the instructions in this procedure. Install it using the following command. Install-WindowsFeature RSAT-DNS-Server To update or create a custom DNS name to your Amazon FSx ﬁle system 1. Connect to your Amazon EC2 instance as a user that is a member of a group that has DNS administration permissions (AWS Delegated Domain Name System Administrators in AWS Managed Active Directory, and Domain Admins or another group to which you've delegated DNS administration permissions in your self-managed Active Directory). For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. 2. At the command prompt, run the following script. This script migrates any existing DNS CNAME records to your Amazon FSx ﬁle system. If none are found, it creates a new DNS CNAME record for the DNS alias alias_fqdn that resolves to the default DNS name for your Amazon FSx ﬁle system. To run the script: • Replace alias_fqdn with the
WindowsGuide-023	WindowsGuide.pdf	23	Administrators in AWS Managed Active Directory, and Domain Admins or another group to which you've delegated DNS administration permissions in your self-managed Active Directory). For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. 2. At the command prompt, run the following script. This script migrates any existing DNS CNAME records to your Amazon FSx ﬁle system. If none are found, it creates a new DNS CNAME record for the DNS alias alias_fqdn that resolves to the default DNS name for your Amazon FSx ﬁle system. To run the script: • Replace alias_fqdn with the DNS alias that you associated with the ﬁle system. • Replace file_system_DNS_name with the DNS name Amazon FSx has assigned to the ﬁle system. $Alias="alias_fqdn" $FSxDnsName="file_system_dns_name" $AliasHost=$Alias.Split('.')[0] $ZoneName=((Get-WmiObject Win32_ComputerSystem).Domain) $DnsServerComputerName = (Resolve-DnsName $ZoneName -Type NS \| Where Type -eq 'A' \| Select -ExpandProperty Name) \| Select -First 1 Add-DnsServerResourceRecordCName -Name $AliasHost -ComputerName $DnsServerComputerName -HostNameAlias $FSxDnsName -ZoneName $ZoneName 3. Repeat the previous step for each DNS alias that you associated with the ﬁle system in Step 1. Update or create a DNS CNAME record 42 Amazon FSx for Windows File Server Windows User Guide You've now added a DNS CNAME value for your Amazon FSx ﬁle system with the DNS alias. You can now use the DNS alias to access your data. Note When updating a DNS CNAME record to point to an Amazon FSx ﬁle system previously pointed to another ﬁle system, clients might not be able to connect with ﬁle system for a brief period of time. When the client DNS cache refreshes, they should be able to connect using the DNS alias. For more information, see Can't access the ﬁle system using a DNS alias. Enforcing Kerberos authentication using Group Policy Objects (GPOs) You can enforce Kerberos authentication when accessing the ﬁle system by setting the following Group Policy Objects (GPOs) in your Active Directory: • Restrict NTLM: Outgoing NTLM traﬃc to remote servers - Use this policy setting to deny or audit outgoing NTLM traﬃc from a computer to any remote server running the Windows operating system. • Restrict NTLM: Add remote server exceptions for NTLM authentication - Use this policy setting to create an exception list of remote servers to which client devices are allowed to use NTLM authentication if the Network security: Restrict NTLM: Outgoing NTLM traﬃc to remote servers policy setting is conﬁgured. 1. Log on to a Windows instance joined to the Active Directory to which your Amazon FSx ﬁle system is joined as an administrator. If you are conﬁguring a self-managed Active Directory, apply these steps directly to your Active Directory. 2. Choose Start, choose Administrative Tools, and then choose Group Policy Management. 3. Choose Group Policy Objects. 4. 5. If your Group Policy Object does not already exist, create it. Locate the existing Network Security: Restrict NTLM: Outgoing NTLM traﬃc to remote servers policy. (If there is no existing policy, create a new policy.) In the Local security setting tab, open the context (right-click) menu, and choose Properties. 6. Choose Deny all. Enforcing Kerberos authentication using Group Policy Objects (GPOs) 43 Amazon FSx for Windows File Server Windows User Guide 7. Choose Apply to save the security setting. 8. To set exceptions for NTLM connections to speciﬁc remote servers for the client, locate the Network security: Restrict NTLM: Add remote server exceptions. Open the context (right-click) menu, and choose Properties in the Local security setting tab. 9. Enter the names of any servers to add to the exception list. 10. Choose Apply to save the security setting. Accessing data using ﬁle shares A Microsoft Windows ﬁle share is a speciﬁc folder or directory on your ﬁle system. It includes any sub folders that might exist. Clients access the ﬁle shares on your ﬁle system using the Server Message Block (SMB) protocol. Your FSx for Windows File Server ﬁle system comes with a default Windows ﬁle share, named share. You can create and manage as many other ﬁle shares as you want by using the Windows Shared Folders graphical user interface (GUI) tool. Microsoft Windows continuously available (CA) shares provide the primary beneﬁt of maintaining uninterrupted access to shared ﬁles even when a server node within a cluster fails. Using CA ﬁle shares can minimize interruptions to the server applications that are storing their data ﬁles on these ﬁle shares during ﬁle system maintenance windows. For more information about creating and managing ﬁle shares on your FSx for Windows File Server ﬁle system, including CA shares, see Creating, updating, removing ﬁle shares. Mapping ﬁle shares To access your ﬁle shares, use the Windows Map Network Drive functionality to map a drive letter on your compute instance to your Amazon FSx ﬁle share. The process of mapping a ﬁle share to a drive
WindowsGuide-024	WindowsGuide.pdf	24	a server node within a cluster fails. Using CA ﬁle shares can minimize interruptions to the server applications that are storing their data ﬁles on these ﬁle shares during ﬁle system maintenance windows. For more information about creating and managing ﬁle shares on your FSx for Windows File Server ﬁle system, including CA shares, see Creating, updating, removing ﬁle shares. Mapping ﬁle shares To access your ﬁle shares, use the Windows Map Network Drive functionality to map a drive letter on your compute instance to your Amazon FSx ﬁle share. The process of mapping a ﬁle share to a drive on your compute instance is known as mounting a ﬁle share in Linux. This process diﬀers depending on the type of compute instance and the operating system. After your ﬁle share is mapped, your applications and users can access ﬁles and folders on your ﬁle share as if they are local ﬁles and folders. For more information about mapping and mounting ﬁle shares to access data on your ﬁle system, see the following procedures: • Mapping a ﬁle share on an Amazon EC2 Windows instance. Accessing data using ﬁle shares 44 Amazon FSx for Windows File Server Windows User Guide • Mounting a ﬁle share on an Amazon EC2 Mac instance • Mounting a ﬁle share on an Amazon EC2 Linux instance Mapping a ﬁle share on an Amazon EC2 Windows instance You can map a ﬁle share on an EC2 Windows instance to access your FSx for Windows File Server ﬁle system by using the Windows File Explorer or the command prompt. To map a ﬁle share on an Amazon EC2 Windows instance (File Explorer) 1. Launch the EC2 Windows instance and connect it to the Microsoft Active Directory that you joined your Amazon FSx ﬁle system to. To do this, choose one of the following procedures from the AWS Directory Service Administration Guide: • Seamlessly join a Windows EC2 instance • Manually join a Windows instance 2. Connect to your EC2 Windows instance. For more information, see Connecting to your Windows instance in the Amazon EC2 User Guide. 3. After you're connected, open File Explorer. 4. 5. 6. In the navigation pane, open the context (right-click) menu for Network, and choose Map Network Drive. For Drive, choose a drive letter. For Folder, enter either the ﬁle system's DNS name or a DNS alias associated with the ﬁle system, and the share name. Important Using an IP address instead of the DNS name could result in unavailability during the failover process of the Multi-AZ ﬁle system. Also, DNS names or associated DNS aliases are required for Kerberos-based authentication in Multi-AZ and Single-AZ ﬁle systems. You can ﬁnd the ﬁle system's DNS name and any associated DNS aliases on the Amazon FSx console by choosing Windows File Server, Network & security. Or, you can ﬁnd them in the response of the CreateFileSystem or DescribeFileSystems API operation. For more information about using DNS aliases, see Managing DNS aliases. Mapping a ﬁle share on an Amazon EC2 Windows instance 45 Amazon FSx for Windows File Server Windows User Guide • For a Single-AZ ﬁle system joined to an AWS Managed Microsoft Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com For example, to use a Single-AZ ﬁle system's DNS name, enter the following for Folder. \\fs-0123456789abcdef0.ad-domain.com\share To use a Multi-AZ ﬁle system's DNS name, enter the following for Folder. \\amznfsxaa11bb22.ad-domain.com\share To use a DNS alias associated with the ﬁle system, enter the following for Folder. \\fqdn-dns-alias\share 7. Choose an option for Reconnect at sign-in, which indicates whether the ﬁle share should reconnect at sign-in, and then choose Finish. To map a ﬁle share on an Amazon EC2 Windows instance (command prompt) 1. Launch the EC2 Windows instance and connect it to the Microsoft Active Directory that you joined your Amazon FSx ﬁle system to. To do this, choose one of the following procedures from the AWS Directory Service Administration Guide: • Seamlessly join a Windows EC2 instance • Manually join a Windows instance 2. Connect to your EC2 Windows instance as a user in your AWS Managed Microsoft AD directory. For more information, see Connecting to your Windows instance in the Amazon EC2 User Guide. Mapping a ﬁle share on an Amazon EC2 Windows instance 46 Amazon FSx for Windows File Server Windows User Guide 3. After you're connected, open a command prompt window. 4. Mount the ﬁle share using a drive letter of your choice, the ﬁle system's DNS name, and the share name. You can ﬁnd the DNS name using the Amazon FSx console by choosing Windows File Server, Network & security. Or, you
WindowsGuide-025	WindowsGuide.pdf	25	your EC2 Windows instance as a user in your AWS Managed Microsoft AD directory. For more information, see Connecting to your Windows instance in the Amazon EC2 User Guide. Mapping a ﬁle share on an Amazon EC2 Windows instance 46 Amazon FSx for Windows File Server Windows User Guide 3. After you're connected, open a command prompt window. 4. Mount the ﬁle share using a drive letter of your choice, the ﬁle system's DNS name, and the share name. You can ﬁnd the DNS name using the Amazon FSx console by choosing Windows File Server, Network & security. Or, you can ﬁnd them in the response of the CreateFileSystem or DescribeFileSystems API operation. • For a Single-AZ ﬁle system joined to an AWS Managed Microsoft Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com The following is an example command to mount the ﬁle share. $ net use H: \\amzfsxaa11bb22.ad-domain.com\share /persistent:yes Instead of the net use command, you can also use any supported PowerShell command to mount a ﬁle share. Mounting a ﬁle share on an Amazon EC2 Mac instance You can mount a ﬁle share on an Amazon EC2 Mac instance that is either joined to your Active Directory or not joined to access your FSx for Windows File Server ﬁle system. If the instance is not joined to your Active Directory, be sure to update the DHCP options set for the Amazon Virtual Private Cloud (Amazon VPC) in which the instance resides to include the DNS name servers for your Active Directory domain. Then relaunch the instance. To mount a ﬁle share on an Amazon EC2 Mac instance (GUI) 1. Launch the EC2 Mac instance. To do this, choose one of the following procedures from the Amazon EC2 User Guide: Mounting a ﬁle share on an Amazon EC2 Mac instance 47 Amazon FSx for Windows File Server Windows User Guide • Launch a Mac instance using the console • Launch a Mac instance using the AWS CLI 2. Connect to your EC2 Mac instance using Virtual Network Computing (VNC). For more information, see Connect to your instance using VNC in the Amazon EC2 User Guide. 3. On your EC2 Mac instance, connect to your Amazon FSx ﬁle share, as follows: a. Open Finder, choose Go, and then choose Connect to Server. b. In the Connect to Server dialog box, enter either the ﬁle system's DNS name or a DNS alias associated with the ﬁle system, and the share name. Then choose Connect. You can ﬁnd the ﬁle system's DNS name and any associated DNS aliases on the Amazon FSx console by choosing Windows File Server, Network & security. Or, you can ﬁnd them in the response of the CreateFileSystem or DescribeFileSystems API operation. For more information about using DNS aliases, see Managing DNS aliases. c. On the next screen, choose Connect to continue. d. Enter your Microsoft Active Directory (AD) credentials for the Amazon FSx service account, as shown in the following example. Then choose Connect. Mounting a ﬁle share on an Amazon EC2 Mac instance 48 Amazon FSx for Windows File Server Windows User Guide e. If the connection is successful, you can see the Amazon FSx share, under Locations in your Finder window. To mount a ﬁle share on an Amazon EC2 Mac instance (command line) 1. Launch the EC2 Mac instance. To do this, choose one of the following procedures from the Amazon EC2 User Guide: • Launch a Mac instance using the console • Launch a Mac instance using the AWS CLI 2. Connect to your EC2 Mac instance using Virtual Network Computing (VNC). For more information, see Connect to your instance using VNC in the Amazon EC2 User Guide. 3. Mount the ﬁle share with the following command. mount_smbfs //file_system_dns_name/file_share mount_point You can ﬁnd the DNS name on the Amazon FSx console by choosing Windows File Server, Network & security. Or, you can ﬁnd them in the response of the CreateFileSystem or DescribeFileSystems API operation. • For a Single-AZ ﬁle system joined to an AWS Managed Microsoft Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com Mounting a ﬁle share on an Amazon EC2 Mac instance 49 Amazon FSx for Windows File Server Windows User Guide • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com The mount command used in this procedure does the following at the given points: • //file_system_dns_name/file_share – Speciﬁes the DNS name and share of the ﬁle system to mount. • mount_point – The directory on the EC2 instance that you are mounting the ﬁle system
WindowsGuide-026	WindowsGuide.pdf	26	Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com Mounting a ﬁle share on an Amazon EC2 Mac instance 49 Amazon FSx for Windows File Server Windows User Guide • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com The mount command used in this procedure does the following at the given points: • //file_system_dns_name/file_share – Speciﬁes the DNS name and share of the ﬁle system to mount. • mount_point – The directory on the EC2 instance that you are mounting the ﬁle system to. Mounting a ﬁle share on an Amazon EC2 Linux instance You can mount an FSx for Windows File Server ﬁle share on an Amazon EC2 Linux instance that is either joined to your Active Directory or not joined to access your FSx for Windows File Server ﬁle system. Note • The following commands specify parameters such as SMB protocol, caching, and read and write buﬀer size as examples only. Parameter choices for the Linux cifs command, as well as the Linux kernel version used, can impact throughput and latency for network operations between the client and the Amazon FSx ﬁle system. For more information, see cifs documentation for the Linux environment you are using. • Linux clients do not support automatic DNS-based failover. For more information, see Failover experience on Linux clients. To mount a ﬁle share on an Amazon EC2 Linux instance joined to an Active Directory 1. If you don't already have a running EC2 Linux instance joined to your Microsoft Active Directory, see Manually join a Linux instance in the AWS Directory Service Administration Guide for the instructions to do so. Mounting a ﬁle share on an Amazon EC2 Linux instance 50 Amazon FSx for Windows File Server Windows User Guide 2. Connect to your EC2 Linux instance. For more information, see Connect to your Linux instance in the Amazon EC2 User Guide. 3. Run the following command to install the cifs-utils package. This package is used to mount network ﬁle systems like Amazon FSx on Linux. $ sudo yum install cifs-utils 4. Create the mount point directory /mnt/fsx. This is where you will mount the Amazon FSx ﬁle system. $ sudo mkdir -p /mnt/fsx 5. Authenticate with kerberos using the following command. $ kinit 6. Mount the ﬁle share with the following command. $ sudo mount -t cifs //file_system_dns_name/file_share mount_point --verbose -o vers=SMB_version,sec=krb5,cruid=ad_user,rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize,cache=none,ip=preferred- file-server-Ip You can ﬁnd the DNS name on the Amazon FSx console by choosing Windows File Server, Network & security. Or, you can ﬁnd them in the response of CreateFileSystem or DescribeFileSystems API operation. • For a Single-AZ ﬁle system joined to an AWS Managed Microsoft Active Directory, the DNS name looks like the following. fs-0123456789abcdef0.ad-domain.com • For a Single-AZ ﬁle system joined to a self-managed Active Directory, and any Multi-AZ ﬁle system, the DNS name looks like the following. amznfsxaa11bb22.ad-domain.com Replace CIFSMaxBufSize with the largest value allowed by your kernel. Run the following command to get this value. Mounting a ﬁle share on an Amazon EC2 Linux instance 51 Amazon FSx for Windows File Server Windows User Guide $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) The output shows that the maximum buﬀer size is 130048. 7. Verify that the ﬁle system is mounted by running the following command, which returns only ﬁle systems of the Common Internet File System (CIFS) type. $ mount -l -t cifs //fs-0123456789abcdef0/share on /mnt/fsx type cifs (rw,relatime,vers=SMB_version,sec=krb5,cache=cache_mode,[email protected],uid=0,noforceuid,gid=0,noforcegid,addr=192.0.2.0,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) The mount command used in this procedure does the following at the given points: • //file_system_dns_name/file_share – Speciﬁes the DNS name and share of the ﬁle system to mount. • mount_point – The directory on the EC2 instance that you are mounting the ﬁle system to. • -t cifs vers=SMB_version – Speciﬁes the type of ﬁle system as CIFS and the SMB protocol version. Amazon FSx for Windows File Server supports SMB versions 2.0 through 3.1.1. • sec=krb5 – Speciﬁes to use Kerberos version 5 for authentication. • cache=cache_mode – Sets the cache mode. This option for CIFS cache can impact performance, and you should test which settings work best (and review Linux documentation) for your kernel and workload. Options strict and none are recommended, because loose can cause data inconsistency due to the looser protocol semantics. • cruid=ad_user – Sets the uid of the owner of the credentials cache to the AD directory administrator. • /mnt/fsx – Speciﬁes the mount point for the Amazon FSx ﬁle share on your EC2 instance. • rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize – Speciﬁes the read and write buﬀer size as the maximum allowed by the CIFS protocol. Replace CIFSMaxBufSize with the largest value allowed by your kernel. Determine the CIFSMaxBufSize by running the
WindowsGuide-027	WindowsGuide.pdf	27	which settings work best (and review Linux documentation) for your kernel and workload. Options strict and none are recommended, because loose can cause data inconsistency due to the looser protocol semantics. • cruid=ad_user – Sets the uid of the owner of the credentials cache to the AD directory administrator. • /mnt/fsx – Speciﬁes the mount point for the Amazon FSx ﬁle share on your EC2 instance. • rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize – Speciﬁes the read and write buﬀer size as the maximum allowed by the CIFS protocol. Replace CIFSMaxBufSize with the largest value allowed by your kernel. Determine the CIFSMaxBufSize by running the following command. $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) Mounting a ﬁle share on an Amazon EC2 Linux instance 52 Amazon FSx for Windows File Server Windows User Guide The output shows that the maximum buﬀer size is 130048. • ip=preferred-file-server-Ip – Sets the destination IP address to that of the ﬁle system's preferred ﬁle server. You can retrieve the ﬁle system's preferred ﬁle server IP address as follows: • Using the Amazon FSx console, on the Network & security tab of the File system details page. • In the response of the describe-file-systems CLI command or the equivalent DescribeFileSystems API command. To mount a ﬁle share on an Amazon EC2 Linux instance not joined to an Active Directory The following procedure mounts an Amazon FSx ﬁle share to an Amazon EC2 Linux instance that is not joined to your Active Directory (AD). For an EC2 Linux instance that is not joined to your AD, you can only mount an FSx for Windows File Server ﬁle share by using its private IP address. You can get the ﬁle system's private IP address using the Amazon FSx console, on the Network & security tab, in Preferred File Server IP Address. This example uses NTLM authentication. To do this, you mount the ﬁle system as a user that is a member of the Microsoft Active Directory domain that the FSx for Windows File Server ﬁle system is joined to. The credentials for the user account are provided in a text ﬁle that you create on your EC2 instance, creds.txt. This ﬁle contains the user name, password, and domain for the user. $ cat creds.txt username=user1 password=Password123 domain=EXAMPLE.COM To launch and conﬁgure the Amazon Linux EC2 instance 1. Launch an Amazon Linux EC2 instance using the Amazon EC2 console. For more information, see Launch an instance in the Amazon EC2 User Guide. 2. Connect to your Amazon Linux EC2 instance. For more information, see Connect to your Linux instance in the Amazon EC2 User Guide. 3. Run the following command to install the cifs-utils package. This package is used to mount network ﬁle systems like Amazon FSx on Linux. Mounting a ﬁle share on an Amazon EC2 Linux instance 53 Amazon FSx for Windows File Server Windows User Guide $ sudo yum install cifs-utils 4. Create the mount point /mnt/fsxx where you plan to mount the Amazon FSx ﬁle system. $ sudo mkdir -p /mnt/fsx 5. Create the creds.txt credentials ﬁle in the /home/ec2-user directory, using the format shown previously. 6. Set the creds.txt ﬁle permissions so that only you (the owner) can read and write to the ﬁle by running the following command. $ chmod 700 creds.txt To mount the ﬁle system 1. You mount a ﬁle share not joined to your Active Directory by using its private IP address. You can get the ﬁle system's private IP address using the Amazon FSx console, on the Network & security tab, in the Preferred File Server IP Address. 2. Mount the ﬁle system using the following command: $ sudo mount -t cifs //file-system-IP-address/file_share /mnt/fsx --verbose -o vers=SMB_version,sec=ntlmsspi,cred=/home/ec2-user/ creds.txt,rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize,cache=none Replace CIFSMaxBufSize with the largest value allowed by your kernel. Run the following command to get this value. $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) The output shows that the maximum buﬀer size is 130048. 3. Verify that the ﬁle system is mounted by running the following command, which returns only CIFS ﬁle systems. $ mount -l -t cifs Mounting a ﬁle share on an Amazon EC2 Linux instance 54 Amazon FSx for Windows File Server Windows User Guide //file-system-IP-address/file_share on /mnt/fsx type cifs (rw,relatime,vers=SMB_version,sec=ntlmsspi,cache=cache_mode,username=user1,domain=CORP.EXAMPLE.COM,uid=0,noforceuid,gid=0,noforcegid,addr=192.0.2.0,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) The mount command used in this procedure does the following at the given points: • //file-system-IP-address/file_share – Speciﬁes the IP address and share of the ﬁle system you're mounting. • -t cifs vers=SMB_version – Speciﬁes the type of ﬁle system as CIFS and the SMB protocol version. Amazon FSx for Windows File Server supports SMB versions 2.0 through 3.1.1. • sec=ntlmsspi – Speciﬁes to use NT LAN Manager Security Support Provider Interface (NTLMSSPI) for
WindowsGuide-028	WindowsGuide.pdf	28	Mounting a ﬁle share on an Amazon EC2 Linux instance 54 Amazon FSx for Windows File Server Windows User Guide //file-system-IP-address/file_share on /mnt/fsx type cifs (rw,relatime,vers=SMB_version,sec=ntlmsspi,cache=cache_mode,username=user1,domain=CORP.EXAMPLE.COM,uid=0,noforceuid,gid=0,noforcegid,addr=192.0.2.0,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) The mount command used in this procedure does the following at the given points: • //file-system-IP-address/file_share – Speciﬁes the IP address and share of the ﬁle system you're mounting. • -t cifs vers=SMB_version – Speciﬁes the type of ﬁle system as CIFS and the SMB protocol version. Amazon FSx for Windows File Server supports SMB versions 2.0 through 3.1.1. • sec=ntlmsspi – Speciﬁes to use NT LAN Manager Security Support Provider Interface (NTLMSSPI) for authentication. • cache=cache_mode – Sets the cache mode. This option for CIFS cache can impact performance, and you should test which settings work best (and review Linux documentation) for your kernel and workload. Options strict and none are recommended, because loose can cause data inconsistency due to the looser protocol semantics. • cred=/home/ec2-user/creds.txt – Speciﬁes where to get the user credentials. • /mnt/fsx – Speciﬁes the mount point for the Amazon FSx ﬁle share on your EC2 instance. • rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize – Speciﬁes the read and write buﬀer size as the maximum allowed by the CIFS protocol. Replace CIFSMaxBufSize with the largest value allowed by your kernel. Determine the CIFSMaxBufSize by running the following command. $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) Automatically mount ﬁle shares on an Amazon EC2 Linux instance You can automatically mount your FSx for Windows File Server ﬁle share to access your FSx for Windows File Server ﬁle system whenever the Amazon EC2 Linux instance to which it's mounted reboots. To do so, add an entry to the /etc/fstab ﬁle on the EC2 instance. The /etc/fstab ﬁle contains information about ﬁle systems. The command mount -a, which runs during instance startup, mounts the ﬁle systems listed in the /etc/fstab ﬁle. Automatically mount ﬁle shares on an Amazon EC2 Linux instance 55 Amazon FSx for Windows File Server Windows User Guide For an Amazon EC2 Linux instance that is not joined to your Active Directory, you can only mount an FSx for Windows File Server ﬁle share by using its private IP address. You can get the ﬁle system's private IP address using the Amazon FSx console, on the Network & security tab, in Preferred File Server IP Address. The following procedure uses Microsoft NTLM authentication. You mount the ﬁle system as a user that is a member of the Microsoft Active Directory domain to which the FSx for Windows File Server ﬁle system is joined. You can retrieve the credentials for the user account from the creds.txt ﬁle using the following command. $ cat creds.txt username=user1 password=Password123 domain=EXAMPLE.COM To automatically mount a ﬁle share on an Amazon Linux EC2 instance not joined to your Active Directory To launch and conﬁgure the Amazon Linux EC2 instance 1. Launch an Amazon Linux EC2 instance using the Amazon EC2 console. For more information, see Launch an instance in the Amazon EC2 User Guide. 2. Connect to your instance. For more information, see Connect to your Linux instance in the Amazon EC2 User Guide. 3. Run the following command to install the cifs-utils package. This package is used to mount network ﬁle systems like Amazon FSx on Linux. $ sudo yum install cifs-utils 4. Create the /mnt/fsx directory. This is where you will mount the Amazon FSx ﬁle system. $ sudo mkdir /mnt/fsx 5. Create the creds.txt credentials ﬁle in the /home/ec2-user directory. 6. Set the ﬁle permissions so that only you (the owner) can read the ﬁle by running the following command. $ sudo chmod 700 creds.txt Automatically mount ﬁle shares on an Amazon EC2 Linux instance 56 Amazon FSx for Windows File Server Windows User Guide To automatically mount the ﬁle system 1. You automatically mount a ﬁle share not joined to your Active Directory by using its private IP address. You can get the ﬁle system's private IP address using the Amazon FSx console, on the Network & security tab, in Preferred File Server IP Address. 2. To automatically mount the ﬁle share using its private IP address, add the following line to the /etc/fstab ﬁle. //file-system-IP-address/file_share /mnt/fsx cifs vers=SMB_version,sec=ntlmsspi,cred=/home/ec2-user/ creds.txt,rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize,cache=none 0 0 Replace CIFSMaxBufSize with the largest value allowed by your kernel. Run the following command to get this value. $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) The output shows that the maximum buﬀer size is 130048. 3. Test the fstab entry by using the mount command with the 'fake' option in conjunction with the 'all' and 'verbose' options. $ sudo mount -fav home/ec2-user/fsx : successfully mounted 4. To mount the ﬁle share, reboot the Amazon EC2 instance. 5. When
WindowsGuide-029	WindowsGuide.pdf	29	/etc/fstab ﬁle. //file-system-IP-address/file_share /mnt/fsx cifs vers=SMB_version,sec=ntlmsspi,cred=/home/ec2-user/ creds.txt,rsize=CIFSMaxBufSize,wsize=CIFSMaxBufSize,cache=none 0 0 Replace CIFSMaxBufSize with the largest value allowed by your kernel. Run the following command to get this value. $ modinfo cifs \| grep CIFSMaxBufSize parm: CIFSMaxBufSize:Network buffer size (not including header). Default: 16384 Range: 8192 to 130048 (uint) The output shows that the maximum buﬀer size is 130048. 3. Test the fstab entry by using the mount command with the 'fake' option in conjunction with the 'all' and 'verbose' options. $ sudo mount -fav home/ec2-user/fsx : successfully mounted 4. To mount the ﬁle share, reboot the Amazon EC2 instance. 5. When the instance is available again, verify that the ﬁle system is mounted by running the following command. $ sudo mount -l -t cifs //file-system-IP-address/file_share on /mnt/fsx type cifs (rw,relatime,vers=SMB_version,sec=ntlmsspi,cache=cache_code,username=user1,domain=CORP.EXAMPLE.COM,uid=0,noforceuid,gid=0,noforcegid,addr=192.0.20.0,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1) The line added to the /etc/fstab ﬁle in this procedure does the following at the given points: Automatically mount ﬁle shares on an Amazon EC2 Linux instance 57 Amazon FSx for Windows File Server Windows User Guide • //file-system-IP-address/file_share – Speciﬁes the IP address and share of the Amazon FSx ﬁle system you're mounting. • /mnt/fsx – Speciﬁes the mount point for the Amazon FSx ﬁle system on your EC2 instance. • cifs vers=SMB_version – Speciﬁes the type of ﬁle system as CIFS and the SMB protocol version. Amazon FSx for Windows File Server supports SMB versions 2.0 through 3.1.1. • sec=ntlmsspi – Speciﬁes using NT LAN Manager Security Support Provider Interface to facilitate NTLM challenge-response authentication. • cache=cache_mode – Sets the cache mode. This option for CIFS cache can impact performance, and you should test which settings work best (and review Linux documentation) for your kernel and workload. Options strict and none are recommended, because loose can cause data inconsistency due to the looser protocol semantics. • cred=/home/ec2-user/creds.txt – Speciﬁes where to get the user credentials. • _netdev – Tells the operating system that the ﬁle system resides on a device that requires network access. Using this option prevents the instance from mounting the ﬁle system until the network service is enabled on the client. • 0 – Indicates that the ﬁle system should be backed up by dump, if it's a nonzero value. For Amazon FSx, this value should be 0. • 0 – Speciﬁes the order in which fsck checks ﬁle systems at boot. For Amazon FSx ﬁle systems, this value should be 0 to indicate that fsck shouldn't run at start up. Creating, updating, removing ﬁle shares This topic describes how you can manage ﬁle shares by performing the following tasks. • Create a new ﬁle share • Modify an existing ﬁle share • Remove an existing ﬁle share You can use the Windows-native Shared Folders GUI and the Amazon FSx CLI for remote management on PowerShell to manage ﬁle shares on your FSx for Windows File Server ﬁle system. You might experience delays when using the Shared Folder GUI (fsmgmt.msc) when ﬁrst opening the context menu for shares located on a diﬀerent ﬁle system. To avoid these delays, use PowerShell to manage ﬁle shares that are located on multiple ﬁle systems. Managing ﬁle shares 58 Amazon FSx for Windows File Server Windows User Guide Microsoft Windows enforces rules and limitations for naming ﬁles and directories. To ensure that you can successfully create and access your data, you should name your ﬁles and directories according to these Windows guidelines. For more information, see Naming Conventions. Warning Amazon FSx requires that the SYSTEM user has Full control NTFS ACL permissions on every folder on which you create an SMB ﬁle share. Do not change the NTFS ACL permissions for this user on your folders, as doing so can make your ﬁle shares inaccessible. Managing ﬁle shares with the Shared Folders GUI To manage ﬁle shares on your Amazon FSx ﬁle system, you can use the Shared Folders GUI. The Shared Folders GUI provides a central location for managing all shared folders on a Windows server. The following procedures describe how to manage your ﬁle shares. To connect shared folders to your FSx for Windows File Server ﬁle system 1. Launch your Amazon EC2 instance and connect it to the Microsoft Active Directory that your Amazon FSx ﬁle system is joined to. To do this, choose one of the following procedures from the AWS Directory Service Administration Guide: • Seamlessly join a Windows EC2 instance • Manually join a Windows instance 2. Connect to your instance as a user that is a member of the ﬁle system administrators group. In AWS Managed Microsoft Active Directory, this group is called AWS Delegated FSx Administrators. In your self-managed Microsoft Active Directory, this group is called Domain Admins or the custom name for the administrators group that you provided during creation. For more information, see Connect to your Windows instance in the
WindowsGuide-030	WindowsGuide.pdf	30	is joined to. To do this, choose one of the following procedures from the AWS Directory Service Administration Guide: • Seamlessly join a Windows EC2 instance • Manually join a Windows instance 2. Connect to your instance as a user that is a member of the ﬁle system administrators group. In AWS Managed Microsoft Active Directory, this group is called AWS Delegated FSx Administrators. In your self-managed Microsoft Active Directory, this group is called Domain Admins or the custom name for the administrators group that you provided during creation. For more information, see Connect to your Windows instance in the Amazon Elastic Compute Cloud User Guide for Windows Instances. 3. Open the Start menu and run fsmgmt.msc using Run As Administrator. Doing this opens the 4. 5. Shared Folders GUI tool. For Action, choose Connect to another computer. For Another computer, enter the Domain Name System (DNS) name for your Amazon FSx ﬁle system, for example amznfsxabcd0123.corp.example.com. Managing ﬁle shares 59 Amazon FSx for Windows File Server Windows User Guide To ﬁnd your ﬁle system's DNS name on the Amazon FSx console, choose File systems, choose your ﬁle system, and then check the Network & Security section of the ﬁle system details page. You can also get the DNS name in the response of the DescribeFileSystems API operation. 6. Choose OK. An entry for your Amazon FSx ﬁle system then appears in the list for the Shared Folders tool. Now that Shared Folders is connected to your Amazon FSx ﬁle system, you can manage the Windows ﬁle shares on the ﬁle system. The default share is called \share. You can do so with the following actions: • Create a new ﬁle share – In the Shared Folders tool, choose Shares in the left pane to see the active shares for your Amazon FSx ﬁle system. Choose New Share and complete the Create a Shared Folder wizard. You have to create the local folder prior to creating the new ﬁle share. You can do so as follows: • Using the Shared Folders tool: click on "Browse" when specifying local folder path and click on "Make new folder" to create the local folder. • Using command line: New-Item -Type Directory -Path \\amznfsxabcd0123.corp.example.com\D$\share \MyNewShare • Modify a ﬁle share – In the Shared Folders tool, open the context (right-click) menu for the ﬁle share that you want to modify in the right pane, and choose Properties. Modify the properties and choose OK. • Remove a ﬁle share – In the Shared Folders tool, open the context (right-click) menu for the ﬁle share that you want to remove in the right pane, and then choose Stop Sharing. Note For Single-AZ 2 and Multi-AZ ﬁle systems, removing ﬁle shares or modifying ﬁle shares (including updating permissions, user limits, and other properties) using the Shared Folders GUI tool is possible only if you connect to fsmgmt.msc using the DNS Name of the Amazon FSx ﬁle system. The Shared Folders GUI tool does not support these actions if you connect using the IP address or DNS alias name of the ﬁle system. Managing ﬁle shares 60 Amazon FSx for Windows File Server Windows User Guide Note If you are using the fsmgmt.msc Shared Folders GUI tool to access shares located on multiple FSx for Windows File Server ﬁle systems, you may experience delays when ﬁrst opening the ﬁle share context menu for a share that is located on a diﬀerent ﬁle system. To avoid these delays, you can manage ﬁle shares using PowerShell as described below. Managing ﬁle shares with PowerShell You can manage ﬁle shares using custom FSx for Windows File Server remote-management commands for PowerShell. These commands can help you to automate managing ﬁle share tasks such as: • Migrating ﬁle shares from existing ﬁle servers to Amazon FSx • Synchronizing ﬁle shares across AWS Regions for disaster recovery • Programmatically managing ongoing ﬁle shares workﬂows, such as team ﬁle-share provisioning To learn how to use the Amazon FSx CLI for remote management on PowerShell, see Using the Amazon FSx CLI for PowerShell. The following table lists the Amazon FSx CLI remote management PowerShell commands that you can use to manage ﬁle shares on FSx for Windows File Server ﬁle systems. Share Management Command Description New-FSxSmbShare Creates a new ﬁle share. Remove-FSxSmbShare Removes a ﬁle share. Get-FSxSmbShare Retrieves existing ﬁle shares. Set-FSxSmbShare Sets properties for a share. Get-FSxSmbShareAccess Retrieves the access control list (ACL) of a share. Managing ﬁle shares 61 Amazon FSx for Windows File Server Windows User Guide Share Management Command Description Grant-FSxSmbShareAccess Adds an allow access control entry (ACE) for a trustee to the security descriptor of a share. Revoke-FSxSmbShareAccess Removes all of the allow ACEs for a trustee from the security descriptor of a share. Block-FSxSmbShareAccess Adds a deny ACE for
WindowsGuide-031	WindowsGuide.pdf	31	for Windows File Server ﬁle systems. Share Management Command Description New-FSxSmbShare Creates a new ﬁle share. Remove-FSxSmbShare Removes a ﬁle share. Get-FSxSmbShare Retrieves existing ﬁle shares. Set-FSxSmbShare Sets properties for a share. Get-FSxSmbShareAccess Retrieves the access control list (ACL) of a share. Managing ﬁle shares 61 Amazon FSx for Windows File Server Windows User Guide Share Management Command Description Grant-FSxSmbShareAccess Adds an allow access control entry (ACE) for a trustee to the security descriptor of a share. Revoke-FSxSmbShareAccess Removes all of the allow ACEs for a trustee from the security descriptor of a share. Block-FSxSmbShareAccess Adds a deny ACE for a trustee to the security descriptor of a share. Unblock-FSxSmbShar eAccess Removes all of the deny ACEs for a trustee from the security descriptor of a share. The online help for each command provides a reference of all command options. To access this help, run the command with a -?, for example New-FSxSmbShare -?. Passing credentials to New-FSxSmbShare You can pass credentials to New-FSxSmbShare so that you can run it in a loop to create hundreds or thousands of shares without having to re-enter credentials each time. Prepare the credential object required to create the ﬁle shares on your FSx for Windows File Server ﬁle server using one of the following options. • To generate the credential object interactively, use the following command. $credential = Get-Credential • To generate the credential object using an AWS Secrets Manager resource, use the following command. $credential = ConvertFrom-Json -InputObject (Get-SECSecretValue -SecretId $AdminSecret).SecretString $FSxAdminUserCredential = (New-Object PSCredential($credential.UserName,(ConvertTo- SecureString $credential.Password -AsPlainText -Force))) Managing ﬁle shares 62 Amazon FSx for Windows File Server Windows User Guide To create a continuously available (CA) share You can create continuously available (CA) shares using the Amazon FSx CLI for Remote Management on PowerShell. CA shares created on an FSx for Windows File Server Multi-AZ ﬁle system are highly durable and highly available. An Amazon FSx Single-AZ ﬁle system is built on a single node cluster. As a result, CA shares created on a Single-AZ ﬁle system are highly durable, but are not highly available. Use the New-FSxSmbShare command with the -ContinuouslyAvailable option set to $True to specify that the share is a continuously available share. The following is an example command to create a CA share. New-FSxSmbShare -Name "New CA Share" -Path "D:\share\new-share" -Description "CA share" -ContinuouslyAvailable $True You can modify the -ContinuouslyAvailable option on an existing ﬁle share using the Set- FSxSmbShare command. Determine if an existing ﬁle share is continuously available Use the following command to view the value of the Continuously Available property for an existing ﬁle share. Invoke-Command -ComputerName powershell_endpoint -ConfigurationName FSxRemoteAdmin - scriptblock { get-fsxsmbshare -name share_name } If CA is enabled, the output will include the following line: [...] ContinuouslyAvailable : True [...] If CA is not enabled, the output will include the following line: [...] ContinuouslyAvailable : False [...] To enable Continuously Available on an existing ﬁle share, use the following command: Invoke-Command -ComputerName powershell_endpoint -ConfigurationName FSxRemoteAdmin - scriptblock { set-fsxsmbshare -name share_name -ContinuouslyAvailable $True} Managing ﬁle shares 63 Amazon FSx for Windows File Server Windows User Guide New-FSxSmbShare command fails with a one-way trust Amazon FSx does not support executing the New-FSxSmbShare PowerShell command in cases where you have a one-way trust and the domain in which the user resides is not conﬁgured to trust the domain associated with Amazon FSx ﬁle system. You can resolve this situation using one of following solutions: • The user executing the New-FSxSmbShare command needs to be in the same domain as the FSx ﬁle system. • You can use the fsmgmt.msc GUI to create shares on your ﬁle system. For more information, see Managing ﬁle shares with the Shared Folders GUI. New-FSxSmbShare command fails with a one-way trust 64 Amazon FSx for Windows File Server Windows User Guide Availability and durability: Single-AZ and Multi-AZ ﬁle systems Amazon FSx for Windows File Server oﬀers two ﬁle system deployment types: Single-AZ and Multi- AZ. The following sections provide information to help you choose the right deployment type for your workloads. For information on the service's availability SLA (Service Level Agreement), see Amazon FSx Service Level Agreement. Single-AZ ﬁle systems are composed of a single Windows ﬁle server instance and a set of storage volumes within a single Availability Zone (AZ). With Single-AZ ﬁle systems, data is automatically replicated to protect it from the failure of a single component in most cases. Amazon FSx continuously monitors for hardware failures, and automatically recovers from failure events by replacing the failed infrastructure component. Single-AZ ﬁle systems usually experience about 30 minutes of downtime during failure recovery events, and during the planned maintenance window that you conﬁgure for your ﬁle system. With Single-AZ ﬁle systems, ﬁle system failure may be unrecoverable in rare cases, such as due to multiple component
WindowsGuide-032	WindowsGuide.pdf	32	server instance and a set of storage volumes within a single Availability Zone (AZ). With Single-AZ ﬁle systems, data is automatically replicated to protect it from the failure of a single component in most cases. Amazon FSx continuously monitors for hardware failures, and automatically recovers from failure events by replacing the failed infrastructure component. Single-AZ ﬁle systems usually experience about 30 minutes of downtime during failure recovery events, and during the planned maintenance window that you conﬁgure for your ﬁle system. With Single-AZ ﬁle systems, ﬁle system failure may be unrecoverable in rare cases, such as due to multiple component failures or due to a non-graceful failure of the single ﬁle server that leaves the ﬁle system in an inconsistent state, in which case you can recover your ﬁle system from the most recent backup. Multi-AZ ﬁle systems are composed of a high-availability cluster of Windows ﬁle servers spread across two AZs (a preferred AZ and a standby AZ), leveraging Windows Server Failover Clustering (WSFC) technology and a set of storage volumes on each of the two AZs. Data is replicated synchronously within each individual AZ and between the two AZs. Relative to Single-AZ deployment, Multi-AZ deployments provide enhanced durability by further replicating data across AZs, and enhanced availability during planned system maintenance and unplanned service disruption by failing over automatically to the standby AZ. This allows you to continue accessing your data, and helps to protect your data against instance failure and AZ disruption. Choosing Single-AZ or Multi-AZ ﬁle system deployment type We recommend using Multi-AZ ﬁle systems for most production workloads given the high availability and durability model it provides. Single-AZ deployment is designed as a cost-eﬃcient solution for test and development workloads, certain production workloads that have replication built into the application layer and do not require additional storage-level redundancy, and production workloads that have relaxed availability and Recovery Point Objective (RPO) needs. Workloads with relaxed availability and RPO needs can tolerate temporary loss of availability for Choosing Single-AZ or Multi-AZ ﬁle system deployment type 65 Amazon FSx for Windows File Server Windows User Guide up to 20 minutes in the event of planned ﬁle system maintenance or unplanned service disruption and, in rare cases, the loss of data updates since the most recent backup. We also recommend reviewing the availability model for your ﬁle system and ensuring that your workload is resilient to the expected recovery behavior for the deployment type you choose during events such as ﬁle system maintenance, throughput capacity changes, and unplanned service disruptions. Feature support by deployment type The following table summarizes features supported by the FSx for Windows File Server ﬁle system deployment types: Deploymen t type SSD storage HDD storage DFS namespace DFS replication ✓ ✓ ✓ ✓ ✓ ✓ s ✓ ✓ ✓ Single- AZ 1 Single- AZ 2 Multi-AZ Note CA shares Custom DNS names ✓ ✓ ✓ ✓* ✓* * While you can create continously available (CA) shares on Single-AZ 2 ﬁle systems, you should use CA shares on Multi-AZ ﬁle systems for SQL Server HA deployments. Failing over process Multi-AZ ﬁle systems automatically fail over from the preferred ﬁle server to the standby ﬁle server if any of the following conditions occur: • An Availability Zone outage occurs. Feature support by deployment type 66 Amazon FSx for Windows File Server Windows User Guide • The preferred ﬁle server becomes unavailable. • The preferred ﬁle server undergoes planned maintenance. When failing over from one ﬁle server to another, the new active ﬁle server automatically begins serving all ﬁle system read and write requests. When the resources in the preferred subnet are available, Amazon FSx automatically fails back to the preferred ﬁle server in the preferred subnet. A failover typically completes in less than 30 seconds from the detection of the failure on the active ﬁle server to the promotion of the standby ﬁle server to active status. Failback to the original Multi-AZ conﬁguration also completes in less than 30 seconds, and only occurs once the ﬁle server in the preferred subnet is fully recovered. During the brief period in which your ﬁle system is failing over and failing back, I/O may be paused and Amazon CloudWatch metrics may be temporarily unavailable. For Multi-AZ ﬁle systems, any ﬁle read and write activity that occurs during failover and failback will need to be synchronized between the primary and secondary ﬁle servers. This process can take up to multiple hours for ﬁle systems with HDD storage, and for workloads that are write-heavy and IOPS-heavy. We recommend testing the impact of failovers on your application while your ﬁle system is under a lighter load. Failover experience on Windows clients When failing over from one ﬁle server to another, the new active ﬁle server automatically begins servicing all ﬁle system read and
WindowsGuide-033	WindowsGuide.pdf	33	may be temporarily unavailable. For Multi-AZ ﬁle systems, any ﬁle read and write activity that occurs during failover and failback will need to be synchronized between the primary and secondary ﬁle servers. This process can take up to multiple hours for ﬁle systems with HDD storage, and for workloads that are write-heavy and IOPS-heavy. We recommend testing the impact of failovers on your application while your ﬁle system is under a lighter load. Failover experience on Windows clients When failing over from one ﬁle server to another, the new active ﬁle server automatically begins servicing all ﬁle system read and write requests. After the resources in the preferred subnet are available, Amazon FSx automatically fails back to the preferred ﬁle server in the preferred subnet. Because the ﬁle system's DNS name remains the same, failovers are transparent to Windows applications, which resume ﬁle system operations without manual intervention. A failover typically completes in less than 30 seconds from the detection of the failure on the active ﬁle server to the promotion of the standby ﬁle server to active status. Failback to the original Multi-AZ conﬁguration also completes in less than 30 seconds, and only occurs after the ﬁle server in the preferred subnet is fully recovered. Failover experience on Linux clients Linux clients do not support automatic DNS-based failover. Therefore, they don't automatically connect to the standby ﬁle server during a failover. They will automatically resume ﬁle system operations after the Multi-AZ ﬁle system has failed back to the ﬁle server in the preferred subnet. Failover experience on Windows clients 67 Amazon FSx for Windows File Server Windows User Guide Testing failover on a ﬁle system You can test failover your Multi-AZ ﬁle system by modifying its throughput capacity. When you modify your ﬁle system's throughput capacity, Amazon FSx switches out the ﬁle system's ﬁle server. Multi-AZ ﬁle systems automatically fail over to the secondary server while Amazon FSx replaces the preferred server ﬁle server ﬁrst. Then the ﬁle system automatically fails back to the new primary server and Amazon FSx replaces the secondary ﬁle server. You can monitor the progress of the throughput capacity update request in the Amazon FSx console, the CLI, and the API. Once the update has completed successfully, your ﬁle system has failed over to the secondary server, and failed back to the primary server. For more information about modifying your ﬁle system's throughput capacity and monitoring the progress of the request, see Managing throughput capacity. Single-AZ and Multi-AZ ﬁle system resources Single-AZ and Multi-AZ ﬁle systems consume subnets and elastic network interfaces diﬀerently, as explained in the following sections. Subnets When you create a virtual private cloud (VPC), it spans all the Availability Zones (AZs) in the AWS Region. Availability Zones are distinct locations that are engineered to be isolated from failures in other Availability Zones. After creating a VPC, you can add one or more subnets in each Availability Zone. The default VPC has a subnet in each Availability Zone. A subnet is a range of IP addresses in your VPC. A subnet must reside in a single Availability Zone. FSx for Windows File Server Single-AZ ﬁle systems require one subnet which you specify at creation. The subnet you choose deﬁnes the Availability Zone in which the ﬁle system gets created. Multi-AZ ﬁle systems require two subnets, one for the preferred ﬁle server and one for the standby ﬁle server. The two subnets you choose must be in diﬀerent Availability Zones within the same AWS Region. For in-AWS applications, we recommend that you launch your clients in the same Availability Zone as your preferred ﬁle server to minimize latency. Testing failover on a ﬁle system 68 Amazon FSx for Windows File Server Windows User Guide File system elastic network interfaces An elastic network interfaces is a logical networking component in a VPC that represents a virtual network card. When you create an Amazon FSx ﬁle system, Amazon FSx provisions one or more elastic network interface in the VPC that you associate with your ﬁle system. The elastic network interface enables clients to communicate with and mount the ﬁle system. The elastic network interface is considered to be within the service scope of Amazon FSx, despite it being part of your account's VPC. Multi-AZ ﬁle systems have two elastic network interfaces, one for each ﬁle server. Single-AZ ﬁle systems have one elastic network interface. Warning Do not modify or delete the elastic network interfaces associated with your ﬁle systems. Modifying or deleting the network interface can cause a permanent loss of connection between your VPC and your ﬁle system. The following table summarizes resource utilization for FSx for Windows File Server Single-AZ and Multi-AZ ﬁle systems: File system deployment type Number of subnets Number of elastic network interfaces Number of IP addresses Single-AZ 2
WindowsGuide-034	WindowsGuide.pdf	34	FSx, despite it being part of your account's VPC. Multi-AZ ﬁle systems have two elastic network interfaces, one for each ﬁle server. Single-AZ ﬁle systems have one elastic network interface. Warning Do not modify or delete the elastic network interfaces associated with your ﬁle systems. Modifying or deleting the network interface can cause a permanent loss of connection between your VPC and your ﬁle system. The following table summarizes resource utilization for FSx for Windows File Server Single-AZ and Multi-AZ ﬁle systems: File system deployment type Number of subnets Number of elastic network interfaces Number of IP addresses Single-AZ 2 Single-AZ 1 Multi-AZ 1 1 2 1 1 2 2 1 4 Once a ﬁle system is created, its IP addresses don't change until the ﬁle system is deleted. Important Amazon FSx doesn't support accessing ﬁle systems from, or exposing ﬁle system to the public Internet. If an Elastic IP address, which is a public IP address reachable from the Internet, gets attached to a ﬁle system's elastic network interface, Amazon FSx automatically detaches it. File system elastic network interfaces 69 Amazon FSx for Windows File Server Windows User Guide Working with Microsoft Active Directory When you create an FSx for Windows File Server ﬁle system, you join it to your Active Directory domain to provide user authentication and ﬁle- and folder-level access control. Amazon FSx works with Microsoft Active Directory to integrate with your existing Microsoft Windows environments. Amazon FSx provides two options using your FSx for Windows File Server ﬁle system with Active Directory: Using Amazon FSx with AWS Directory Service for Microsoft Active Directory and Using a self-managed Microsoft Active Directory. Active Directory is the Microsoft directory service used to store information about objects on the network and make this information easy for administrators and users to ﬁnd and use. These objects typically include shared resources such as ﬁle servers and network user and computer accounts. Your users can then use their existing user identities in Active Directory to authenticate themselves and access the FSx for Windows File Server ﬁle system. Users can also use their existing identities to control access to individual ﬁles and folders. In addition, you can migrate your existing ﬁles and folders along with their security access control list (ACL) conﬁguration to Amazon FSx without any modiﬁcations. Note Amazon FSx supports Microsoft Azure Active Directory Domain Services, which you can join to a Microsoft Azure Active Directory. After you create a joined Active Directory conﬁguration for a ﬁle system, you can update only the following properties: • Service user credentials • DNS server IP addresses You cannot change the following properties for your joined Microsoft AD after you've created the ﬁle system: • DomainName • OrganizationalUnitDistinguishedName • FileSystemAdministratorsGroup 70 Amazon FSx for Windows File Server Windows User Guide However, you can create a new ﬁle system from a backup and change these properties in the new ﬁle system's Microsoft Active Directory integration conﬁguration. For more information, see Restoring backups to new ﬁle system. Note Amazon FSx does not support Active Directory Connector and Simple Active Directory. Your FSx for Windows File Server may become Misconﬁgured if there is a change in your Active Directory conﬁguration that disrupts the connection to your ﬁle system. To return your ﬁle system to the Available state, select the Attempt Recovery button in the Amazon FSx console, or use the StartMisconfiguredStateRecovery command in the Amazon FSx API or console. For more information see File system is in a misconﬁgured state. Topics • Using Amazon FSx with AWS Directory Service for Microsoft Active Directory • Using a self-managed Microsoft Active Directory Using Amazon FSx with AWS Directory Service for Microsoft Active Directory AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD) provides fully managed, highly available, actual Active Directory directories in the cloud. You can use these Active Directory directories in your workload deployment. If your organization is using AWS Managed Microsoft AD to manage identities and devices, we recommend that you integrate your Amazon FSx ﬁle system with AWS Managed Microsoft AD. By doing this, you get a turnkey solution using Amazon FSx with AWS Managed Microsoft AD. AWS handles the deployment, operation, high availability, reliability, security, and seamless integration of the two services, enabling you to focus on operating your own workload eﬀectively. To use Amazon FSx with your AWS Managed Microsoft AD setup, you can use the Amazon FSx console. When you create a new FSx for Windows File Server ﬁle system in the console, choose AWS Managed Active Directory under the Windows Authentication section. You also choose the speciﬁc directory that you want to use. For more information, see Step 5. Create your ﬁle system. Using AWS Managed Microsoft AD 71 Amazon FSx for Windows File Server Windows User Guide Your organization might
WindowsGuide-035	WindowsGuide.pdf	35	security, and seamless integration of the two services, enabling you to focus on operating your own workload eﬀectively. To use Amazon FSx with your AWS Managed Microsoft AD setup, you can use the Amazon FSx console. When you create a new FSx for Windows File Server ﬁle system in the console, choose AWS Managed Active Directory under the Windows Authentication section. You also choose the speciﬁc directory that you want to use. For more information, see Step 5. Create your ﬁle system. Using AWS Managed Microsoft AD 71 Amazon FSx for Windows File Server Windows User Guide Your organization might manage identities and devices on a self-managed Active Directory domain (on-premises or in the cloud). If so, you can join your Amazon FSx ﬁle system directly to your existing, self-managed Active Directory domain. For more information, see Using a self-managed Microsoft Active Directory. Additionally, you can also set up your system to beneﬁt from a resource forest isolation model. In this model, you isolate your resources, including your Amazon FSx ﬁle systems, into a separate Active Directory forest from the one where your users are. Important For Single-AZ 2 and all Multi-AZ ﬁle systems, the Active Directory fully qualiﬁed domain name (FQDN) cannot exceed 47 characters. Networking prerequisites Before you create an FSx for Windows File Server ﬁle system joined to your AWS Microsoft Managed Active Directory domain, make sure that you have created and set up the following network conﬁgurations: • For VPC security groups, the default security group for your default Amazon VPC is already added to your ﬁle system in the console. Please ensure that the security group and the VPC Network ACLs for the subnet(s) where you're creating your FSx ﬁle system allow traﬃc on the ports and in the directions shown in the following diagram. Networking prerequisites 72 Amazon FSx for Windows File Server Windows User Guide The following table identiﬁes the role of each port. Protocol TCP/UDP TCP/UDP TCP/UDP Ports 53 88 464 Role Domain Name System (DNS) Kerberos authentic ation Change/ Se t password Networking prerequisites 73 Amazon FSx for Windows File Server Windows User Guide Protocol TCP/UDP UDP TCP Ports 389 123 135 TCP 445 Role Lightweig ht Directory Access Protocol (LDAP) Network Time Protocol (NTP) Distribut ed Computing Environme nt / End Point Mapper (DCE / EPMAP) Directory Services SMB ﬁle sharing Networking prerequisites 74 Amazon FSx for Windows File Server Windows User Guide Protocol TCP TCP TCP Ports 636 3268 3269 TCP 5985 Role Lightweig ht Directory Access Protocol over TLS/ SSL (LDAPS) Microsoft Global Catalog Microsoft Global Catalog over SSL WinRM 2.0 (Microsof t Windows Remote Managemen t) Networking prerequisites 75 Role Microsoft AD DS Web Services, PowerShel l Ephemeral ports for RPC Amazon FSx for Windows File Server Windows User Guide Protocol TCP Ports 9389 TCP 49152 - 65535 Important Allowing outbound traﬃc on TCP port 9389 is required for Single-AZ 2 and all Multi-AZ ﬁle system deployments. Note If you're using VPC network ACLs, you must also allow outbound traﬃc on dynamic ports (49152-65535) from your FSx ﬁle system. • If you are connecting your Amazon FSx ﬁle system to an AWS Managed Microsoft Active Directory in a diﬀerent VPC or account, then ensure connectivity between that VPC and the Amazon VPC where you want to create the ﬁle system. For more information, see Using Amazon FSx with AWS Managed Microsoft AD in a diﬀerent VPC or account. Important While Amazon VPC security groups require ports to be opened only in the direction that network traﬃc is initiated, VPC network ACLs require ports to be open in both directions. Networking prerequisites 76 Amazon FSx for Windows File Server Windows User Guide Use the Amazon FSx Network Validation tool to validate connectivity to your Active Directory domain controllers. Using a resource forest isolation model You join your ﬁle system to an AWS Managed Microsoft AD setup. You then establish a one-way forest trust relationship between an AWS Managed Microsoft AD domain that you create and your existing self-managed Active Directory domain. For Windows authentication in Amazon FSx, you only need a one-way directional forest trust, where the AWS managed forest trusts the corporate domain forest. Your corporate domain takes the role of the trusted domain, and the AWS Directory Service managed domain takes the role of the trusting domain. Validated authentication requests travel between the domains in only one direction—allowing accounts in your corporate domain to authenticate against resources shared in the managed domain. In this case, Amazon FSx interacts only with the AWS managed domain. In a Kerberos authentication scenario, authentication requests originating from a corporate client get validated by the corporate domain, which then refers it to the AWS Managed Microsoft AD, and eventually the client presents its service ticket to your FSx for Windows File
WindowsGuide-036	WindowsGuide.pdf	36	takes the role of the trusted domain, and the AWS Directory Service managed domain takes the role of the trusting domain. Validated authentication requests travel between the domains in only one direction—allowing accounts in your corporate domain to authenticate against resources shared in the managed domain. In this case, Amazon FSx interacts only with the AWS managed domain. In a Kerberos authentication scenario, authentication requests originating from a corporate client get validated by the corporate domain, which then refers it to the AWS Managed Microsoft AD, and eventually the client presents its service ticket to your FSx for Windows File Server ﬁle system. For more information about trusts, see the post Everything you wanted to know about trusts with AWS Managed Microsoft AD in the AWS Security Blog. Test your Active Directory conﬁguration Before creating your Amazon FSx ﬁle system, we recommend that you validate the connectivity to your Active Directory domain controllers using the Amazon FSx Network Validation tool. For more information, see Validating connectivity to your Active Directory domain controllers. The following related resources can help you as you use AWS Directory Service for Microsoft Active Directory with FSx for Windows File Server: • What is AWS Directory Service in the AWS Directory Service Administration Guide • Create your AWS Managed Active Directory in the AWS Directory Service Administration Guide • When to Create a Trust Relationship in the AWS Directory Service Administration Guide Using a resource forest isolation model 77 Amazon FSx for Windows File Server Windows User Guide Using Amazon FSx with AWS Managed Microsoft AD in a diﬀerent VPC or account You can join your FSx for Windows File Server ﬁle system to an AWS Managed Microsoft AD directory that's in a diﬀerent VPC within the same account by using VPC peering. You can also join your ﬁle system to an AWS Managed Microsoft AD directory that's in a diﬀerent AWS account by using directory sharing. Note You can only select an AWS Managed Microsoft AD within the same AWS Region as your ﬁle system. If you want to use a cross-Region VPC peering setup, you should use a self- managed Microsoft Active Directory. For more information, see Using a self-managed Microsoft Active Directory. The workﬂow for joining your ﬁle system to an AWS Managed Microsoft AD that's in a diﬀerent VPC involves the following steps: 1. Set up your networking environment. 2. Share your directory. 3. Join your ﬁle system to the shared directory. For more information, see Share your directory in the AWS Directory Service Administration Guide. To set up your networking environment you can use AWS Transit Gateway or Amazon VPC and create a VPC peering connection. In addition, make sure that network traﬃc is allowed between the two VPCs. A transit gateway is a network transit hub that you can use to interconnect your VPCs and on- premises networks. For more information about using VPC transit gateways, see Getting Started with Transit Gateways in the Amazon VPC Transit Gateways Guide. A VPC peering connection is a networking connection between two VPCs. This connection enables you to route traﬃc between them using private Internet Protocol version 4 (IPv4) or Internet Protocol version 6 (IPv6) addresses. You can use VPC peering to connect VPCs within the same AWS Region or between AWS Regions. For more information on VPC peering, see What is VPC Peering? in the Amazon VPC Peering Guide. Using AWS Managed Microsoft AD in diﬀerent VPC or account 78 Amazon FSx for Windows File Server Windows User Guide There is another prerequisite when you join your ﬁle system to an AWS Managed Microsoft AD directory in a diﬀerent account than that of your ﬁle system. You also need to share your Microsoft Active Directory with the other account. To do this, you can use AWS Managed Microsoft Active Directory's directory sharing feature. To learn more, see Share your directory in the AWS Directory Service Administration Guide. Validating connectivity to your Active Directory domain controllers Before you create an FSx for Windows File Server ﬁle system joined to your Active Directory, use the Amazon FSx Active Directory Validation tool to validate the connectivity to your Active Directory domain. You can use this test whether you are using FSx for Windows File Server with AWS Managed Microsoft Active Directory or with a self-managed Active Directory conﬁguration. The Domain Controller Network Connectivity test (Test-FSxADControllerConnection) does not run the full suite of network connectivity checks against every domain controller in the domain. Instead, use this test to run network connectivity validation against a speciﬁc set of domain controllers. To validate connectivity to your Active Directory domain controllers 1. Launch an Amazon EC2 Windows instance in the same subnet and with the same Amazon VPC security groups that you will use for your FSx for Windows
WindowsGuide-037	WindowsGuide.pdf	37	test whether you are using FSx for Windows File Server with AWS Managed Microsoft Active Directory or with a self-managed Active Directory conﬁguration. The Domain Controller Network Connectivity test (Test-FSxADControllerConnection) does not run the full suite of network connectivity checks against every domain controller in the domain. Instead, use this test to run network connectivity validation against a speciﬁc set of domain controllers. To validate connectivity to your Active Directory domain controllers 1. Launch an Amazon EC2 Windows instance in the same subnet and with the same Amazon VPC security groups that you will use for your FSx for Windows File Server ﬁle system. For Multi-AZ deployment types, use the subnet for the preferred active ﬁle server. 2. Join your EC2 Windows instance to your Active Directory. For more information, see Manually Join a Windows Instance in the AWS Directory Service Administration Guide. 3. Connect to your EC2 instance. For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. 4. Open a Windows PowerShell window (using Run as Administrator) on the EC2 instance. To test whether the required Active Directory module for Windows PowerShell is installed, use the following test command. PS C:\> Import-Module ActiveDirectory If above returns an error, install it using the following command. Validating connectivity to your Active Directory domain controllers 79 Amazon FSx for Windows File Server Windows User Guide PS C:\> Install-WindowsFeature RSAT-AD-PowerShell 5. Download the network validation tool using the following command. PS C:\> Invoke-WebRequest "https://docs.aws.amazon.com/fsx/latest/WindowsGuide/ samples/AmazonFSxADValidation.zip" -OutFile "AmazonFSxADValidation.zip" 6. Expand the zip ﬁle by using the following command. PS C:\> Expand-Archive -Path "AmazonFSxADValidation.zip" 7. Add the AmazonFSxADValidation module to the current session. PS C:\> Import-Module .\AmazonFSxADValidation 8. Set the value for the Active Directory domain controller IP address and run the connectivity test using the following commands: $ADControllerIp = '10.0.75.243' $Result = Test-FSxADControllerConnection -ADControllerIp $ADControllerIp 9. The following example demonstrates retrieving the test output, with results of a successful connectivity test. PS C:\AmazonFSxADValidation> $Result Name Value ---- ----- TcpDetails {@{Port=88; Result=Listening; Description=Kerberos authentication}, @{Port=135; Resul... Server 10.0.75.243 UdpDetails {@{Port=88; Result=Timed Out; Description=Kerberos authentication}, @{Port=123; Resul... Success True PS C:\AmazonFSxADValidation> $Result.TcpDetails Port Result Description ---- ------ ----------- Validating connectivity to your Active Directory domain controllers 80 Amazon FSx for Windows File Server Windows User Guide 88 Listening Kerberos authentication 135 Listening DCE / EPMAP (End Point Mapper) 389 Listening Lightweight Directory Access Protocol (LDAP) 445 Listening Directory Services SMB file sharing 464 Listening Kerberos Change/Set password 636 Listening Lightweight Directory Access Protocol over TLS/SSL (LDAPS) 3268 Listening Microsoft Global Catalog 3269 Listening Microsoft Global Catalog over SSL 9389 Listening Microsoft AD DS Web Services, PowerShell The following example shows running the test and getting a failed result. PS C:\AmazonFSxADValidation> $Result = Test-FSxADControllerConnection - ADControllerIp $ADControllerIp WARNING: TCP 9389 failed to connect. Required for Microsoft AD DS Web Services, PowerShell. Verify security group and firewall settings on both client and directory controller. WARNING: 1 ports failed to connect to 10.0.75.243. Check pre-requisites in https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD.html#self- manage-prereqs PS C:\AmazonFSxADValidation> $Result Name Value ---- ----- TcpDetails {@{Port=88; Result=Listening; Description=Kerberos authentication}, @{Port=135; Resul... Server 10.0.75.243 UdpDetails {@{Port=88; Result=Timed Out; Description=Kerberos authentication}, @{Port=123; Resul... Success False FailedTcpPorts {9389} PS C:\AmazonFSxADValidation> $Result.FailedTcpPorts 9389 ``` Windows socket error code mapping https://msdn.microsoft.com/en-us/library/ms740668.aspx Validating connectivity to your Active Directory domain controllers 81 Amazon FSx for Windows File Server Windows User Guide Note As an alternative to the above procedure, you can use the AWSSupport- ValidateFSxWindowsADConfig runbook to validate your self-managed Active Directory conﬁguration. For more information, see AWSSupport-ValidateFSxWindowsADConfig in the AWS Systems Manager Automation runbook reference. Using a self-managed Microsoft Active Directory If your organization manages identities and devices using a self-managed Active Directory on- premises or in the cloud, you can join an FSx for Windows File Server ﬁle system to your Active Directory domain at creation. When you join your ﬁle system to your self-managed Active Directory, your FSx for Windows File Server ﬁle system resides in the same Active Directory forest (the top logical container in an Active Directory conﬁguration that contains domains, users, and computers) and in the same Active Directory domain as your users and existing resources (including existing ﬁle servers). Note You can isolate your resources—including your Amazon FSx ﬁle systems—into a separate Active Directory forest from the one where your users reside. To do this, join your ﬁle system to an AWS Managed Microsoft Active Directory and establish a one-way forest trust relationship between an AWS Managed Microsoft Active Directory that you create and your existing self-managed Active Directory. • User name and password for a service account on your Active Directory domain, for Amazon FSx to use to join the ﬁle system to your Active Directory domain. • (Optional) The Organizational Unit (OU) in your domain in which you want your ﬁle system to be joined. • (Optional) The domain group
WindowsGuide-038	WindowsGuide.pdf	38	Active Directory forest from the one where your users reside. To do this, join your ﬁle system to an AWS Managed Microsoft Active Directory and establish a one-way forest trust relationship between an AWS Managed Microsoft Active Directory that you create and your existing self-managed Active Directory. • User name and password for a service account on your Active Directory domain, for Amazon FSx to use to join the ﬁle system to your Active Directory domain. • (Optional) The Organizational Unit (OU) in your domain in which you want your ﬁle system to be joined. • (Optional) The domain group to which you want to delegate authority to perform administrative actions on your ﬁle system. For example, this domain group might manage Windows ﬁle shares, manage Access Control Lists (ACLs) on the ﬁle system's root folder, take ownership of ﬁles and folders, and so on. If you don’t specify this group, Amazon FSx delegates this authority to the Domain Admins group in your Active Directory domain by default. Using a self-managed Active Directory 82 Amazon FSx for Windows File Server Windows User Guide Note The domain group name you provide must be unique in your Active Directory. FSx for Windows File Server will not create the domain group under the following circumstances: • If a group already exists with the name you specify • If you do not specify a name, and a group named "Domain Admins" already exists in your Active Directory. For more information, see Joining an Amazon FSx ﬁle system to a self-managed Microsoft Active Directory domain. Topics • Prerequisites • Best practices when using a self-managed Active Directory • Amazon FSx service account • Delegating permissions to the Amazon FSx service account or group • Validating your Active Directory conﬁguration • Joining an Amazon FSx ﬁle system to a self-managed Microsoft Active Directory domain • Getting the correct ﬁle system IP addresses to use for manual DNS entries • Updating a self-managed Active Directory conﬁguration • Changing the Amazon FSx service account • Monitoring self-managed Active Directory updates Prerequisites Before you join an FSx for Windows File Server ﬁle system to your self-managed Microsoft Active Directory domain, review the following prerequisites to help ensure that you can successfully join your Amazon FSx ﬁle system to your self-managed Active Directory. On-premises conﬁgurations These are the prerequisites for your self-managed Microsoft Active Directory, either an on-premises or cloud-based, that you will join the Amazon FSx ﬁle system to. Prerequisites 83 Amazon FSx for Windows File Server Windows User Guide • The Active Directory domain controllers: • Must have a domain functional level at Windows Server 2008 R2 or higher. • Must be writable. • At least one of the reachable domain controllers must be a Global Catalog of the forest. • The DNS server must be able to resolve names as follows: • In the domain that you are joining the ﬁle system • In the root domain of the forest • The DNS server and Active Directory domain controller IP addresses must meet the following requirements, which vary depending on when your Amazon FSx ﬁle system was created: For ﬁle systems created before December 17, 2020 For ﬁle systems created after December 17, 2020 IP addresses must be in an RFC 1918 private IP address range: IP addresses can be in any range, except: • IP addresses that conﬂict with Amazon • 10.0.0.0/8 • 172.16.0.0/12 • 192.168.0.0/16 Web Services owned IP addresses in the AWS Region that the ﬁle system is in. For a list of AWS owned IP addresses by region, see the AWS IP address ranges. • IP addresses in the CIDR block range of 198.19.0.0/16 If you need to access an FSx for Windows File Server ﬁle system that was created before December 17, 2020 using a non-private IP address range, you can create a new ﬁle system by restoring a backup of the ﬁle system. For more information, see Restoring a backup to a new ﬁle system. • The domain name of your self-managed Active Directory must meet the following requirements: • The domain name isn't in Single Label Domain (SLD) format. Amazon FSx doesn't support SLD domains. • For Single-AZ 2 and all Multi-AZ ﬁle systems, the domain name cannot exceed 47 characters. • Any Active Directory sites that you have deﬁned must meet the following prerequisites: • The subnets in the VPC that's associated with your ﬁle system must be deﬁned in an Active Directory site. Prerequisites 84 Amazon FSx for Windows File Server Windows User Guide • There are no conﬂicts between the VPC subnets and any of the Active Directory site subnets. Amazon FSx requires connectivity to the domain controllers or Active Directory sites you have deﬁned in your Active Directory environment. Amazon FSx will ignore any domain controllers
WindowsGuide-039	WindowsGuide.pdf	39	all Multi-AZ ﬁle systems, the domain name cannot exceed 47 characters. • Any Active Directory sites that you have deﬁned must meet the following prerequisites: • The subnets in the VPC that's associated with your ﬁle system must be deﬁned in an Active Directory site. Prerequisites 84 Amazon FSx for Windows File Server Windows User Guide • There are no conﬂicts between the VPC subnets and any of the Active Directory site subnets. Amazon FSx requires connectivity to the domain controllers or Active Directory sites you have deﬁned in your Active Directory environment. Amazon FSx will ignore any domain controllers with TCP and UDP blocked on port 389. For the remaining domain controllers in your Active Directory, ensure that they meet the Amazon FSx connectivity requirements. Additionally, verify that any changes to your service account are propagated to all these domain controllers. Important Do not move computer objects that Amazon FSx creates in the OU after your ﬁle system is created. Doing so will cause your ﬁle system to become misconﬁgured. You can validate your Active Directory conﬁguration, including testing connectivity of multiple domain controllers, using the Amazon FSx Active Directory Validation tool. To limit the number of domain controllers that require connectivity, you can also build a trust relationship between your on-premise domain controllers and AWS Managed Microsoft AD. For more information, see Using a resource forest isolation model. Important Amazon FSx only registers the DNS records for a ﬁle system if you are using Microsoft DNS as the default DNS service. If you are using a third-party DNS, you will need to manually set up DNS record entries for your ﬁle system after you create it. Network conﬁgurations This section describes the network conﬁguration requirements for joining a ﬁle system to your self- managed Active Directory. We strongly recommend that you use the Amazon FSx Active Directory validation tool to test your network settings before attempting to join your ﬁle system to your self- managed Active Directory. • Ensure that your ﬁrewall rules will allow ICMP traﬃc between your Active Directory domain controllers and Amazon FSx. Prerequisites 85 Amazon FSx for Windows File Server Windows User Guide • Connectivity must be conﬁgured between the Amazon VPC where you want to create the ﬁle system and your self-managed Active Directory. You can set up this connectivity using AWS Direct Connect, AWS Virtual Private Network, VPC peering, or AWS Transit Gateway. • The default VPC security group for your default Amazon VPC must be added to your ﬁle system using the Amazon FSx console. Ensure that the security group and the VPC Network ACLs for the subnets where you create your ﬁle system allow traﬃc on the ports and in the direction shown in the following diagram. The following table identiﬁes the protocol, ports, and its role. Protocol Ports Role TCP/UDP TCP/UDP TCP/UDP TCP/UDP 53 88 464 389 Domain Name System (DNS) Kerberos authentication Change/set password Lightweight Directory Access Protocol (LDAP) Prerequisites 86 Amazon FSx for Windows File Server Windows User Guide Protocol Ports Role UDP TCP TCP TCP TCP TCP TCP TCP 123 135 445 636 3268 3269 5985 9389 Network Time Protocol (NTP) Distributed Computing Environment/End Point Mapper (DCE/EPMAP) Directory Services SMB ﬁle sharing Lightweight Directory Access Protocol over TLS/SSL (LDAPS) Microsoft Global Catalog Microsoft Global Catalog over SSL WinRM 2.0 (Microsoft Windows Remote Management) Microsoft Active Directory DS Web Services, PowerShell Important Allowing outbound traﬃc on TCP port 9389 is required for Single-AZ 2 and Multi-AZ ﬁle system deployments. TCP 49152 - 65535 Ephemeral ports for RPC These traﬃc rules need to also be mirrored on the ﬁrewalls that apply to each of the Active Directory domain controllers, DNS servers, FSx clients, and FSx administrators. Note If you're using VPC network ACLs, you must also allow outbound traﬃc on dynamic ports (49152-65535) from your ﬁle system. Prerequisites 87 Amazon FSx for Windows File Server Windows User Guide Important While Amazon VPC security groups require ports to be opened only in the direction that network traﬃc is initiated, most Windows ﬁrewalls and VPC network ACLs require ports to be open in both directions. Service account permissions You need to have a service account in your self-managed Microsoft Active Directory with delegated permissions to join computer objects to your self-managed Active Directory domain. A service account is a user account in your self-managed Active Directory that has been delegated certain tasks. The following is the minimum set of permissions that must be delegated to the Amazon FSx service account in the OU that you're joining the ﬁle system to. • If using Delegate Control in the Active Directory User and Computers MMC: • Reset passwords • Read and write Account Restrictions • Validated write to DNS host name • Validated write to service principal name • If using Advanced
WindowsGuide-040	WindowsGuide.pdf	40	Directory with delegated permissions to join computer objects to your self-managed Active Directory domain. A service account is a user account in your self-managed Active Directory that has been delegated certain tasks. The following is the minimum set of permissions that must be delegated to the Amazon FSx service account in the OU that you're joining the ﬁle system to. • If using Delegate Control in the Active Directory User and Computers MMC: • Reset passwords • Read and write Account Restrictions • Validated write to DNS host name • Validated write to service principal name • If using Advanced Features in the Active Directory User and Computers MMC: • Modify permissions • Create computer objects • Delete computer objects For more information, see the Microsoft Windows Server documentation topic Error: Access is denied when non-administrator users who have been delegated control try to join computers to a domain controller. For more information about setting the required permissions, see Delegating permissions to the Amazon FSx service account or group. Prerequisites 88 Amazon FSx for Windows File Server Windows User Guide Best practices when using a self-managed Active Directory We recommend that you follow these best practices when joining an Amazon FSx for Windows File Server ﬁle systems to your self-managed Microsoft Active Directory. These best practices will help you in maintaining continuous, uninterrupted availability of your ﬁle system. Use a separate service account for Amazon FSx Use a separate service account to delegate the required privileges for Amazon FSx to fully manage ﬁle systems that are joined to your self-managed Active Directory. We do not recommend using the Domain Admins for this purpose. Use an Active Directory group Use an Active Directory group to manage Active Directory permissions and conﬁgurations associated with the Amazon FSx service account. Segregate the Organizational Unit (OU) To make it easier to ﬁnd and manage your Amazon FSx computer objects, we recommend that you segregate the Organizational Unit (OU) you use for your FSx for Windows File Server ﬁle systems from other domain controller concerns. Keep the Active Directory conﬁguration up-to-date It is imperative that you keep your ﬁle system's Active Directory conﬁguration up-to-date with any changes. For example, if your self-managed Active Directory uses a time-based password reset policy, as soon as the password is reset, make sure to update the service account password on your ﬁle system. For more information, see Updating a self-managed Active Directory conﬁguration. Changing the Amazon FSx service account If you update your ﬁle system with a new service account, it must have the required permissions and privileges to join your Active Directory and have Full control permissions for the existing computer objects associated with the ﬁle system. For more information, see Changing the Amazon FSx service account. Assign subnets to a single Microsoft Active Directory site If your Active Directory environment has a large number of domain controllers, use Active Directory Sites and Services to assign the subnets used by your Amazon FSx ﬁle systems to a Best practices when using a self-managed Active Directory 89 Amazon FSx for Windows File Server Windows User Guide single Active Directory site with the highest availability and reliability. Make sure that the VPC security group, VPC network ACL, Windows ﬁrewall rules on your DCs, and any other network routing controls you have in your Active Directory infrastructure allow communication from Amazon FSx on the required ports. This allows Windows to revert to other domain controllers if it can't use the assigned Active Directory site. For more information, see File system access control with Amazon VPC. Use security group rules to limit traﬃc Use security group rules to implement the principle of least privilege in your virtual private cloud (VPC). You can limiting the type of inbound and outbound network traﬃc allowed for your ﬁle using VPC security group rules. For example, we recommend only allowing outbound traﬃc to your self-managed Active Directory domains controllers or to within the subnet or security group you are using. For more information, see File system access control with Amazon VPC. Do not move computer objects created Amazon FSx Important Do not move computer objects that Amazon FSx creates in the OU after your ﬁle system is created. Doing so will cause your ﬁle system to become misconﬁgured. Validate your Active Directory conﬁguration Before attempting to join an FSx for Windows File Server ﬁle system to your Active Directory, we strongly recommend that you validate your Active Directory conﬁguration using the Amazon FSx Active Directory Validation tool. Amazon FSx service account Amazon FSx ﬁle systems that are joined to a self-managed Active Directory require a valid service account throughout their lifetime. Amazon FSx uses the service account to fully manage your ﬁle systems and perform administrative tasks that require unjoining and rejoining computer objects to your
WindowsGuide-041	WindowsGuide.pdf	41	is created. Doing so will cause your ﬁle system to become misconﬁgured. Validate your Active Directory conﬁguration Before attempting to join an FSx for Windows File Server ﬁle system to your Active Directory, we strongly recommend that you validate your Active Directory conﬁguration using the Amazon FSx Active Directory Validation tool. Amazon FSx service account Amazon FSx ﬁle systems that are joined to a self-managed Active Directory require a valid service account throughout their lifetime. Amazon FSx uses the service account to fully manage your ﬁle systems and perform administrative tasks that require unjoining and rejoining computer objects to your Active Directory domain. These tasks include replacing a failed ﬁle server and patching Microsoft Windows Server software. For Amazon FSx to perform these tasks, the Amazon FSx service account must have, at a minimum, the set of permissions that are described in Service account permissions delegated to it. Amazon FSx service account 90 Amazon FSx for Windows File Server Windows User Guide Although members of the Domain Admins group have suﬃcient privileges to perform these tasks, we strongly recommend that you use a separate service account to delegate the required privileges to Amazon FSx. For more information about how to delegate privileges using either the Delegate Control or Advanced Features features in the Active Directory User and Computers MMC snap-in, see Delegating permissions to the Amazon FSx service account or group. If you update your ﬁle system with a new service account, the new service account must have the required permissions and privileges to join your Active Directory and have Full control permissions for the existing computer objects associated with the ﬁle system. For more information, see Changing the Amazon FSx service account. Delegating permissions to the Amazon FSx service account or group The Amazon FSx service account or admin group must have the privileges necessary for it to join FSx for Windows File Server ﬁle systems to your self-managed Active Directory domain. To delegate these permissions, you can use either Delegate Control or Advanced Features in the Active Directory User and Computers MMC snap-in, as described in the following procedures. To assign permissions using Delegate Control To assign permissions to a service account or group using Delegate Control 1. Log in to your system as a domain administrator for your Active Directory domain. 2. Open the Active Directory User and Computers MMC snap-in. 3. 4. In the task pane, expand the domain node. Locate and open the context (right-click) menu for the OU that you want to modify, and then choose Delegate Control. 5. On the Delegation of Control Wizard page, choose Next. 6. Choose Add to add the name of your Amazon FSx service account or group, and then choose Next. 7. On the Tasks to Delegate page, choose Create a custom task to delegate, and then choose Next. 8. Choose Only the following objects in the folder, and then choose Computer objects. 9. Choose Create selected objects in this folder and Delete selected objects in this folder. Then choose Next. Delegating privileges to Amazon FSx 91 Amazon FSx for Windows File Server Windows User Guide 10. For Permissions, choose the following: • Reset Password • Read and write Account Restrictions • Validated write to DNS host name • Validated write to service principal name 11. Choose Next, and then choose Finish. 12. Close the Active Directory User and Computers MMC snap-in. To assign permissions using Advanced Features 1. Log in to your system as a domain administrator for your Active Directory domain. 2. Open the Active Directory User and Computers MMC snap-in. 3. 4. 5. 6. 7. Select View from the menu bar and ensure that Advanced Features is enabled (a check mark will appear next to it if the feature is enabled). In the task pane, expand the domain node. Locate and open (right-click) the context menu for the OU that you want to modify, and then choose Properties. In the OU Properties pane, select the Security tab. In the Security tab, select Advanced. Then select Add. 8. On the Permission Entry page, choose Select a principal and enter the name of your Amazon FSx service account or group. For Applies to:, choose This Object and all Descendant Computer. Ensure that the following are selected: • Modify permissions • Create Computer Objects • Delete Computer Objects 9. Select Apply, and then select OK. 10. Close the Active Directory User and Computers MMC snap-in. Validating your Active Directory conﬁguration Before you create an FSx for Windows File Server ﬁle system joined to your Active Directory, we recommend that you validate your Active Directory conﬁguration using the Amazon FSx Active Validating your Active Directory conﬁguration 92 Amazon FSx for Windows File Server Windows User Guide Directory Validation tool. Note that outbound internet connectivity is required to successfully validate
WindowsGuide-042	WindowsGuide.pdf	42	all Descendant Computer. Ensure that the following are selected: • Modify permissions • Create Computer Objects • Delete Computer Objects 9. Select Apply, and then select OK. 10. Close the Active Directory User and Computers MMC snap-in. Validating your Active Directory conﬁguration Before you create an FSx for Windows File Server ﬁle system joined to your Active Directory, we recommend that you validate your Active Directory conﬁguration using the Amazon FSx Active Validating your Active Directory conﬁguration 92 Amazon FSx for Windows File Server Windows User Guide Directory Validation tool. Note that outbound internet connectivity is required to successfully validate the Active Directory conﬁguration. To validate your Active Directory conﬁguration 1. Launch an Amazon EC2 Windows instance in the same subnet and with the same Amazon VPC security groups that you use for your FSx for Windows File Server ﬁle system. Ensure that your EC2 instance has the required AmazonEC2ReadOnlyAccess IAM permissions. You can validate EC2 instance role permissions using the IAM policy simulator. For more information, see Testing IAM Policies with the IAM Policy Simulator in the IAM User Guide. 2. Join your EC2 Windows instance to your Active Directory. For more information, see Manually Join a Windows Instance in the AWS Directory Service Administration Guide. 3. Connect to your EC2 instance. For more information, see Connecting to Your Windows Instance in the Amazon EC2 User Guide. 4. Open a Windows PowerShell window (using Run as Administrator) on the EC2 instance. To test whether the required Active Directory module for Windows PowerShell is installed, use the following test command. PS C:\> Import-Module ActiveDirectory If above returns an error, install it using the following command. PS C:\> Install-WindowsFeature RSAT-AD-PowerShell 5. Download the network validation tool using the following command. PS C:\> Invoke-WebRequest "https://docs.aws.amazon.com/fsx/latest/WindowsGuide/ samples/AmazonFSxADValidation.zip" -OutFile "AmazonFSxADValidation.zip" 6. Expand the zip ﬁle by using the following command. PS C:\> Expand-Archive -Path "AmazonFSxADValidation.zip" 7. Add the AmazonFSxADValidation module to the current session. Validating your Active Directory conﬁguration 93 Amazon FSx for Windows File Server Windows User Guide PS C:\> Import-Module .\AmazonFSxADValidation 8. Set required parameters by substituting into the following command your: • Active Directory domain name (DOMAINNAME.COM) • Prepare the $Credential object for the service account password using one of the following options. • To generate the credential object interactively, use the following command. $Credential = Get-Credential • To generate the credential object using an AWS Secrets Manager resource, use the following command. $Secret = ConvertFrom-Json -InputObject (Get-SECSecretValue -SecretId $AdminSecret).SecretString $Credential = (New-Object PSCredential($Secret.UserName,(ConvertTo-SecureString $Secret.Password -AsPlainText -Force))) • DNS server IP addresses (IP_ADDRESS_1, IP_ADDRESS_2) • Subnet ID(s) for subnets where you plan to create your Amazon FSx ﬁle system (SUBNET_1, SUBNET_2, for example, subnet-04431191671ac0d19). PS C:\> $FSxADValidationArgs = @{ # DNS root of ActiveDirectory domain DomainDNSRoot = 'DOMAINNAME.COM' # IP v4 addresses of DNS servers DnsIpAddresses = @('IP_ADDRESS_1', 'IP_ADDRESS_2') # Subnet IDs for Amazon FSx file server(s) SubnetIds = @('SUBNET_1', 'SUBNET_2') Credential = $Credential } Validating your Active Directory conﬁguration 94 Amazon FSx for Windows File Server Windows User Guide 9. (Optional) Set Organizational Unit, Delegated Administrators group, DomainControllersMaxCount, and enable service account permission validation by following instructions in the included README.md ﬁle prior to running the validation tool. Note The Domain Admins group has a diﬀerent name if the operating system is not in English. For example, the group is named Administrateurs du domaine in the French OS version. If you don't specify a value, the default Domain Admins group name is used and the ﬁle system creation fails. 10. Run the validation tool by using this command. PS C:\> $Result = Test-FSxADConfiguration @FSxADValidationArgs 11. The following is an example of a successful test result. Test 1 - Validate EC2 Subnets ... ... Test 17 - Validate 'Delete Computer Objects' permission ... Test computer object amznfsxtestd53f deleted! ... SUCCESS - All tests passed! Please proceed to creating an Amazon FSx file system. For your convenience, SelfManagedActiveDirectoryConfiguration of result can be used directly in CreateFileSystemWindowsConfiguration for New-FSXFileSystem PS C:\AmazonFSxADValidation> $Result.Failures.Count 0 PS C:\AmazonFSxADValidation> $Result.Warnings.Count 0 The following is an example of a test result with errors. Test 1 - Validate EC2 Subnets ... ... Test 7 - Validate that provided EC2 Subnets belong to a single AD Site ... Name DistinguishedName Site ---- ----------------- ---- Validating your Active Directory conﬁguration 95 Amazon FSx for Windows File Server Windows User Guide 10.0.0.0/19 CN=10.0.0.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=SiteB,CN=Sites,CN=Configu... 10.0.128.0/19 CN=10.0.128.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=Default-First-Site-Name,C... 10.0.64.0/19 CN=10.0.64.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=SiteB,CN=Sites,CN=Configu... Best match for EC2 subnet subnet-092f4caca69e360e7 is AD site CN=Default-First- Site-Name,CN=Sites,CN=Configuration,DC=te st-ad,DC=local Best match for EC2 subnet subnet-04431191671ac0d19 is AD site CN=SiteB,CN=Sites,CN=Configuration,DC=test-ad,DC=local WARNING: EC2 subnets subnet-092f4caca69e360e7 subnet-04431191671ac0d19 matched to different AD sites! Make sure they are in a single AD site. ... 9 of 16 tests skipped. FAILURE - Tests failed. Please see error details below: Name Value ---- ----- SubnetsInSeparateAdSites {subnet-04431191671ac0d19, subnet-092f4caca69e360e7} Please address all errors and warnings
WindowsGuide-043	WindowsGuide.pdf	43	Site ---- ----------------- ---- Validating your Active Directory conﬁguration 95 Amazon FSx for Windows File Server Windows User Guide 10.0.0.0/19 CN=10.0.0.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=SiteB,CN=Sites,CN=Configu... 10.0.128.0/19 CN=10.0.128.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=Default-First-Site-Name,C... 10.0.64.0/19 CN=10.0.64.0/19,CN=Subnets,CN=Sites,CN=Configuration,DC=test- ad,DC=local CN=SiteB,CN=Sites,CN=Configu... Best match for EC2 subnet subnet-092f4caca69e360e7 is AD site CN=Default-First- Site-Name,CN=Sites,CN=Configuration,DC=te st-ad,DC=local Best match for EC2 subnet subnet-04431191671ac0d19 is AD site CN=SiteB,CN=Sites,CN=Configuration,DC=test-ad,DC=local WARNING: EC2 subnets subnet-092f4caca69e360e7 subnet-04431191671ac0d19 matched to different AD sites! Make sure they are in a single AD site. ... 9 of 16 tests skipped. FAILURE - Tests failed. Please see error details below: Name Value ---- ----- SubnetsInSeparateAdSites {subnet-04431191671ac0d19, subnet-092f4caca69e360e7} Please address all errors and warnings above prior to re-running validation to confirm fix. PS C:\AmazonFSxADValidation> $Result.Failures.Count 1 PS C:\AmazonFSxADValidation> $Result.Failures Name Value ---- ----- SubnetsInSeparateAdSites {subnet-04431191671ac0d19, subnet-092f4caca69e360e7} PS C:\AmazonFSxADValidation> $Result.Warnings.Count 0 Validating your Active Directory conﬁguration 96 Amazon FSx for Windows File Server Windows User Guide If you receive warnings or errors when you run the validation tool, refer to the Troubleshooting guide included in the validation tool package (TROUBLESHOOTING.md) and Troubleshooting Amazon FSx. Joining an Amazon FSx ﬁle system to a self-managed Microsoft Active Directory domain When you create a new FSx for Windows File Server ﬁle system, you can conﬁgure Microsoft Active Directory integration so that it joins to your self-managed Microsoft Active Directory domain. To do this, provide the following information for your Microsoft Active Directory: • The fully qualiﬁed domain name (FQDN) of your on-premises Microsoft Active Directory directory. Note Amazon FSx currently does not support Single Label Domain (SLD) domains. • The IP addresses of the DNS servers for your domain. • Credentials for a service account in your on-premises Microsoft Active Directory domain. Amazon FSx uses these credentials to join to your self-managed Active Directory. Optionally, you can also specify the following: • A speciﬁc Organizational Unit (OU) within the domain that you want your Amazon FSx ﬁle system to join to. • The name of the domain group whose members are granted administrative privileges for the Amazon FSx ﬁle system. The domain group name you provide must be unique in your Active Directory. After you specify this information, Amazon FSx joins your new ﬁle system to your self-managed Active Directory domain using the service account that you provided. Join FSx to a self-managed Active Directory 97 Amazon FSx for Windows File Server Windows User Guide Important Amazon FSx only registers DNS records for a ﬁle system if the Active Directory domain that you are joining it to is using Microsoft DNS as the default DNS. If you are using a third-party DNS, you will need to manually setup DNS entries for your Amazon FSx ﬁle systems after you create your ﬁle system. For more information on choosing the correct IP addresses to use for the ﬁle system, see Getting the correct ﬁle system IP addresses to use for manual DNS entries. Before you begin Make sure that you have completed the Prerequisites detailed in Using a self-managed Microsoft Active Directory. To create an FSx for Windows File Server ﬁle system joined to a self-managed Active Directory (Console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. On the dashboard, choose Create ﬁle system to start the ﬁle system creation wizard. 3. Choose FSx for Windows File Server and then choose Next. The Create ﬁle system page appears. 4. Provide a name for your ﬁle system. You can use a maximum of 256 Unicode letters, white space, and numbers, plus the special characters + - = . _ : / 5. For Storage capacity, enter the storage capacity of your ﬁle system, in GiB. If you're using SSD storage, enter any whole number in the range of 32–65,536. If you're using HDD storage, enter any whole number in the range of 2,000–65,536. You can increase the amount of storage capacity as needed at any time after you create the ﬁle system. For more information, see Managing storage capacity. 6. Keep Throughput capacity at its default setting. Throughput capacity is the sustained speed at which the ﬁle server that hosts your ﬁle system can serve data. The Recommended throughput capacity setting is based on the amount of storage capacity you choose. If you need more than the recommended throughput capacity, choose Specify throughput capacity, and then choose a value. For more information, see FSx for Windows File Server performance. You can modify the throughput capacity as needed at any time after you create the ﬁle system. For more information, see Managing throughput capacity. Join FSx to a self-managed Active Directory 98 Amazon FSx for Windows File Server Windows User Guide 7. Choose the VPC that you want to associate with your ﬁle system. For the purposes of this getting started exercise, choose the same VPC as for your AWS Directory Service directory and Amazon EC2 instance. 8. Choose any value
WindowsGuide-044	WindowsGuide.pdf	44	choose Specify throughput capacity, and then choose a value. For more information, see FSx for Windows File Server performance. You can modify the throughput capacity as needed at any time after you create the ﬁle system. For more information, see Managing throughput capacity. Join FSx to a self-managed Active Directory 98 Amazon FSx for Windows File Server Windows User Guide 7. Choose the VPC that you want to associate with your ﬁle system. For the purposes of this getting started exercise, choose the same VPC as for your AWS Directory Service directory and Amazon EC2 instance. 8. Choose any value for Availability Zones and Subnet. 9. For VPC security groups, the default security group for your default Amazon VPC is already added to your ﬁle system in the console. Please ensure that the security group and the VPC Network ACLs for the subnet(s) where you're creating your FSx ﬁle system allow traﬃc on the ports and in the directions shown in the following diagram. The following table identiﬁes the role of each port. Protocol TCP/UDP Ports 53 Role Domain Name System (DNS) Join FSx to a self-managed Active Directory 99 Amazon FSx for Windows File Server Windows User Guide Protocol TCP/UDP Ports 88 TCP/UDP 464 TCP/UDP 389 UDP TCP 123 135 Role Kerberos authentic ation Change/ Se t password Lightweig ht Directory Access Protocol (LDAP) Network Time Protocol (NTP) Distribut ed Computing Environme nt / End Point Mapper (DCE / EPMAP) Join FSx to a self-managed Active Directory 100 Amazon FSx for Windows File Server Windows User Guide Protocol TCP Ports 445 TCP 636 TCP TCP 3268 3269 TCP 5985 Role Directory Services SMB ﬁle sharing Lightweig ht Directory Access Protocol over TLS/ SSL (LDAPS) Microsoft Global Catalog Microsoft Global Catalog over SSL WinRM 2.0 (Microsof t Windows Remote Managemen t) Join FSx to a self-managed Active Directory 101 Role Microsoft Active Directory DS Web Services, PowerShel l Ephemeral ports for RPC Amazon FSx for Windows File Server Windows User Guide Protocol TCP Ports 9389 TCP 49152 - 65535 Important Allowing outbound traﬃc on TCP port 9389 is required for Single-AZ 2 and all Multi- AZ ﬁle system deployments. Note If you're using VPC network ACLs, you must also allow outbound traﬃc on dynamic ports (49152-65535) from your FSx ﬁle system. • Outbound rules to allow all traﬃc to the IP addresses associated with the DNS servers and domain controllers for your self-managed Microsoft Active Directory domain. For more information, see Microsoft's documentation on conﬁguring your ﬁrewall for Active Directory communication. • Ensure that these traﬃc rules are also mirrored on the ﬁrewalls that apply to each of the Active Directory domain controllers, DNS servers, FSx clients and FSx administrators. Join FSx to a self-managed Active Directory 102 Amazon FSx for Windows File Server Windows User Guide Note If you have Active Directory sites deﬁned, you must ensure that the subnet(s) in the VPC associated with your Amazon FSx ﬁle system are deﬁned in an Active Directory site, and that no conﬂicts exist between the subnet(s) in your VPC and the subnets in your other sites. You can view and change these settings using the Active Directory Sites and Services MMC snap-in. Important While Amazon VPC security groups require ports to be opened only in the direction that network traﬃc is initiated, most Windows ﬁrewalls and VPC network ACLs require ports to be open in both directions. 10. For Windows authentication, choose Self-managed Microsoft Active Directory. 11. Enter a value for Fully qualiﬁed domain name for the self-managed Microsoft Active Directory directory. Note Domain name must not be in the Single Label Domain (SLD) format. Amazon FSx currently does not support SLD domains. Important For Single-AZ 2 and all Multi-AZ ﬁle systems, the Active Directory domain name cannot exceed 47 characters. 12. Enter a value for Organizational Unit for the self-managed Microsoft Active Directory directory. Join FSx to a self-managed Active Directory 103 Amazon FSx for Windows File Server Windows User Guide Note Ensure that the service account you provided has permissions delegated to the OU that you specify here or to the default OU if you don’t specify one. 13. Enter at least one, and no more than two, values for DNS Server IP Addresses for the self- managed Microsoft Active Directory directory. 14. Enter a string value for Service account username for the account on your self-managed Active Directory domain, such as ServiceAcct. Amazon FSx uses this user name to join to your Microsoft Active Directory domain. Important DO NOT include a domain preﬁx (corp.com\ServiceAcct) or domain suﬃx ([email protected]) when entering the Service account username. DO NOT use the Distinguished Name (DN) when entering the Service account username (CN=ServiceAcct,OU=example,DC=corp,DC=com). 15. Enter a value for Service account password for the account on your self-managed Active Directory domain. Amazon FSx
WindowsGuide-045	WindowsGuide.pdf	45	values for DNS Server IP Addresses for the self- managed Microsoft Active Directory directory. 14. Enter a string value for Service account username for the account on your self-managed Active Directory domain, such as ServiceAcct. Amazon FSx uses this user name to join to your Microsoft Active Directory domain. Important DO NOT include a domain preﬁx (corp.com\ServiceAcct) or domain suﬃx ([email protected]) when entering the Service account username. DO NOT use the Distinguished Name (DN) when entering the Service account username (CN=ServiceAcct,OU=example,DC=corp,DC=com). 15. Enter a value for Service account password for the account on your self-managed Active Directory domain. Amazon FSx uses this password to join to your Microsoft Active Directory domain. 16. Re-enter the password to conﬁrm it in Conﬁrm password. 17. For Delegated ﬁle system administrators group, specify the Domain Admins group or a custom delegated ﬁle system administrators group (if you've created one). The group you specify should have the delegated authority to perform administrative tasks on your ﬁle system. If you don't provide a value, Amazon FSx uses the Builtin Domain Admins group. Note that Amazon FSx does not support having a Delegated file system administrators group (either the Domain Admins group or a custom group you specify) that is located in the Builtin container. Important If you do not provide a Delegated ﬁle system administrators group, by default Amazon FSx attempts to use the Builtin Domain Admins group in your Active Directory domain. If the name of this Builtin group has been changed or if you’re using Join FSx to a self-managed Active Directory 104 Amazon FSx for Windows File Server Windows User Guide a diﬀerent group for domain administration, you must provide that name for the group here. Important DO NOT include a domain preﬁx (corp.com\FSxAdmins) or domain suﬃx ([email protected]) when providing the group name parameter. DO NOT use the Distinguished Name (DN) for the group. An example of a distinguished name is CN=FSxAdmins,OU=example,DC=corp,DC=com. To create an FSx for Windows File Server ﬁle system joined to a self-managed Active Directory (AWS CLI) The following example creates an FSx for Windows File Server ﬁle system with a SelfManagedActiveDirectoryConfiguration in the us-east-2 Availability Zone. aws fsx --region us-east-2 \ create-file-system \ --file-system-type WINDOWS \ --storage-capacity 300 \ --security-group-ids security-group-id \ --subnet-ids subnet-id\ --windows-configuration SelfManagedActiveDirectoryConfiguration='{DomainName="corp.example.com", \ OrganizationalUnitDistinguishedName="OU=FileSystems,DC=corp,DC=example,DC=com",FileSystemAdministratorsGroup="FSxAdmins", \ UserName="FSxService",Password="password", \ DnsIps=["10.0.1.18"]}',ThroughputCapacity=8 Important Do not move computer objects that Amazon FSx creates in the OU after your ﬁle system is created. Doing so will cause your ﬁle system to become misconﬁgured. Join FSx to a self-managed Active Directory 105 Amazon FSx for Windows File Server Windows User Guide Getting the correct ﬁle system IP addresses to use for manual DNS entries Amazon FSx only registers DNS records for a ﬁle system if you are using Microsoft DNS as the default DNS service. If you are using a third-party DNS, you will need to manually setup DNS entries for your Amazon FSx ﬁle systems. This section describes how to obtain the correct ﬁle system IP addresses to use if you have to manually add the ﬁle system to your DNS. Note that once a ﬁle system is created, its IP addresses don't change until the ﬁle system is deleted. How to obtain ﬁle system IP addresses to use for DNS A entries 1. In the https://console.aws.amazon.com/fsx/, choose the ﬁle system that you want to obtain the IP address of to display the ﬁle system details page. 2. In the Network & security tab do one of the following: • For Single-AZ 1 ﬁle systems: • In the Subnet panel, choose the elastic network interface shown under Network interface to open the Network Interfaces page in the Amazon EC2 console. • The IP address for the Single-AZ 1 ﬁle system to use is shown in the Primary private IPv4 IP column. • For Single-AZ 2 or Multi-AZ ﬁle systems: • In the Preferred subnet panel, choose the elastic network interface shown under Network interface to open the Network Interfaces page in the Amazon EC2 console. • The IP address for the preferred subnet to use is shown in the Secondary private IPv4 IP column. • In the Amazon FSx Standby subnet panel, choose the elastic network interface shown under Network interface to open the Network Interfaces page in the Amazon EC2 console. • The IP address for the standby subnet to use is shown in the Secondary private IPv4 IP column. Note If you need to setup DNS entries for your Windows Remote PowerShell Endpoint for Single- AZ 2 or Multi-AZ ﬁle systems, you should use the Primary private IPv4 address for the Getting IP addresses for manual DNS entries 106 Amazon FSx for Windows File Server Windows User Guide elastic network interface for your Preferred subnet. For more information, see Using the Amazon FSx CLI for PowerShell. Updating a self-managed
WindowsGuide-046	WindowsGuide.pdf	46	to open the Network Interfaces page in the Amazon EC2 console. • The IP address for the standby subnet to use is shown in the Secondary private IPv4 IP column. Note If you need to setup DNS entries for your Windows Remote PowerShell Endpoint for Single- AZ 2 or Multi-AZ ﬁle systems, you should use the Primary private IPv4 address for the Getting IP addresses for manual DNS entries 106 Amazon FSx for Windows File Server Windows User Guide elastic network interface for your Preferred subnet. For more information, see Using the Amazon FSx CLI for PowerShell. Updating a self-managed Active Directory conﬁguration To help ensure continuous, uninterrupted availability of your Amazon FSx ﬁle system, you must update the ﬁle system's Active Directory conﬁguration when any of the following Active Directory properties change: • The DNS server IP addresses • The service account credentials of the self-managed Active Directory When you update the self-managed Active Directory conﬁguration for your Amazon FSx ﬁle system, your ﬁle system's state switches from Available to Updating while the update is applied. Verify that the state switches back to Available after the update has been applied – note that the update can take up to several minutes to complete. For more information, see Monitoring self- managed Active Directory updates. If there's an issue with the updated self-managed Active Directory conﬁguration, the ﬁle system state switches to Misconﬁgured. This state shows an error message and recommended corrective action beside the ﬁle system description in the console, API, and CLI. After taking the recommended corrective action, verify that your ﬁle system's state eventually changes to Available. Important If you update your ﬁle system with a new service account, ensure that the new service account has Full control permissions for the existing computer objects associated with the ﬁle system. For information about troubleshooting possible issues related to self-managed Active Directory conﬁgurations, see File system is in a misconﬁgured state. You can use the AWS Management Console, Amazon FSx API, or AWS CLI to update the service account username and password and the DNS server IP addresses of a ﬁle system's self-managed Update self-managed Active Directory 107 Amazon FSx for Windows File Server Windows User Guide Active Directory conﬁguration. You can track the progress of a self-managed Active Directory conﬁguration update at any time using the AWS Management Console, CLI, and API. For more information, see Monitoring self-managed Active Directory updates. To update the self-managed Active Directory conﬁguration (Console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. Navigate to File systems, and choose the Windows ﬁle system for which you want to update self-managed Active Directory conﬁguration. 3. In the Network & security tab, then choose Update for the DNS server IP addresses, or for the service account username, depending on which Active Directory properties you are updating. 4. Enter the new DNS server IP addresses, or the new service account credentials in the dialog that appears. 5. Choose Update to initiate the Active Directory conﬁguration update. You can monitor the update progress using the AWS Management Console or the AWS CLI. To update the self-managed Active Directory conﬁguration (CLI) • To update the self-managed Active Directory conﬁguration of an FSx for Windows File Server ﬁle system, use the AWS CLI command update-ﬁle-system. Set the following parameters: • --file-system-id to the ID of the ﬁle system you are updating. • UserName the new username for the self-managed Active Directory service account. • Password the new password for the self-managed Active Directory service account. • DnsIps the IP addresses for the self-managed Active Directory DNS servers. aws fsx update-file-system --file-system-id fs-0123456789abcdef0 \ --windows-configuration 'SelfManagedActiveDirectoryConfiguration={UserName=username,Password=password,\ DnsIps=[192.0.2.0,192.0.2.24]}' If the update action is successful, the service sends back an HTTP 200 response. The AdminstrativeActions object in the response describes the request and its status. Update self-managed Active Directory 108 Amazon FSx for Windows File Server Windows User Guide Changing the Amazon FSx service account If you update your ﬁle system with a new service account, the new service account must have the required permissions and privileges to join your Active Directory and has Full control permissions for the existing computer objects associated with the ﬁle system. In addition, make sure that new service account is part of the trusted accounts with the enabled Group Policy setting Domain controller: Allow computer account re-use during domain join. We strongly recommend using an Active Directory group to manage Active Directory permissions and conﬁgurations associated with service accounts. When changing the service account for Amazon FSx, ensure that the service accounts have the following settings: • The new service account (or the Active Directory group it is a member of) has Full control permissions for the existing computer objects associated with the ﬁle system. • The new and previous service accounts (or the Active Directory group
WindowsGuide-047	WindowsGuide.pdf	47	service account is part of the trusted accounts with the enabled Group Policy setting Domain controller: Allow computer account re-use during domain join. We strongly recommend using an Active Directory group to manage Active Directory permissions and conﬁgurations associated with service accounts. When changing the service account for Amazon FSx, ensure that the service accounts have the following settings: • The new service account (or the Active Directory group it is a member of) has Full control permissions for the existing computer objects associated with the ﬁle system. • The new and previous service accounts (or the Active Directory group they are a member of) are part of the trusted accounts (or trusted Active Directory group) with the Domain controller: Allow computer account re-use during domain join Group Policy setting enabled on all domain controllers in the Active Directory. If the service accounts do not meet these requirements, the following conditions could occur: • For Single-AZ ﬁle systems, the ﬁle system could become MISCONFIGURED_UNAVAILABLE. • For Multi-AZ ﬁle systems, the ﬁle system could become MISCONFIGURED and the RemotePowerShell endpoint name might change. Conﬁguring a domain controller's Group Policy The following Microsoft recommended procedure describes how to use the domain controller Group Policy to conﬁgure the allow list policy. To conﬁgure a domain controller's allow list policy 1. Install the September 12, 2023 or later Microsoft Windows updates on all member computers and domain controllers in your self-managed Microsoft Active Directory. 2. In a new or existing group policy that applies to all domain controllers in your self-managed Active Directory, conﬁgure the following settings. Changing the Amazon FSx service account 109 Amazon FSx for Windows File Server Windows User Guide a. Navigate to Computer Conﬁguration>Policies>Windows Settings>Security Settings> Local Policies>Security Options. b. Double-click Domain controller: Allow computer account re-use during domain join. c. Select Deﬁne this policy setting and <Edit Security…>. d. Use the object picker to add users or groups of trusted computer account creators and owners to the Allow permission. (As a best practice, we highly recommend that you use groups for permissions.) Do not add the user account that performs the domain join. Warning Limit membership to the policy to trusted users and service accounts. Do not add authenticated users, everyone or other large groups to this policy. Instead, add speciﬁc trusted users and service accounts to groups and add those groups to the policy. 3. Wait for the Group Policy refresh interval or run gpupdate /force on all domain controllers. 4. Verify that the HKLM\System\CCS\Control\SAM – “ComputerAccountReuseAllowList” registry key is populated with the desired SDDL. Do not manually edit the registry. 5. Attempt to join a computer that has the September 12, 2023, or later updates installed. Ensure that one of the accounts listed in the policy owns the computer account. Also ensure that its registry does not have the NetJoinLegacyAccountReuse key enabled (set to 1). If the domain join fails, check the c:\windows\debug\netsetup.log. Monitoring self-managed Active Directory updates You can monitor the progress of a self-managed Active Directory conﬁguration update using the AWS Management Console, the API, or the AWS CLI, as described in the following procedures. When you update your ﬁle system's self-managed Active Directory conﬁguration, the ﬁle system's state switches from Available to Updating while the update is applied. Once the update is complete, the state switches back to Available. An Active Directory conﬁguration update can take up to several minutes to complete. Monitoring self-managed Active Directory updates 110 Amazon FSx for Windows File Server Windows User Guide Monitoring updates in the console In the Updates tab in the File system details window, you can view the 10 most recent updates for each update type. For self-managed Active Directory updates, you can view the following information. Update type Supported types are as follows: • DNS server IP address • Service account credentials Target value The desired value to update the ﬁle system property to. For Service account credentials updates, only the user name is shown, service account passwords are never included in this ﬁeld. Status The current status of the update. For self-managed Active Directory updates, the possible values are as follows: • Pending – Amazon FSx has received the update request, but has not started processing it. • In progress – Amazon FSx is processing the update request. • Completed – The ﬁle system update completed successfully. Monitoring self-managed Active Directory updates 111 Amazon FSx for Windows File Server Windows User Guide • Failed – The ﬁle system update failed. Choose the question mark (?) to see details about the failure. Progress % Displays the progress of the ﬁle system update as percent complete. Request time The time that Amazon FSx received the update action request. Monitoring updates using the AWS CLI and API You can view and monitor ﬁle system update requests that
WindowsGuide-048	WindowsGuide.pdf	48	started processing it. • In progress – Amazon FSx is processing the update request. • Completed – The ﬁle system update completed successfully. Monitoring self-managed Active Directory updates 111 Amazon FSx for Windows File Server Windows User Guide • Failed – The ﬁle system update failed. Choose the question mark (?) to see details about the failure. Progress % Displays the progress of the ﬁle system update as percent complete. Request time The time that Amazon FSx received the update action request. Monitoring updates using the AWS CLI and API You can view and monitor ﬁle system update requests that are in progress using the describe-ﬁle-systems AWS CLI command and the DescribeFileSystems API action. The AdministrativeActions array lists the 10 most recent update actions for each administrative action type. The following example shows an excerpt of the response of a describe-ﬁle-systems CLI command show two self-managed Active Directory ﬁle system updates. { "OwnerId": "111122223333", . . . "StorageCapacity": 1000, "AdministrativeActions": [ { "AdministrativeActionType": "FILE_SYSTEM_UPDATE", "RequestTime": 1581694766.757, "Status": "PENDING", "TargetFileSystemValues": { "WindowsConfiguration": { "SelfManagedActiveDirectoryConfiguration": { "UserName": "serviceUser", } } } }, { "AdministrativeActionType": "FILE_SYSTEM_UPDATE", Monitoring self-managed Active Directory updates 112 Amazon FSx for Windows File Server Windows User Guide "RequestTime": 1619032957.759, "Status": "FAILED", "TargetFileSystemValues": { "WindowsConfiguration": { "SelfManagedActiveDirectoryConfiguration": { "DnsIps": [ "10.0.138.161" ] } } }, "FailureDetails": { "Message": "Failure details message." } } ], . . . Monitoring self-managed Active Directory updates 113 Amazon FSx for Windows File Server Windows User Guide FSx for Windows File Server performance FSx for Windows File Server oﬀers ﬁle system conﬁguration options to meet a variety of performance needs. Following is an overview of Amazon FSx ﬁle system performance, with a discussion of the available performance conﬁguration options and useful performance tips. Topics • File system performance • Additional performance considerations • Impact of throughput capacity on performance • Choosing the right level of throughput capacity • Impact of storage conﬁguration on performance • Example: storage capacity and throughput capacity • Measuring performance using CloudWatch metrics • Troubleshooting ﬁle system performance issues File system performance Each FSx for Windows File Server ﬁle system consists of a Windows ﬁle server that clients communicate with and a set of storage volumes, or disks, attached to the ﬁle server. Each ﬁle server employs a fast, in-memory cache to enhance performance for the most frequently accessed data. The following diagram illustrates how data is accessed from an FSx for Windows File Server ﬁle system. File system performance 114 Amazon FSx for Windows File Server Windows User Guide When a client accesses data that is stored in the in-memory cache, the data is served directly to the requesting client as network I/O. The ﬁle server doesn't need to read it from or write it into the disk. The performance of this data access is determined by the network I/O limits and the size of the in-memory cache. When a client accesses data that is not in cache, the ﬁle server reads it from or writes it into the disk as disk I/O. The data is then served from the ﬁle server to the client as network I/O. The performance of this data access is determined by the network I/O limits as well as the disk I/O limits. Network I/O performance and ﬁle server in-memory cache are determined by a ﬁle sytem's throughput capacity. Disk I/O performance is determined by a combination of throughput capacity and storage conﬁguration. The maximum disk I/O performance, which consists of disk throughput and disk IOPS levels, that your ﬁle system can achieve is the lower of: • The disk I/O performance level provided by your ﬁle server, based on the throughput capacity you select for your ﬁle system. • The disk I/O performance level provided by your storage conﬁguration (the storage capacity, storage type, and SSD IOPS level you select for your ﬁle system). Additional performance considerations File system performance is typically measured by its latency, throughput, and I/O operations per second (IOPS). Additional performance considerations 115 Amazon FSx for Windows File Server Windows User Guide Latency FSx for Windows File Server ﬁle servers employ a fast, in-memory cache to achieve consistent sub- millisecond latencies for actively accessed data. For data that is not in the in-memory cache, that is, for ﬁle operations that need to be served by performing I/O on the underlying storage volumes, Amazon FSx provides sub-millisecond ﬁle operation latencies with solid state drive (SSD) storage, and single-digit millisecond latencies with hard disk drive (HDD) storage. Throughput and IOPS Amazon FSx ﬁle systems provide up to 2 GBps and 80,000 IOPS in all AWS Regions where Amazon FSx is available, and 12 GBps of throughput and 400,000 IOPS in US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Singapore). The speciﬁc amount
WindowsGuide-049	WindowsGuide.pdf	49	in the in-memory cache, that is, for ﬁle operations that need to be served by performing I/O on the underlying storage volumes, Amazon FSx provides sub-millisecond ﬁle operation latencies with solid state drive (SSD) storage, and single-digit millisecond latencies with hard disk drive (HDD) storage. Throughput and IOPS Amazon FSx ﬁle systems provide up to 2 GBps and 80,000 IOPS in all AWS Regions where Amazon FSx is available, and 12 GBps of throughput and 400,000 IOPS in US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Singapore). The speciﬁc amount of throughput and IOPS that your workload can drive on your ﬁle system depends on the throughput capacity, storage capacity and storage type of your ﬁle system, along with the nature of your workload, including the size of the active working set. Single-client performance With Amazon FSx, you can get up to the full throughput and IOPS levels for your ﬁle system from a single client accessing it. Amazon FSx supports SMB Multichannel. This feature enables it to provide up to multiple GBps throughput and hundreds of thousands of IOPS for a single client accessing your ﬁle system. SMB Multichannel uses multiple network connections between the client and server simultaneously to aggregate network bandwidth for maximal utilization. Although there's a theoretical limit to the number of SMB connections supported by Windows, this limit is in the millions, and practically you can have an unlimited number of SMB connections. Burst performance File-based workloads are typically spiky, characterized by short, intense periods of high I/O with plenty of idle time between bursts. To support spiky workloads, in addition to the baseline speeds that a ﬁle system can sustain 24/7, Amazon FSx provides the capability to burst to higher speeds for periods of time for both network I/O and disk I/O operations. Amazon FSx uses an I/O credit mechanism to allocate throughput and IOPS based on average utilization — ﬁle systems accrue credits when their throughput and IOPS usage is below their baseline limits, and can use these credits when they perform I/O operations. Latency 116 Amazon FSx for Windows File Server Windows User Guide Impact of throughput capacity on performance Throughput capacity determines ﬁle system performance in the following categories: • Network I/O – The speed at which the ﬁle server can serve ﬁle data to clients accessing it. • File server CPU and memory – Resources that are available for serving ﬁle data and performing background activities such as data deduplication and shadow copies. • Disk I/O – The speed at which the ﬁle server can support I/O between the ﬁle server and the storage volumes. The following tables provide details about the maximum levels of network I/O (throughput and IOPS) and disk I/O (throughput and IOPS) that you can drive with each provisioned throughput capacity conﬁguration, and the amount of memory available for caching and supporting background activities such as data deduplication and shadow copies. While you can select levels of throughput capacity below 32 megabytes per second (MBps) when you use the Amazon FSx API or CLI, keep in mind that these levels are meant for test and development workloads, not for production workloads. Note Note that throughput capacity levels of 4,608 MBps and higher are supported only in the following regions: US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (Ireland), Asia Paciﬁc (Tokyo), and Asia Paciﬁc (Singapore). Network I/O and memory FSx throughput capacity (MBps) Network throughput (MBps) Network IOPS Memory (GB) Baseline Burst (for a few minutes a day) 32 64 32 64 600 600 Thousands Tens of thousands 4 8 Throughput capacity & performance 117 Amazon FSx for Windows File Server Windows User Guide FSx throughput capacity (MBps) Network throughput (MBps) Network IOPS Memory (GB) 150 300 600 1,500 3,125 9,375 12,500 18,750 21,250 1,250 1,250 1,250 – – – – – – Hundreds of thousands Millions 8 16 32 72 144 192 256 384 512 128 256 512 1,024 2,048 4,608 6,144 9,216 12,288 Disk I/O FSx throughput capacity (MBps) Disk throughput (MBps) Disk IOPS Baseline Burst (for 30 mins a day) Baseline Burst (for 30 mins a day) 32 64 128 256 512 32 64 128 256 512 1,024 1,024 260 350 600 600 – – 2K 4K 6K 10K 20K 40K 12K 16K 20K 20K – – Throughput capacity & performance 118 Amazon FSx for Windows File Server Windows User Guide FSx throughput capacity (MBps) Disk throughput (MBps) Disk IOPS 2,048 4,608 6,144 9,216 12,288 2,048 4,608 6,144 9,2161 12,2881 – – – – – 80K 150K 200K 300K1 400K1 – – – – – Note 1If you have a Multi-AZ ﬁle system with a throughput capacity of 9,216 or 12,288 MBps, performance will be limited to 9,000 MBps and
WindowsGuide-050	WindowsGuide.pdf	50	256 512 32 64 128 256 512 1,024 1,024 260 350 600 600 – – 2K 4K 6K 10K 20K 40K 12K 16K 20K 20K – – Throughput capacity & performance 118 Amazon FSx for Windows File Server Windows User Guide FSx throughput capacity (MBps) Disk throughput (MBps) Disk IOPS 2,048 4,608 6,144 9,216 12,288 2,048 4,608 6,144 9,2161 12,2881 – – – – – 80K 150K 200K 300K1 400K1 – – – – – Note 1If you have a Multi-AZ ﬁle system with a throughput capacity of 9,216 or 12,288 MBps, performance will be limited to 9,000 MBps and 262,500 IOPS for write traﬃc only. Otherwise, for read traﬃc on all Multi-AZ ﬁle systems, read and write traﬃc on all Single- AZ ﬁle systems, and all other throughput capacity levels, your ﬁle system will support the performance limits shown in the table. Choosing the right level of throughput capacity When you create a ﬁle system using the Amazon Web Services Management Console, Amazon FSx automatically picks the recommended throughput capacity level for your ﬁle system based on the amount of storage capacity you conﬁgure. While the recommended throughput capacity should be suﬃcient for most workloads, you have the option to override the recommendation and conﬁgure a speciﬁc amount of throughput capacity to meet your workload's needs. For example, if your workload requires driving 1 GBps of traﬃc to your ﬁle system, you should select a throughput capacity of at least 1,024 MBps. The following table provides the minimum recommended throughput capacity level for a ﬁle system based on the amount of provisioned storage capacity. SSD storage capacity (GiB) HDD storage capacity (GiB) Minimum recommended throughput capacity (MBps) Up to 640 Up to 3,200 32 Choosing throughput capacity 119 Amazon FSx for Windows File Server Windows User Guide SSD storage capacity (GiB) HDD storage capacity (GiB) Minimum recommended throughput capacity (MBps) 641—1,280 3201—6,400 1281—2,560 6,401—12,800 2,561—5,120 12,801—25,600 5,121—10,240 25,601—51,200 10,241—20,480 >20,480 >51,200 NA 64 128 256 512 1,024 2,048 You should also consider the features you’re planning to enable on your ﬁle system in deciding the level of throughput to conﬁgure. For example, enabling Shadow Copies may require you to increase your throughput capacity to a level up to three times your expected workload to ensure the ﬁle server can maintain the shadow copies with the available I/O performance capacity. If you are enabling Data Deduplication, you should determine the amount of memory associated with your ﬁle system's throughput capacity and ensure this amount of memory is suﬃcient for the size of your data. You can adjust the amount of throughput capacity up or down at any time after you create it. For more information, see Managing throughput capacity. You can monitor your workload’s utilization of ﬁle server performance resources and get recommendations on which throughput capacity to select by viewing the Monitoring & performance > Performance tab of your Amazon FSx console. We recommend testing in a pre- production environment to ensure the conﬁguration you’ve selected meets your workload’s performance requirements. For Multi-AZ ﬁle systems, we also recommend testing the impact of the failover process that occurs during ﬁle system maintenance, throughput capacity changes, and unplanned service disruption on your workload, as well as ensuring that you have provisioned suﬃcient throughput capacity to prevent performance impact during these events. For more information, see Accessing ﬁle system metrics. Choosing throughput capacity 120 Amazon FSx for Windows File Server Windows User Guide Impact of storage conﬁguration on performance Your ﬁle system's storage capacity, storage type, and SSD IOPS level all impact the disk I/ O performance of your ﬁle system. You can conﬁgure these resources to deliver the desired performance levels for your workload. You can increase storage capacity and scale SSD IOPS at any time. For more information, see Managing storage capacity and Managing SSD IOPS. You can also upgrade your ﬁle system from HDD storage type to SSD storage type. For more information, see Managing your ﬁle system's storage type. Your ﬁle system provides the following default levels of disk throughput and IOPS: Storage type Disk throughput (MBps per TiB of storage) Disk IOPS (per TiB of storage) SSD HDD 750 3,0001 12 baseline; 80 burst (up to a max. of 1 GBps per ﬁle system) 12 baseline; 80 burst Note 1For ﬁle systems with SSD storage type, you can provision additional IOPS, up to a maximum ratio of 500 IOPS per GiB of storage and 400,000 IOPS per ﬁle system. HDD burst performance For HDD storage volumes, Amazon FSx uses a burst bucket model for performance. Volume size determines the baseline throughput of your volume, which is the rate at which the volume accumulates throughput credits. Volume size also determines the burst throughput of your volume, which is the rate at which you can spend credits when they
WindowsGuide-051	WindowsGuide.pdf	51	max. of 1 GBps per ﬁle system) 12 baseline; 80 burst Note 1For ﬁle systems with SSD storage type, you can provision additional IOPS, up to a maximum ratio of 500 IOPS per GiB of storage and 400,000 IOPS per ﬁle system. HDD burst performance For HDD storage volumes, Amazon FSx uses a burst bucket model for performance. Volume size determines the baseline throughput of your volume, which is the rate at which the volume accumulates throughput credits. Volume size also determines the burst throughput of your volume, which is the rate at which you can spend credits when they are available. Larger volumes have higher baseline and burst throughput. The more credits your volume has, the longer it can drive I/ O at the burst level. The available throughput of an HDD storage volume is expressed by the following formula: Storage conﬁguration & performance 121 Amazon FSx for Windows File Server Windows User Guide (Volume size) × (Credit accumulation rate per TiB) = Throughput For a 1-TiB HDD volume, burst throughput is limited to 80 MiBps, the bucket ﬁlls with credits at 12 MiBps, and it can hold up to 1 TiB-worth of credits. HDD storage volumes can experience signiﬁcant performance variations depending on the workload. Sudden spikes in IOPS or throughput can lead to disk performance degradation. The DiskThroughputBalance metric provides information about the burst credit balance for both disk throughput and disk IOPS utilization. For example, if your workload exceeds the baseline HDD IOPS limits (12 IOPS per TiB of storage), the Disk IOPS utilization (HDD) will be above 100% and result in depleting the burst credit balance, which you can see in the DiskThroughputBalance metric. In order for your workload to continue driving high levels of I/O, you may need to do one of the following: • Reduce the I/O demands for your workload so that the burst credit balance is replenished. • Increase the ﬁle system's storage capacity to provide higher baseline level of disk IOPS. • Upgrade the ﬁle system to use SSD storage, which provides a higher baseline level of disk IOPS to better match your workload’s requirements. Example: storage capacity and throughput capacity The following example illustrates how storage capacity and throughput capacity impact ﬁle system performance. A ﬁle system that is conﬁgured with 2 TiB of HDD storage capacity and 32 MBps of throughput capacity has the following throughput levels: • Network throughput – 32 MBps baseline and 600 MBps burst (see throughput capacity table) • Disk throughput – 24 MBps baseline and 160 MBps burst, which is the lower of: • the disk throughput levels of 32 MBps baseline and 260 MBps burst supported by the ﬁle server, based on the ﬁle system's throughput capacity • the disk throughput levels of 24 MBps baseline (12 MBps per TB * 2 TiB) and 160 MBps burst (80 MBps per TiB * 2 TiB) supported by the storage volumes, based on storage type and capacity Example: storage capacity and throughput capacity 122 Amazon FSx for Windows File Server Windows User Guide Your workload accessing the ﬁle system will therefore be able to drive up to 32 MBps baseline and 600 MBps burst throughput for ﬁle operations performed on actively accessed data cached in the ﬁle server in-memory cache, and up to 24 MBps baseline and 160 MBps burst throughput for ﬁle operations that need to go all the way to the disk, for example, due to cache misses. Measuring performance using CloudWatch metrics You can use Amazon CloudWatch to measure and monitor your ﬁle system's throughput and IOPS. For more information, see Monitoring with Amazon CloudWatch. Troubleshooting ﬁle system performance issues The performance of your FSx for Windows File Server ﬁle system depends on several factors, including the traﬃc that you drive to your ﬁle system, how you provision your ﬁle system, and the resources being consumed by features that are enabled, such as Data Deduplication or Shadow Copies. For information about understanding your ﬁle system’s performance, see FSx for Windows File Server performance. Topics • How do I determine the throughput and IOPS limits for my ﬁle system? • What is the diﬀerence between network I/O and disk I/O? Why is my network I/O diﬀerent from my disk I/O? • Why is my CPU or memory usage high, even when my network I/O is low? • What is bursting? How much bursting is my ﬁle system using? What happens when burst credits run out? • I see a warning on the Monitoring & performance page – do I need to change my ﬁle system’s conﬁguration? • My metrics were temporarily missing, should I be concerned? How do I determine the throughput and IOPS limits for my ﬁle system? To view a ﬁle system's throughput and IOPS limits, refer to the table
WindowsGuide-052	WindowsGuide.pdf	52	my network I/O diﬀerent from my disk I/O? • Why is my CPU or memory usage high, even when my network I/O is low? • What is bursting? How much bursting is my ﬁle system using? What happens when burst credits run out? • I see a warning on the Monitoring & performance page – do I need to change my ﬁle system’s conﬁguration? • My metrics were temporarily missing, should I be concerned? How do I determine the throughput and IOPS limits for my ﬁle system? To view a ﬁle system's throughput and IOPS limits, refer to the table showing performance levels based on the amount of provision throughput capacity. Measuring performance using CloudWatch metrics 123 Amazon FSx for Windows File Server Windows User Guide What is the diﬀerence between network I/O and disk I/O? Why is my network I/O diﬀerent from my disk I/O? Amazon FSx ﬁle systems include one or more ﬁle servers that serve data over the network to the clients accessing the ﬁle system. This is the network I/O. The ﬁle server has a fast, in-memory cache to enhance performance for the most frequently accessed data. The ﬁle servers also drives traﬃc to the storage volumes that host your ﬁle system data. This is the disk I/O. The following diagram illustrates network and disk I/O for an Amazon FSx ﬁle system. For more information, see Monitoring with Amazon CloudWatch. Why is my CPU or memory usage high, even when my network I/O is low? The ﬁle server CPU and memory usage depends not only on the network traﬃc you drive, but also the features you have enabled on your ﬁle system. How you conﬁgure and schedule these features can impact CPU and memory utilization. Data Deduplication jobs in progress can consume memory. You can modify the conﬁguration of deduplication jobs to reduce memory requirements. For example, you can constrain the optimization to run on speciﬁc ﬁle types or folders, or set a minimum ﬁle size and age for optimization. We also recommend conﬁguring deduplication jobs to run during idle periods when there is minimal load on your ﬁle system. For more information, see Reducing storage costs with Data Deduplication. If you have access-based enumeration enabled, you might see high CPU utilization when your end-users view or list ﬁle shares, or during the Optimization phase of a storage scaling job. For more information, see Enable access-based enumeration on a namespace in the Microsoft Storage Documentation. What is network I/O vs. disk I/O? Why are they diﬀerent? 124 Amazon FSx for Windows File Server Windows User Guide What is bursting? How much bursting is my ﬁle system using? What happens when burst credits run out? File-based workloads are typically spiky, characterized by short, intense periods of high I/O with idle time between bursts. To support these types of workloads, in addition to the baseline speeds that a ﬁle system can sustain, Amazon FSx provides the capability to burst to higher speeds for periods of time for both network I/O and disk I/O operations. Amazon FSx uses a I/O credit mechanism to allocate throughput and IOPS based on average utilization — ﬁle systems accrue credits when their throughput and IOPS usage is below their baseline limits, and can use these credits to burst above the baseline limits (up to the burst limits) when required. For more information about the burst limits and duration for your ﬁle system, see FSx for Windows File Server performance. I see a warning on the Monitoring & performance page – do I need to change my ﬁle system’s conﬁguration? The Monitoring & performance page includes warnings that indicate when recent workload demands have approached or exceeded resource limits determined by how you’ve conﬁgured your ﬁle system. This doesn’t necessarily mean you need to change your conﬁguration, though your ﬁle system might be under-provisioned for your workload if you don’t take the recommended action. If the workload that caused the warning was atypical and you do not expect it to continue, it may be safe to take no action and closely monitor your utilization going forward. However, if the workload that caused the warning is typical and you expect it to continue, or even intensify, we advise following the recommended action to increase ﬁle server performance (by increasing throughput capacity) or increase storage volume performance (by increasing storage capacity, or by switching from HDD to SSD storage). Note Certain ﬁle system events can consume disk I/O performance resources and potentially trigger performance warnings. For example: • The optimization phase of storage capacity scaling can generate increased disk throughput, as described in Storage capacity increases and ﬁle system performance • For Multi-AZ ﬁle systems, events such as throughput capacity scaling, hardware replacement, or Availability Zone disruption result in automatic failover and failback What is bursting?
WindowsGuide-053	WindowsGuide.pdf	53	intensify, we advise following the recommended action to increase ﬁle server performance (by increasing throughput capacity) or increase storage volume performance (by increasing storage capacity, or by switching from HDD to SSD storage). Note Certain ﬁle system events can consume disk I/O performance resources and potentially trigger performance warnings. For example: • The optimization phase of storage capacity scaling can generate increased disk throughput, as described in Storage capacity increases and ﬁle system performance • For Multi-AZ ﬁle systems, events such as throughput capacity scaling, hardware replacement, or Availability Zone disruption result in automatic failover and failback What is bursting? How much bursting is my ﬁle system using? What happens when burst credits run out? 125 Amazon FSx for Windows File Server Windows User Guide events. Any data changes that occur during this time need to be synchronized between the primary and secondary ﬁle servers, and Windows Server runs a data synchronization job that can consume disk I/O resources. For more information, see Managing throughput capacity. My metrics were temporarily missing, should I be concerned? Single-AZ ﬁle systems will experience unavailability during ﬁle system maintenance, infrastructure component replacement, and when an Availability Zone is unavailable. During these times, metrics will not be available. In a Multi-AZ deployment, Amazon FSx automatically provisions and maintains a standby ﬁle server in a diﬀerent Availability Zone. If there is ﬁle system maintenance or an unplanned service disruption, Amazon FSx automatically fails over to the secondary ﬁle server, allowing you to continue accessing your data without manual intervention. During the brief period in which your ﬁle system is failing over and failing back, metrics may be temporarily unavailable. My metrics were temporarily missing, should I be concerned? 126 Amazon FSx for Windows File Server Windows User Guide Administering FSx for Windows ﬁle systems Amazon FSx provides a wide range of administrative capabilities that help you easily manage and grow your Amazon FSx for Windows File Server ﬁle systems to meet changing workload and user requirements, and your organizations regulatory and compliance needs. The following is a list of some of the ﬁle system conﬁgurations that you can manage using the AWS Management Console, AWS CLI and API, the Amazon FSx CLI for remote management on PowerShell, and native Microsoft Windows Server graphical interfaces. • Storage capacity • Storage type • SSD IOPS • Throughput capacity • DNS aliases • Data deduplication • Shadow copies • Storage quotas • File access auditing • File shares The following sections provide information about the ﬁle system administrative features and setting that are available to you. We've included guidance to help you determine which options are best for your situation, and best practices where applicable. Topics • Amazon FSx ﬁle system status • Using the Amazon FSx CLI for PowerShell • Starting an Amazon FSx remote PowerShell session • One-time ﬁle system setup tasks using the Amazon FSx CLI for remote management on PowerShell • Troubleshooting access to the Amazon FSx CLI on PowerShell • File system maintenance window 127 Amazon FSx for Windows File Server Windows User Guide • Changing the weekly maintenance window • Managing DNS aliases • User sessions and open ﬁles • Managing storage on FSx for Windows File Server • Using DFS Namespaces • Managing throughput capacity • Tagging your Amazon FSx resources • Update a ﬁle system using the AWS CLI Amazon FSx ﬁle system status You can view the status of an Amazon FSx ﬁle system by using the Amazon FSx console, the AWS CLI command describe-ﬁle-systems, or the API operation DescribeFileSystems. File system status Description AVAILABLE CREATING DELETING UPDATING MISCONFIGURED MISCONFIGURED_UNAVAILABLE The ﬁle system is in a healthy state, and is reachable and available for use. Amazon FSx is creating a new ﬁle system. Amazon FSx is deleting an existing ﬁle system. The ﬁle system is undergoing a customer- initiated update. The ﬁle system is in an impaired state due to a change in your Active Directory environment. Your ﬁle system is either currently unavailab le or at risk of losing availability, and backups may not succeed. For information on restoring availability, see File system is in a misconﬁg ured state. The ﬁle system is currently unavailable due to a change in your Active Directory environme Amazon FSx ﬁle system status 128 Amazon FSx for Windows File Server Windows User Guide File system status Description FAILED nt. For information on restoring availability, see File system is in a misconﬁgured state. • When creating a new ﬁle system, Amazon FSx was unable to create the new ﬁle system. • The ﬁle system is unavailable. • The ﬁle system has failed and Amazon FSx can't recover it. • Amazon FSx is unable to create backups. Using the Amazon FSx CLI for PowerShell This chapter describes how to access the Amazon FSx CLI for
WindowsGuide-054	WindowsGuide.pdf	54	in your Active Directory environme Amazon FSx ﬁle system status 128 Amazon FSx for Windows File Server Windows User Guide File system status Description FAILED nt. For information on restoring availability, see File system is in a misconﬁgured state. • When creating a new ﬁle system, Amazon FSx was unable to create the new ﬁle system. • The ﬁle system is unavailable. • The ﬁle system has failed and Amazon FSx can't recover it. • Amazon FSx is unable to create backups. Using the Amazon FSx CLI for PowerShell This chapter describes how to access the Amazon FSx CLI for remote management on PowerShell to perform ﬁle system administrative tasks for FSx for Windows ﬁle systems. You can also use the Microsoft Windows–native graphical user interface (GUI) to perform some administrative tasks. The Amazon FSx CLI for remote management on PowerShell enables ﬁle system administration for users in the ﬁle system administrators group. To start a remote PowerShell session on your FSx for Windows File Server ﬁle system, you ﬁrst need to meet the following prerequisites: • Be able to connect to a Windows compute instance that has network connectivity with your FSx for Windows File Server ﬁle system. • Be logged into the Windows compute instance as a member of the ﬁle system administrators group. If you are using AWS Managed Microsoft AD, that is the AWS Delegated FSx Administrators group. If you are using a self-managed Microsoft Active Directory, that is the Domain Admins group or the custom group that you speciﬁed for administration when you created your ﬁle system. For more information, see Best practices when using a self-managed Active Directory. • Your ﬁle system's VPC security group inbound rules allow traﬃc on port 5985. The Amazon FSx CLI for remote management on PowerShell uses the following security features: • User credentials are authenticated using Kerberos authentication. Using the Amazon FSx CLI for PowerShell 129 Amazon FSx for Windows File Server Windows User Guide • Management session communications between the connected client and ﬁle system are encrypted using Kerberos. You have two options to run remote management CLI commands on your Amazon FSx ﬁle system: • You can establish a long-running Remote PowerShell session and run the commands inside the session. • You can use the Invoke-Command to run a single command or a single block of commands without establishing a long-running Remote PowerShell session. If you want to set and pass variables as parameters to the remote management command, you will need to use Invoke-Command. Note For Multi-AZ ﬁle systems, you can only use the Amazon FSx CLI for Remote Management while the ﬁle system is using its preferred ﬁle server. For more information, see Availability and durability: Single-AZ and Multi-AZ ﬁle systems. You need to use the ﬁle system's Windows Remote PowerShell Endpoint to access the Remote PowerShell. The remote administration endpoint has the format of amznfsxctlyaa1k.ActiveDirectory-DNS-name, for example, amznfsxctlyaa1k.corp.example.com. You can ﬁnd the endpoint name by using the AWS Management Console in the File system details page on the Network & security tab. Use the AWS CLI describe-file-systems command to view the RemoteAdministrationEndpoint property returned in the response. You can use the Get-Command cmdlet to retrieve information about the cmdlets, functions, and aliases available in PowerShell. For more information, see the Microsoft Get-Command documentation. You can also run Amazon FSx CLI for remote management CLI on PowerShell commands on your ﬁle system using the Invoke-Command cmdlet, using the following syntax: PS C:\Users\delegateadmin> Invoke-Command -ComputerName amznfsxctlyaa1k.corp.example.com -ConfigurationName FSxRemoteAdmin -scriptblock { fsx- command} Using the Amazon FSx CLI for PowerShell 130 Amazon FSx for Windows File Server Windows User Guide For instructions on how to start a long-lived Remote PowerShell session on your FSx for Windows File Server ﬁles system, see Starting an Amazon FSx remote PowerShell session Starting an Amazon FSx remote PowerShell session This topic provides instructions for starting a long-lived remote PowerShell session on your FSx for Windows File Server ﬁle server. To start a remote PowerShell session on your ﬁle system 1. Connect to a compute instance that has network connectivity with your ﬁle system as a user that is a member of the delegated FSx Administrators Group that you chose when you created the ﬁle system. 2. Open a Windows PowerShell window on the compute instance. 3. In the PowerShell, enter the following command to open a long-lived remote session on your Amazon FSx ﬁle system. Replace Remote-PowerShell-Endpoint with the Windows Remote PowerShell endpoint of ﬁle system that you want to administer. Use FsxRemoteAdmin as the session conﬁguration name. PS C:\Users\delegateadmin> enter-pssession -ComputerName Remote-PowerShell-Endpoint -ConfigurationName FsxRemoteAdmin [fs-0123456789abcdef0]: PS> If your instance is not part of the Amazon FSx Active Directory domain, you are prompted to enter user credentials in a pop-up. Enter the credentials of the user that is a member
WindowsGuide-055	WindowsGuide.pdf	55	you created the ﬁle system. 2. Open a Windows PowerShell window on the compute instance. 3. In the PowerShell, enter the following command to open a long-lived remote session on your Amazon FSx ﬁle system. Replace Remote-PowerShell-Endpoint with the Windows Remote PowerShell endpoint of ﬁle system that you want to administer. Use FsxRemoteAdmin as the session conﬁguration name. PS C:\Users\delegateadmin> enter-pssession -ComputerName Remote-PowerShell-Endpoint -ConfigurationName FsxRemoteAdmin [fs-0123456789abcdef0]: PS> If your instance is not part of the Amazon FSx Active Directory domain, you are prompted to enter user credentials in a pop-up. Enter the credentials of the user that is a member of the FSx Administrators Group. If your instance is joined to the domain, you will not be asked for credentials. Important The Windows Remote PowerShell endpoint might change if you are using self- managed Active Directory conﬁguration and change the service account without proper Active Directory Group Policy settings. For more information, see Changing the Amazon FSx service account for more details. Starting an Amazon FSx remote PowerShell session 131 Amazon FSx for Windows File Server Windows User Guide One-time ﬁle system setup tasks using the Amazon FSx CLI for remote management on PowerShell Use the following Amazon FSx CLI for Remote Management on PowerShell commands to quickly implement the ﬁle system administration tasks following our best practices. Managing storage consumption Use the following commands to manage your ﬁle system storage consumption. • To turn on data deduplication with the default schedule, run the following command. Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Enable-FsxDedup } Optionally, use the following command to get data deduplication operating on your ﬁles soon after a ﬁle is created, without requiring any minimum ﬁle age. Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Set-FSxDedupConfiguration -MinimumFileAgeDays 0 } For more information, see Reducing storage costs with Data Deduplication. • Use the following command to turn on user storage quotas in “Track” mode, which is for reporting purposes only and not for enforcement. $QuotaLimit = Quota limit in bytes $QuotaWarningLimit = Quota warning threshold in bytes Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Enable-FSxUserQuotas -Track -DefaultLimit $Using:QuotaLimit -DefaultWarningLimit $Using:QuotaWarningLimit } For more information, see Managing storage quotas. One-time ﬁle system setup tasks 132 Amazon FSx for Windows File Server Windows User Guide Turning on shadow copies to enable end-users to recover ﬁles and folders to previous versions Turn on shadow copies with the default schedule (weekdays 7 AM and 12 noon), as follows. Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Set-FsxShadowStorage -Default } Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Set-FsxShadowCopySchedule -Default -Confirm:$False} For more information, see Conﬁguring shadow copies to use the default storage and schedule. Enforcing encryption in transit The following command enforces encryption for clients connecting to your ﬁle system. Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Set-FsxSmbServerConfiguration -EncryptData $True - RejectUnencryptedAccess $True -Confirm:$False} You can close all open sessions and force clients currently connected to reconnect using encryption. Invoke-Command -ComputerName $FSxWindowsRemotePowerShellEndpoint -ConfigurationName FSxRemoteAdmin -ScriptBlock { Close-FSxSmbSession -Confirm:$False} For more information, see Managing encryption in transit and User sessions and open ﬁles. Troubleshooting access to the Amazon FSx CLI on PowerShell There are a number of potential causes for being unable to connect to your ﬁle system using Remote PowerShell, each with their own resolution, as follows. To ﬁrst ensure that you can connect successfully to the Windows Remote PowerShell Endpoint, you can also run a basic connectivity test. For example, you can run the test-netconnection endpoint -port 5985 command. Turning on shadow copies to enable end-users to recover ﬁles and folders to previous versions 133 Amazon FSx for Windows File Server Windows User Guide The ﬁle system's security group lacks the required inbound rules to allow a remote PowerShell connection The ﬁle system's security group must have an inbound rule that allows traﬃc on port 5985 in order to establish a Remote PowerShell session. For more information, see Amazon VPC Security Groups. You have an external trust conﬁgured between the AWS managed Microsoft Active Directory and your on-premises Active Directory In order to use the Amazon FSx Remote PowerShell with Kerberos authentication, you need to conﬁgure a local group policy on the client for forest search order. For more information, see the Microsoft documentation Conﬁgure Kerberos Forest Search Order (KFSO). A language localization error occurs when trying to initiate a remote PowerShell session You need to add the following -SessionOption to your command: -SessionOption (New- PSSessionOption -uiCulture "en-US") Following are two examples using -SessionOption when initiating a remote PowerShell session on your ﬁle system. PS C:\Users\delegateadmin> Invoke-Command -ComputerName Windows Remote PowerShell Endpoint -ConfigurationName FSxRemoteAdmin -scriptblock {fsx-command} -SessionOption (New-PSSessionOption -uiCulture "en-US") PS C:\Users\delegateadmin> Enter-Pssession -ComputerName Windows Remote PowerShell Endpoint -ConfigurationName FsxRemoteAdmin -SessionOption (New-PSSessionOption - uiCulture "en-US") File system maintenance window Amazon FSx for Windows File Server performs routine software patching for the Microsoft Windows Server
WindowsGuide-056	WindowsGuide.pdf	56	Conﬁgure Kerberos Forest Search Order (KFSO). A language localization error occurs when trying to initiate a remote PowerShell session You need to add the following -SessionOption to your command: -SessionOption (New- PSSessionOption -uiCulture "en-US") Following are two examples using -SessionOption when initiating a remote PowerShell session on your ﬁle system. PS C:\Users\delegateadmin> Invoke-Command -ComputerName Windows Remote PowerShell Endpoint -ConfigurationName FSxRemoteAdmin -scriptblock {fsx-command} -SessionOption (New-PSSessionOption -uiCulture "en-US") PS C:\Users\delegateadmin> Enter-Pssession -ComputerName Windows Remote PowerShell Endpoint -ConfigurationName FsxRemoteAdmin -SessionOption (New-PSSessionOption - uiCulture "en-US") File system maintenance window Amazon FSx for Windows File Server performs routine software patching for the Microsoft Windows Server software that it manages. The maintenance window speciﬁes the day of the week and the time of day when this maintenance process begins. You can specify the start period of the maintenance window during ﬁle system creation. If you do not specify one, a 30-minute default maintenance start window is assigned. The duration of the maintenance window depends on multiple factors, including the scope of the maintenance, and the process of synchronizing any ﬁle The ﬁle system's security group lacks the required inbound rules to allow a remote PowerShell connection 134 Amazon FSx for Windows File Server Windows User Guide read and write activity that occurs during maintenance between the primary and secondary servers for Multi-AZ ﬁle systems. For more information, see Failing over process. FSx for Windows File Server lets you adjust the start time of your maintenance window to accommodate your workload and operational requirements. You can move the start time of your maintenance window as frequently as required, provided that a maintenance window start time is scheduled at least once every 14 days. If a patch is released and you haven’t scheduled a maintenance window within 14 days, FSx for Windows File Server proceeds with maintenance on the ﬁle system to ensure its security and reliability. For more information about how to adjust the start time of your ﬁle system's maintenance window, see Changing the weekly maintenance window. While patching is in progress, expect your Single-AZ ﬁle systems to be unavailable, typically for less than 20 minutes. Multi-AZ ﬁle systems remain available and automatically fail over and fail back between the preferred and the standby ﬁle servers. For more information, see Failing over process. Because patching for Multi-AZ ﬁle systems involves failing over and failing back between the ﬁle servers, any ﬁle read and write activity occuring during this time must be synchronized between the preferred and the standby ﬁle servers. To reduce patching time, we recommend scheduling your maintenance window during idle periods when there's minimal load on your ﬁle system. Note To ensure data integrity during maintenance activity, Amazon FSx for Windows File Server completes any pending write operations to the underlying storage volumes hosting your ﬁle system before maintenance begins. Changing the weekly maintenance window FSx for Windows File Server lets you adjust when your ﬁle system's maintenance window starts to accommodate your workload and operational requirements. You can use the AWS Management Console, AWS CLI, and Amazon FSx API to change when the weekly maintenance window starts, described in the following procedure. To change the start time of the weekly maintenance window (console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. Choose File systems in the left hand navigation column. Changing the weekly maintenance window 135 Amazon FSx for Windows File Server Windows User Guide 3. Choose the ﬁle system that you want to change the weekly maintenance window for. The ﬁle system details page displays. 4. Choose Administration to display the ﬁle system administration Settings panel. 5. Choose Update to display the Change maintenance window window. 6. Enter the new day and time that you want the weekly maintenance window to start. 7. Choose Save to save your changes. The new maintenance start time is displayed in the Administration Settings panel. To change the start time of the weekly maintenance window using the update-ﬁle-system CLI command, see Update a ﬁle system using the AWS CLI. Managing DNS aliases In addition to the default Domain Name System (DNS) name that Amazon FSx provides, you can also associate DNS aliases of your choosing with your ﬁle systems. With DNS aliases, you can continue using existing DNS names to access data stored on Amazon FSx when migrating ﬁle system storage from on-premises to Amazon FSx, without needing to update any tools or applications. You can associate DNS aliases with new and existing FSx for Windows File Server ﬁle systems, and when you restore a backup to a new ﬁle system, using the AWS Management Console and AWS CLI. You can associate up to 50 DNS aliases with a ﬁle system at any one time. Note Support for DNS aliases is available on FSx for Windows File Server ﬁle systems created after 12:00 pm ET
WindowsGuide-057	WindowsGuide.pdf	57	using existing DNS names to access data stored on Amazon FSx when migrating ﬁle system storage from on-premises to Amazon FSx, without needing to update any tools or applications. You can associate DNS aliases with new and existing FSx for Windows File Server ﬁle systems, and when you restore a backup to a new ﬁle system, using the AWS Management Console and AWS CLI. You can associate up to 50 DNS aliases with a ﬁle system at any one time. Note Support for DNS aliases is available on FSx for Windows File Server ﬁle systems created after 12:00 pm ET on November 9, 2020. To use DNS aliases on a ﬁle system created before 12:00 pm ET on November 9, 2020, do the following: 1. Take a backup of the existing ﬁle system. For more information, see Working with user- initiated backups. 2. Restore the backup to a new ﬁle system. For more information, see Restoring backups to new ﬁle system. Once the new ﬁle system is available, you will be able to use DNS aliases to access it, using the information provided in this section. DNS aliases 136 Amazon FSx for Windows File Server Windows User Guide Note The information presented here assumes that you're working entirely within Active Directory and that you're not using external DNS providers. Third-party DNS providers may result in unexpected behavior. Amazon FSx only registers DNS records for a ﬁle system if the Active Directory domain that you are joining it to is using Microsoft DNS as the default DNS. If you are using a third-party DNS, you will need to manually set up DNS entries for your Amazon FSx ﬁle systems after you create your ﬁle system. For more information on choosing the correct IP addresses to use for the ﬁle system, see Getting the correct ﬁle system IP addresses to use for manual DNS entries. You can associate DNS aliases with existing FSx for Windows File Server ﬁle systems, when you create new ﬁle systems, and when you create a new ﬁle system from a backup. You can associate up to 50 DNS aliases with a ﬁle system at any one time. In addition to associating DNS aliases with your ﬁle system, for clients to connect to the ﬁle system using the DNS aliases, you also must do the following: • Conﬁgure service principal names (SPNs) for Kerberos authentication and encryption. • Conﬁgure a DNS CNAME record for the DNS alias that resolves to the default DNS name for your Amazon FSx ﬁle system. For more information, see Accessing data using DNS aliases. A DNS alias name for your FSx for Windows File Server ﬁle system needs to meet the following requirements: • Must be formatted as a fully qualiﬁed domain name (FQDN). • Can contain alphanumeric characters and hyphens (‐). • Cannot start or end with a hyphen. • Can start with a numeric. For DNS alias names, Amazon FSx stores alphabetic characters as lowercase letters (a-z), regardless of how you specify them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes. DNS aliases 137 Amazon FSx for Windows File Server Windows User Guide If you try to associate an alias that is already associated with the ﬁle system, it has no eﬀect. If you try to disassociate an alias from a ﬁle system that is not associated with the ﬁle system, Amazon FSx responds with a bad request error. Note When Amazon FSx adds or removes aliases on a ﬁle system, connected clients are temporarily disconnected and will automatically reconnect to the ﬁle system. Any ﬁles that were open by clients mapping a non-Continuously-Available (non-CA) share at the time of disconnection must be reopened by the client. Topics • DNS alias status • Using DNS aliases with Kerberos authentication • Viewing DNS aliases for ﬁle systems and backups • Associating DNS aliases with ﬁle systems • Managing DNS aliases on existing ﬁle systems DNS alias status DNS aliases can have one of the following status values: • Available – The DNS alias is associated with an Amazon FSx ﬁle system. • Creating – Amazon FSx is creating the DNS alias and associating it with the ﬁle system. • Deleting – Amazon FSx is disassociating the DNS alias from the ﬁle system and deleting it. • Failed to create – Amazon FSx was unable to associate the DNS alias with the ﬁle system. • Failed to delete – Amazon FSx was unable to disassociate the DNS alias from the ﬁle system. Using DNS aliases with Kerberos authentication We recommend that you use Kerberos-based authentication and encryption in transit with Amazon FSx. Kerberos provides the most secure authentication for clients accessing your ﬁle system. To enable Kerberos authentication for clients that access your Amazon FSx ﬁle system using a
WindowsGuide-058	WindowsGuide.pdf	58	• Deleting – Amazon FSx is disassociating the DNS alias from the ﬁle system and deleting it. • Failed to create – Amazon FSx was unable to associate the DNS alias with the ﬁle system. • Failed to delete – Amazon FSx was unable to disassociate the DNS alias from the ﬁle system. Using DNS aliases with Kerberos authentication We recommend that you use Kerberos-based authentication and encryption in transit with Amazon FSx. Kerberos provides the most secure authentication for clients accessing your ﬁle system. To enable Kerberos authentication for clients that access your Amazon FSx ﬁle system using a DNS DNS alias status 138 Amazon FSx for Windows File Server Windows User Guide alias, you must conﬁgure service principal names (SPNs) that correspond to the DNS alias on your ﬁle system’s Active Directory computer object. If you have SPNs conﬁgured for the DNS alias that you've assigned to another ﬁle system on a computer object in your Active Directory, you must ﬁrst remove those SPNs before adding SPNs to your ﬁle system’s computer object. For more information, see Conﬁgure service principal names (SPNs) for Kerberos. Viewing DNS aliases for ﬁle systems and backups You can view the DNS aliases currently associated with your FSx for Windows File Server ﬁle systems and backups using the AWS Management Console, the AWS CLI, and API, as described in the following procedures. To view DNS aliases associated with ﬁle systems • Using the console — Choose a ﬁle system to view the File systems detail page. Choose the Network & security tab to view the DNS aliases. • Using the CLI or API — Use the describe-file-system-aliases CLI command or the DescribeFileSystemAliases API operation. To view DNS aliases associated with backups • Using the console — In the navigation pane, choose Backups, and then choose the backup that you want to view. In the Summary pane, view the DNS aliases ﬁeld. • Using the CLI or API — Use the describe-backups CLI command or the DescribeBackups API operation. Associating DNS aliases with ﬁle systems You can associate DNS aliases when creating a new FSx for Windows File Server ﬁle system from scratch, or when restoring a backup to a new ﬁle system, using the AWS Management Console, AWS CLI, and API, described the following procedures. To associate DNS aliases when creating a new ﬁle system (console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. Viewing existing DNS aliases 139 Amazon FSx for Windows File Server Windows User Guide 2. Follow the procedure for creating a new ﬁle system described in Step 5. Create your ﬁle system in the Getting Started section. 3. In the Access - optional section of the Create ﬁle system wizard, enter the DNS aliases that you want to associate with your ﬁle system. 4. When the ﬁle system is Available, you can access it using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. To associate DNS aliases when creating a new Amazon FSx ﬁle system (CLI) 1. When creating a new ﬁle system, use the Alias property with the CreateFileSystem API operation to associate DNS aliases with the new ﬁle system. aws fsx create-file-system \ --file-system-type WINDOWS \ --storage-capacity 2000 \ --storage-type SSD \ --subnet-ids subnet-123456 \ --windows-configuration Aliases=[financials.corp.example.com,accts- rcv.corp.example.com] 2. When the ﬁle system is Available, you can access it using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. To add or remove DNS aliases when restoring a backup (CLI) 1. When creating a new ﬁle system from a backup of an existing ﬁle system, you can use the Aliases property with the CreateFileSystemFromBackup API operation as follows: Associating DNS aliases with ﬁle systems 140 Amazon FSx for Windows File Server Windows User Guide • Any aliases associated with the backup are associated with the new ﬁle system by default. • To create a ﬁle system without preserving any aliases from the backup, use the Aliases property with an empty set. To associate additional DNS aliases, use the Aliases property and include both the original aliases associated with the backup and the new aliases you want to associate. The following CLI command associates two aliases with the ﬁle system Amazon FSx is creating from a backup. aws fsx create-file-system-from-backup \ --backup-id backup-0123456789abcdef0 --storage-capacity 2000 \ --storage-type HDD \ --subnet-ids subnet-123456 \ --windows-configuration Aliases=[transactions.corp.example.com,accts- rcv.corp.example.com] 2. When the ﬁle system is Available, you can access it using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. Managing
WindowsGuide-059	WindowsGuide.pdf	59	use the Aliases property and include both the original aliases associated with the backup and the new aliases you want to associate. The following CLI command associates two aliases with the ﬁle system Amazon FSx is creating from a backup. aws fsx create-file-system-from-backup \ --backup-id backup-0123456789abcdef0 --storage-capacity 2000 \ --storage-type HDD \ --subnet-ids subnet-123456 \ --windows-configuration Aliases=[transactions.corp.example.com,accts- rcv.corp.example.com] 2. When the ﬁle system is Available, you can access it using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. Managing DNS aliases on existing ﬁle systems You can add and remove aliases on existing FSx for Windows File Server ﬁle systems using the AWS Management Console and AWS CLI, as described in the following procedures. To manage ﬁle system DNS aliases (console) 1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/. 2. Navigate to File systems, and choose the Windows ﬁle system that you want to manage DNS aliases for. 3. On the Network & security tab, choose Manage for DNS aliases to display the Manage DNS aliases window. • To associate DNS aliases – In the Associate new aliases box, enter the DNS aliases that you want to associate. Choose Associate. Managing DNS aliases on existing ﬁle systems 141 Amazon FSx for Windows File Server Windows User Guide • To disassociate DNS aliases – In the Current aliases list, choose the aliases to disassociate from. Choose Disassociate. You can monitor the status of the aliases you have managed in the Current aliases list. Refresh the list to update the status. It takes up to 2.5 minutes for an alias to be associated or disassociated with a ﬁle system. 4. When the alias is Available, you can access your ﬁle system using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. To associate DNS aliases with existing ﬁle systems (CLI) 1. Use the associate-file-system-aliases CLI command or the AssociateFileSystemAliases API operation to associate DNS aliases with an existing ﬁle system. The following CLI request associates two aliases with the speciﬁed ﬁle system. aws fsx associate-file-system-aliases \ --file-system-id fs-0123456789abcdef0 \ --aliases financials.corp.example.com transfers.corp.example.com The response shows the status of the aliases that Amazon FSx is associating with the ﬁle system. { "Aliases": [ { "Name": "financials.corp.example.com", "Lifecycle": CREATING }, { "Name": "transfers.corp.example.com", "Lifecycle": CREATING } ] } 2. Use the describe-file-system-aliases CLI command (DescribeFileSystemAliases is the equivalent API operation) to monitor the status of the aliases that you are associating. Managing DNS aliases on existing ﬁle systems 142 Amazon FSx for Windows File Server Windows User Guide 3. When the Lifecycle has a value of AVAILABLE (a process that can take up to 2.5 minutes), you can access your ﬁle system using the DNS alias by conﬁguring service principal names (SPNs) and updating or creating a DNS CNAME record for the alias. For more information, see Accessing data using DNS aliases. To disassociate DNS aliases from ﬁle systems (CLI) • Use the disassociate-file-system-aliases CLI command or the DisassociateFileSystemAliases API operation to disassociate DNS aliases from an existing ﬁle system. The following command disassociates one alias from a ﬁle system. aws fsx disassociate-file-system-aliases \ --file-system-id fs-0123456789abcdef0 \ --aliases financials.corp.example.com The response shows the status of the aliases that Amazon FSx is disassociating from the ﬁle system. { "Aliases": [ { "Name": "financials.corp.example.com", "Lifecycle": DELETING } ] } Use the describe-file-system-aliases CLI command (DescribeFileSystemAliases is the equivalent API operation) to monitor the status of the aliases. It takes up to 2.5 minutes for the alias to be deleted. User sessions and open ﬁles You can monitor connected user sessions and open ﬁles on your FSx for Windows File Server ﬁle system using the Shared Folders tool. The Shared Folders tool provides a central location to User sessions and open ﬁles 143 Amazon FSx for Windows File Server Windows User Guide monitor who is connected to the ﬁle system, along with what ﬁles are open and by whom. You can use this tool to do the following: • Restore access to locked ﬁles. • Disconnect a user session, which closes all ﬁles opened by that user. You can use the Windows-native Shared Folders GUI tool and the Amazon FSx CLI for remote management on PowerShell to manage user sessions and open ﬁles on your FSx for Windows File Server ﬁle system. Using the GUI to manage users and sessions The following procedures detail how you can manage user sessions and open ﬁles on your Amazon FSx ﬁle system using the Microsoft Windows shared folders tool. To launch the shared folders tool 1. Launch your Amazon EC2 instance and connect it to the Microsoft Active Directory

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.