# Use the EC2Config service to perform tasks during EC2 legacy Windows operating system instance launch EC2Config service **Note** EC2Config has reached the end of support. The operating system versions that it runs on are no longer supported by Microsoft. We strongly recommend that you upgrade to the latest launch agent. The latest launch agent for Windows Server 2022 and later operating system versions is [EC2Launch v2](ec2launch-v2.md), which replaces both EC2Config and EC2Launch, and comes pre-installed on AWS Windows Server 2022 and 2025 AMIs. You can also manually install and configure the agent on Windows Server 2016 and 2019. For more information, see [Install EC2Launch v2](ec2launch-v2-install.md). Windows AMIs for Windows Server versions prior to Windows Server 2016 include an optional service, the EC2Config service (`EC2Config.exe`). EC2Config starts when the instance boots and performs tasks during startup and each time you stop or start the instance. EC2Config can also perform tasks on demand. Some of these tasks are automatically enabled, while others must be enabled manually. Although optional, this service provides access to advanced features that aren't otherwise available. This service runs in the LocalSystem account. The EC2Config service runs Sysprep, a Microsoft tool that enables you to create a customized Windows AMI that can be reused. When EC2Config calls Sysprep, it uses the files in `%ProgramFiles%\Amazon\EC2ConfigService\Settings` to determine which operations to perform. You can edit these files indirectly using the **EC2 Service Properties** system dialog, or directly using an XML editor or a text editor. However, there are some advanced settings that aren't available in the **Ec2 Service Properties** system dialog, so you must edit those entries directly. If you create an AMI from an instance after updating its settings, the new settings are applied to any instance that's launched from the new AMI. For information about creating an AMI, see [Create an Amazon EBS-backed AMI](creating-an-ami-ebs.md). EC2Config uses settings files to control its operation. You can update these settings files using either a graphical tool or by directly editing XML files. The service binaries and additional files are contained in the `%ProgramFiles%\Amazon\EC2ConfigService` directory. **Topics** + [ ## EC2Config and AWS Systems Manager ](#ec2config-ssm) + [ ## EC2Config tasks ](#UsingConfig_Ovw) + [ ## EC2Config settings files ](#UsingConfigXML_WinAMI) + [ # Install the latest version of EC2Config ](UsingConfig_Install.md) + [ # Configure .NET proxy settings for the EC2Config service ](ec2config-proxy.md) + [ # Set EC2Config service properties from the system dialog on your EC2 Windows instance ](set-ec2config-service-properties.md) + [ # Troubleshoot issues with the EC2Config launch agent ](repair-ec2config.md) + [ # EC2Config version history ](ec2config-version-details.md) ## EC2Config and AWS Systems Manager The EC2Config service processes Systems Manager requests on instances created from AMIs for versions of Windows Server prior to Windows Server 2016 that were published before November 2016. Instances created from AMIs for versions of Windows Server prior to Windows Server 2016 that were published after November 2016 include the EC2Config service *and* SSM Agent. EC2Config performs all of the tasks described earlier, and SSM Agent processes requests for Systems Manager capabilities like Run Command and State Manager. You can use Run Command to upgrade your existing instances to use to the latest version of the EC2Config service and SSM Agent. For more information, see [Update SSM Agent using Run Command](https://docs.aws.amazon.com/systems-manager/latest/userguide/run-command-tutorial-update-software.html) in the *AWS Systems Manager User Guide*. ## EC2Config tasks EC2Config runs initial startup tasks when the instance is first started and then disables them. To run these tasks again, you must explicitly enable them prior to shutting down the instance, or by running Sysprep manually. These tasks are as follows: + Set a random, encrypted password for the administrator account. + Generate and install the host certificate used for Remote Desktop Connection. + Dynamically extend the operating system partition to include any unpartitioned space. + Execute the specified user data (and Cloud-Init, if it's installed). For more information about specifying user data, see [Run commands when you launch an EC2 instance with user data input](user-data.md). EC2Config performs the following tasks every time the instance starts: + Change the host name to match the private IP address in Hex notation (this task is disabled by default and must be enabled in order to run at instance start). + Configure the key management server (AWS KMS), check for Windows activation status, and activate Windows as necessary. + Mount all Amazon EBS volumes and instance store volumes, and map volume names to drive letters. + Write event log entries to the console to help with troubleshooting (this task is disabled by default and must be enabled in order to run at instance start). + Write to the console that Windows is ready. + Add a custom route to the primary network adapter to enable the following IP addresses when a single NIC or multiple NICs are attached: `169.254.169.250`, `169.254.169.251`, and `169.254.169.254`. These addresses are used by Windows Activation and when you access instance metadata. **Note** If the Windows OS is configured to use IPv4, these IPv4 link-local addresses can be used. If the Windows OS has the IPv4 network protocol stack disabled and uses IPv6 instead, add `[fd00:ec2::250]` in place of `169.254.169.250` and `169.254.169.251`. Then add `[fd00:ec2::254]` in place of `169.254.169.254`. EC2Config performs the following task every time a user logs in: + Display wallpaper information to the desktop background. While the instance is running, you can request that EC2Config perform the following task on demand: + Run Sysprep and shut down the instance so that you can create an AMI from it. For more information, see [Create an Amazon EC2 AMI using Windows Sysprep](ami-create-win-sysprep.md). ## EC2Config settings files The settings files control the operation of the EC2Config service. These files are located in the `C:\Program Files\Amazon\Ec2ConfigService\Settings` directory: + `ActivationSettings.xml`—Controls product activation using a key management server (AWS KMS). + `AWS.EC2.Windows.CloudWatch.json`—Controls which performance counters to send to CloudWatch and which logs to send to CloudWatch Logs. + `BundleConfig.xml`—Controls how EC2Config prepares an instance store-backed instance for AMI creation. + `Config.xml`—Controls the primary settings. + `DriveLetterConfig.xml`—Controls drive letter mappings. + `EventLogConfig.xml`—Controls the event log information that's displayed on the console while the instance is booting. + `WallpaperSettings.xml`—Controls the information that's displayed on the desktop background. **ActivationSettings.xml** This file contains settings that control product activation. When Windows boots, the EC2Config service checks whether Windows is already activated. If Windows is not already activated, it attempts to activate Windows by searching for the specified AWS KMS server. + `SetAutodiscover`—Indicates whether to detect a AWS KMS automatically. + `TargetKMSServer`—Stores the private IP address of a AWS KMS. The AWS KMS must be in the same Region as your instance. + `DiscoverFromZone`—Discovers the AWS KMS server from the specified DNS zone. + `ReadFromUserData`—Gets the AWS KMS server from UserData. + `LegacySearchZones`—Discovers the AWS KMS server from the specified DNS zone. + `DoActivate`—Attempts activation using the specified settings in the section. This value can be `true` or `false`. + `LogResultToConsole`—Displays the result to the console. **BundleConfig.xml** This file contains settings that control how EC2Config prepares an instance for AMI creation. + `AutoSysprep`—Indicates whether to use Sysprep automatically. Change the value to `Yes` to use Sysprep. + `SetRDPCertificate`—Sets a self-signed certificate to the Remote Desktop server. This enables you to securely RDP into the instances. Change the value to `Yes` if the new instances should have the certificate. This setting is not used for instances with operating system versions prior to Windows Server 2016, because they can generate their own certificates. + `SetPasswordAfterSysprep`—Sets a random password on a newly launched instance, encrypts it with the user launch key, and outputs the encrypted password to the console. Change the value of this setting to `No` if the new instances should not be set to a random encrypted password. **Config.xml** *Plug-ins* + `Ec2SetPassword`—Generates a random encrypted password each time you launch an instance. This feature is disabled by default after the first launch so that reboots of this instance don't change a password set by the user. Change this setting to `Enabled` to continue to generate passwords each time you launch an instance. This setting is important if you are planning to create an AMI from your instance. + `Ec2SetComputerName`—Sets the host name of the instance to a unique name based on the IP address of the instance and reboots the instance. To set your own host name, or prevent your existing host name from being modified, you must disable this setting. + `Ec2InitializeDrives`—Initializes and formats all volumes during startup. This feature is enabled by default. + `Ec2EventLog`—Displays event log entries in the console. By default, the three most recent error entries from the system event log are displayed. To specify the event log entries to display, edit the `EventLogConfig.xml` file located in the `EC2ConfigService\Settings` directory. For information about the settings in this file, see [Eventlog Key](https://learn.microsoft.com/en-us/windows/win32/eventlog/eventlog-key). + `Ec2ConfigureRDP`—Sets up a self-signed certificate on the instance, so users can securely access the instance using Remote Desktop. This setting is not used for instances with operating system versions prior to Windows Server 2016, because they can generate their own certificates. + `Ec2OutputRDPCert`—Displays the Remote Desktop certificate information to the console so that the user can verify it against the thumbprint. + `Ec2SetDriveLetter`—Sets the drive letters of the mounted volumes based on user-defined settings. By default, when an Amazon EBS volume is attached to an instance, it can be mounted using the drive letter on the instance. To specify your drive letter mappings, edit the `DriveLetterConfig.xml` file located in the `EC2ConfigService\Settings` directory. + `Ec2WindowsActivate`—The plug-in handles Windows activation. It checks to see if Windows is activated. If not, it updates the AWS KMS client settings, and then activates Windows. To modify the AWS KMS settings, edit the `ActivationSettings.xml` file located in the `EC2ConfigService\Settings` directory. + `Ec2DynamicBootVolumeSize`—Extends Disk 0/Volume 0 to include any unpartitioned space. + `Ec2HandleUserData`—Creates and runs scripts created by the user on the first launch of an instance after Sysprep is run. Commands wrapped in script tags are saved to a batch file, and commands wrapped in PowerShell tags are saved to a .ps1 file (corresponds to the User Data checkbox on the Ec2 Service Properties system dialog). + `Ec2ElasticGpuSetup`—Installs the Elastic GPU software package if the instance is associated with an elastic GPU. + `Ec2FeatureLogging`—Sends Windows feature installation and corresponding service status to the console. Supported only for the Microsoft Hyper-V feature and corresponding vmms service. *Global Settings* + `ManageShutdown`—Ensures that instances launched from Amazon S3-backed AMIs do not terminate while running Sysprep. + `SetDnsSuffixList`—Sets the DNS suffix of the network adapter for Amazon EC2. This allows DNS resolution of servers running in Amazon EC2 without providing the fully qualified domain name. **Note** This adds a DNS suffix lookup for the following domain and configures other standard suffixes. For more information about how launch agents set DNS suffixes, see [Configure DNS Suffix for EC2 Windows launch agents](launch-agents-set-dns.md). ``` region.ec2-utilities.amazonaws.com ``` + `WaitForMetaDataAvailable`—Ensures that the EC2Config service will wait for metadata to be accessible and the network available before continuing with the boot. This check ensures that EC2Config can obtain information from metadata for activation and other plug-ins. + `ShouldAddRoutes`—Adds a custom route to the primary network adapter to enable the following IP addresses when multiple NICs are attached: 169.254.169.250, 169.254.169.251, and 169.254.169.254. These addresses are used by Windows Activation and when you access instance metadata. + `RemoveCredentialsfromSyspreponStartup`—Removes the administrator password from `Sysprep.xml` the next time the service starts. To ensure that this password persists, edit this setting. **DriveLetterConfig.xml** This file contains settings that control drive letter mappings. By default, a volume can be mapped to any available drive letter. You can mount a volume to a particular drive letter as follows. ``` . . . ``` + `VolumeName`—The volume label. For example, `My Volume`. To specify a mapping for an instance storage volume, use the label `Temporary Storage X`, where `X` is a number from 0 to 25. + `DriveLetter`—The drive letter. For example, `M:`. The mapping fails if the drive letter is already in use. **EventLogConfig.xml** This file contains settings that control the event log information that's displayed on the console while the instance is booting. By default, we display the three most recent error entries from the System event log. + `Category`—The event log key to monitor. + `ErrorType`—The event type (for example, `Error`, `Warning`, `Information`.) + `NumEntries`—The number of events stored for this category. + `LastMessageTime`—To prevent the same message from being pushed repeatedly, the service updates this value every time it pushes a message. + `AppName`—The event source or application that logged the event. **WallpaperSettings.xml** This file contains settings that control the information that's displayed on the desktop background. The following information is displayed by default. + `Hostname`—Displays the computer name. + `Instance ID`—Displays the ID of the instance. + `Public IP Address`—Displays the public IP address of the instance. + `Private IP Address`—Displays the private IP address of the instance. + `Availability Zone`—Displays the Availability Zone in which the instance is running. + `Instance Size`—Displays the type of instance. + `Architecture`—Displays the setting of the `PROCESSOR_ARCHITECTURE` environment variable. You can remove any of the information that's displayed by default by deleting its entry. You can add additional instance metadata to display as follows. ``` display_name metadata meta-data/path ``` You can add additional System environment variables to display as follows. ``` display_name EnvironmentVariable variable-name ``` **InitializeDrivesSettings.xml** This file contains settings that control how EC2Config initializes drives. By default, EC2Config initialize drives that were not brought online with the operating system. You can customize the plugin as follows. ``` setting ``` Use a settings group to specify how you want to initialize drives: *FormatWithTRIM* Enables the TRIM command when formatting drives. After a drive has been formatted and initialized, the system restores TRIM configuration. Starting with EC2Config version 3.18, the TRIM command is disabled during the disk format operation by default. This improves formatting times. Use this setting to enable TRIM during the disk format operation for EC2Config version 3.18 and later. *FormatWithoutTRIM* Disables the TRIM command when formatting drives and improves formatting times in Windows. After a drive has been formatted and initialized, the system restores TRIM configuration. *DisableInitializeDrives* Disables formatting for new drives. Use this setting to initialize drives manually. # Install the latest version of EC2Config Install EC2Config **Note** The latest launch agent for Windows Server 2022 and later operating system versions is [EC2Launch v2](ec2launch-v2.md), which replaces both EC2Config and EC2Launch. EC2Launch v2 comes pre-installed on AWS Windows Server 2022 and 2025 AMIs. You can also manually install and configure the agent on Windows Server 2016 and 2019. For more information, see [Install EC2Launch v2](ec2launch-v2-install.md). For information about how to receive notifications for EC2Config updates, see [Subscribe to EC2 Windows launch agent notifications](launch-agents-subscribe-notifications.md). For information about the changes in each version, see the [EC2Config version history](ec2config-version-details.md). ## Before you begin + Verify that you have .NET framework 3.5 SP1 or greater. + By default, Setup replaces your settings files with default settings files during installation and restarts the EC2Config service when the installation is completed. If you changed EC2Config service settings, copy the `config.xml` file from the `%Program Files%\Amazon\Ec2ConfigService\Settings` directory. After you update the EC2Config service, you can restore this file to retain your configuration changes. ## Verify the EC2Config version Use the following procedure to verify the version of EC2Config that is installed on your instances. **To verify the installed version of EC2Config** 1. Launch an instance from your AMI and connect to it. 1. In Control Panel, select **Programs and Features**. 1. In the list of installed programs, look for `Ec2ConfigService`. Its version number appears in the **Version** column. ## Update EC2Config Use the following procedure to download and install the latest version of EC2Config on your instances. **To download and install the latest version of EC2Config** 1. Download and unzip the [EC2Config installer](https://s3.amazonaws.com/ec2-downloads-windows/EC2Config/EC2Install.zip). 1. Run `EC2Install.exe`. For a complete list of options, run `EC2Install` with the `/?` option. By default, setup displays prompts. To run the command with no prompts, use the `/quiet` option. **Important** To keep the custom settings from the `config.xml` file that you saved, run `EC2Install` with the `/norestart` option, restore your settings, and then restart the EC2Config service manually. 1. If you are running EC2Config version 4.0 or later, you must restart SSM Agent on the instance from the Microsoft Services snap-in. **Note** The updated EC2Config version information will not appear in the instance System Log or Trusted Advisor check until you reboot or stop and start your instance. **To download and install the latest version of EC2Config using PowerShell** To download, unzip, and install the latest version of EC2Config using PowerShell, run the following commands from a PowerShell window: ``` $Url = "https://s3.amazonaws.com/ec2-downloads-windows/EC2Config/EC2Install.zip" $DownloadZipFile = "$env:USERPROFILE\Desktop\" + $(Split-Path -Path $Url -Leaf) $ExtractPath = "$env:USERPROFILE\Desktop\" Invoke-WebRequest -Uri $Url -OutFile $DownloadZipFile $ExtractShell = New-Object -ComObject Shell.Application $ExtractFiles = $ExtractShell.Namespace($DownloadZipFile).Items() $ExtractShell.NameSpace($ExtractPath).CopyHere($ExtractFiles) Start-Process $ExtractPath Start-Process ` -FilePath $env:USERPROFILE\Desktop\EC2Install.exe ` -ArgumentList "/S" ``` **Note** If you receive an error when downloading the file, and you are using Windows Server 2016 or earlier, TLS 1.2 might need to be enabled for your PowerShell terminal. You can enable TLS 1.2 for the current PowerShell session with the following command and then try again: ``` [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 ``` Verify the installation by checking `C:\Program Files\Amazon\` for the `Ec2ConfigService` directory. # Configure .NET proxy settings for the EC2Config service Configure proxy settings You can configure the EC2Config service to communicate through a proxy using one of the following methods: the AWS SDK for .NET, the `system.net` element, or Microsoft Group Policy and Internet Explorer. Using the AWS SDK for .NET is the preferred method because you can specify sign-in credentials. **Topics** + [ ## Configure proxy settings using the AWS SDK for .NET (Preferred) ](#sdk-proxy) + [ ## Configure proxy settings using the system.net element ](#system-proxy) + [ ## Configure proxy settings using Microsoft Group Policy and Microsoft Internet Explorer ](#ie-proxy) ## Configure proxy settings using the AWS SDK for .NET (Preferred) You can configure proxy settings for the EC2Config service by specifying the `proxy` element in the `Ec2Config.exe.config` file. For more information, see [Configuration Files Reference for AWS SDK for .NET](https://docs.aws.amazon.com/sdk-for-net/latest/developer-guide/net-dg-config-ref.html#net-dg-config-ref-elements-proxy). **To specify the proxy element in Ec2Config.exe.config** 1. Edit the `Ec2Config.exe.config` file on an instance where you want the EC2Config service to communicate through a proxy. By default, the file is located in the following directory: `%ProgramFiles%\Amazon\Ec2ConfigService`. 1. Add the following `aws` element to the `configSections`. Do not add this to any existing `sectionGroups`. **For EC2Config versions 3.17 or earlier** ```
``` **For EC2Config versions 3.18 or later** ```
``` 1. Add the following `aws` element to the `Ec2Config.exe.config` file. ``` ``` 1. Save your changes. ## Configure proxy settings using the system.net element You can specify proxy settings in a `system.net` element in the `Ec2Config.exe.config` file. For more information, see [defaultProxy element (network settings)](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings). **To specify the system.net element in Ec2Config.exe.config** 1. Edit the `Ec2Config.exe.config` file on an instance where you want the EC2Config service to communicate through a proxy. By default, the file is located in the following directory: `%ProgramFiles%\Amazon\Ec2ConfigService`. 1. Add a `defaultProxy` entry to `system.net`. For more information, see [defaultProxy element (network settings)](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings). For example, the following configuration routes all traffic to use the proxy that is currently configured for Internet Explorer, with the exception of the metadata and licensing traffic, which will bypass the proxy. ``` ``` 1. Save your changes. ## Configure proxy settings using Microsoft Group Policy and Microsoft Internet Explorer The EC2Config service runs under the Local System user account. You can specify instance-wide proxy settings for this account in Internet Explorer after you change Group Policy settings on the instance. **To configure proxy settings using Group Policy and Internet Explorer** 1. On an instance where you want the EC2Config service to communicate through a proxy, open a Command prompt as an Administrator, type **gpedit.msc**, and press Enter. 1. In the Local Group Policy Editor, under **Local Computer Policy**, choose **Computer Configuration**, **Administrative Templates**, **Windows Components**, **Internet Explorer**. 1. In the right-pane, choose **Make proxy settings per-machine (rather than per-user)** and then choose **Edit policy setting**. 1. Choose **Enabled**, and then choose **Apply**. 1. Open Internet Explorer, and then choose the **Tools** button. 1. Choose **Internet Option**, and then choose the **Connections** tab. 1. Choose **LAN settings**. 1. Under **Proxy server**, choose the **Use a proxy server for your LAN** option. 1. Specify address and port information and then choose **OK**. # Set EC2Config service properties from the system dialog on your EC2 Windows instance Set EC2Config service properties The following procedure describes how to use the **EC2 Service Properties** system dialog to enable or disable settings. 1. Launch and connect to your Windows instance. 1. From the **Start** menu, click **All Programs**, and then click **EC2ConfigService Settings**. ![\[EC2Config service properties shown in the General tab.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EC2ConfigProperties_General.png) 1. On the **General** tab of the **EC2 Service Properties** system dialog, you can enable or disable the following settings. **Set Computer Name** If this setting is enabled (it is disabled by default), the host name is compared to the current internal IP address at each boot; if the host name and internal IP address do not match, the host name is reset to contain the internal IP address and then the system reboots to pick up the new host name. To set your own host name, or to prevent your existing host name from being modified, do not enable this setting. **User Data** User data execution enables you to specify scripts in the instance metadata. By default, these scripts are run during the initial launch. You can also configure them to run the next time you reboot or start the instance, or every time you reboot or start the instance. If you have a large script, we recommend that you use user data to download the script, and then run it. For more information, see [User data execution](user-data.md#user-data-execution). **Event Log** Use this setting to display event log entries on the console during boot for easy monitoring and debugging. Click **Settings** to specify filters for the log entries sent to the console. The default filter sends the three most recent error entries from the system event log to the console. **Wallpaper Information** Use this setting to display system information on the desktop background. The following is an example of the information displayed on the desktop background. ![\[Wallpaper Information displayed on the desktop background.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EC2ConfigProperties_Wallpaper.png) The information displayed on the desktop background is controlled by the settings file `EC2ConfigService\Settings\WallpaperSettings.xml`. **Enable Hibernation** Use this setting to allow EC2 to signal the operating system to perform hibernation. 1. Click the **Storage** tab. You can enable or disable the following settings. ![\[Storage tab within EC2 Service Properties.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EC2ConfigProperties_Storage.png) **Root Volume** This setting dynamically extends Disk 0/Volume 0 to include any unpartitioned space. This can be useful when the instance is booted from a root volume that has a custom size. **Initialize Drives** This setting formats and mounts all volumes attached to the instance during start. **Drive Letter Mapping** The system maps the volumes attached to an instance to drive letters. For Amazon EBS volumes, the default is to assign drive letters going from D: to Z:. For instance store volumes, the default depends on the driver. AWS PV drivers and Citrix PV drivers assign instance store volumes drive letters going from Z: to A:. Red Hat drivers assign instance store volumes drive letters going from D: to Z:. To choose the drive letters for your volumes, click **Mappings**. In the **DriveLetterSetting** dialog box, specify the **Volume Name** and **Drive Letter** values for each volume, click **Apply**, and then click **OK**. We recommend that you select drive letters that avoid conflicts with drive letters that are likely to be in use, such as drive letters in the middle of the alphabet. ![\[DriveLetterSetting dialog box.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EC2ConfigProperties_driver_letter_mapping.png) After you specify a drive letter mapping and attach a volume with same label as one of the volume names that you specified, EC2Config automatically assigns your specified drive letter to that volume. However, the drive letter mapping fails if the drive letter is already in use. Note that EC2Config doesn't change the drive letters of volumes that were already mounted when you specified the drive letter mapping. 1. To save your settings and continue working on them later, click **OK** to close the **EC2 Service Properties** system dialog. If you have finished customizing your instance and want to create an AMI from that instance, see [Create an Amazon EC2 AMI using Windows Sysprep](ami-create-win-sysprep.md). # Troubleshoot issues with the EC2Config launch agent Troubleshoot EC2Config The following information can help you troubleshoot issues with the EC2Config service. ## Update EC2Config on an unreachable instance Use the following procedure to update the EC2Config service on a Windows Server instance that is inaccessible using Remote Desktop. **To update EC2Config on an Amazon EBS-backed Windows instance that you can't connect to** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Instances**. 1. Locate the affected instance. Select the instance and choose **Instance state**, and then choose **Stop instance**. **Warning** When you stop an instance, the data on instance store volumes is lost. To preserve this data, back it up to persistent storage. 1. Choose **Launch instances** and create a temporary `t2.micro` instance in the same Availability Zone as the affected instance. Use a different AMI than the one that you used to launch the affected instance. **Important** If you do not create the instance in the same Availability Zone as the affected instance you will not be able to attach the root volume of the affected instance to the new instance. 1. In the EC2 console, choose **Volumes**. 1. Locate the root volume of the affected instance. Detach the volume and then attach the volume to the temporary instance that you created earlier. Attach it with the default device name (xvdf). 1. Use Remote Desktop to connect to the temporary instance, and then use the Disk Management utility to make the volume available for use. 1. [Download](https://s3.amazonaws.com/ec2-downloads-windows/EC2Config/EC2Install.zip) the latest version of the EC2Config service. Extract the files from the `.zip` file to the `Temp` directory on the drive you attached. 1. On the temporary instance, open the Run dialog box, type **regedit**, and press Enter. 1. Choose `HKEY_LOCAL_MACHINE`. From the **File** menu, choose **Load Hive**. Choose the drive and then navigate to and open the following file: `Windows\System32\config\SOFTWARE`. When prompted, specify a key name. 1. Select the key you just loaded and navigate to `Microsoft\Windows\CurrentVersion`. Choose the `RunOnce` key. If this key doesn't exist, choose `CurrentVersion` from the context (right-click) menu, choose **New** and then choose **Key**. Name the key `RunOnce`. 1. From the context (right-click) menu choose the `RunOnce` key, choose **New** and then choose **String Value**. Enter `Ec2Install` as the name and `C:\Temp\Ec2Install.exe /quiet` as the data. 1. Choose the `HKEY_LOCAL_MACHINE\specified key name\Microsoft\Windows NT\CurrentVersion\Winlogon` key. From the context (right-click) menu choose **New**, and then choose **String Value**. Enter **AutoAdminLogon** as the name and **1** as the value data. 1. Choose the `HKEY_LOCAL_MACHINE\specified key name\Microsoft\Windows NT\CurrentVersion\Winlogon>` key. From the context (right-click) menu choose **New**, and then choose **String Value**. Enter **DefaultUserName** as the name and **Administrator** as the value data. 1. Choose the `HKEY_LOCAL_MACHINE\specified key name\Microsoft\Windows NT\CurrentVersion\Winlogon` key. From the context (right-click) menu choose **New**, and then choose **String Value**. Type **DefaultPassword** as the name and enter a password in the value data. 1. In the Registry Editor navigation pane, choose the temporary key that you created when you first opened Registry Editor. 1. From the **File** menu, choose **Unload Hive**. 1. In Disk Management Utility, choose the drive you attached earlier, open the context (right-click) menu, and choose **Offline**. 1. In the Amazon EC2 console, detach the affected volume from the temporary instance and reattach it to your instance with the device name `/dev/sda1`. You must specify this device name to designate the volume as a root volume. 1. [Stop and start Amazon EC2 instances](Stop_Start.md) the instance. 1. After the instance starts, check the system log and verify that you see the message Windows is ready to use. 1. Open Registry Editor and choose `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon`. Delete the String Value keys you created earlier: **AutoAdminLogon**, **DefaultUserName**, and **DefaultPassword**. 1. Delete or stop the temporary instance you created in this procedure. # EC2Config version history Version history The following table describes the released versions of EC2Config. For information about the updates for SSM Agent, see [Systems Manager SSM Agent Release Notes](https://github.com/aws/amazon-ssm-agent/blob/master/RELEASENOTES.md). **Important** EC2Config has reached the end of support. Only the latest version of the EC2Config agent is available for download. Prior versions are marked as private. | Version | Details | Release date | | --- | --- | --- | | 4.9.5777 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 17 June 2024 | | 4.9.5554 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 4 October 2023 | | 4.9.5467 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 1 August 2023 | | 4.9.5288 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 8 March 2023 | | 4.9.5231 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 14 February 2023 | | 4.9.5103 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 5 December 2022 | | 4.9.5064 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 16 November 2022 | | 4.9.4588 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 31 May 2022 | | 4.9.4556 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 1 March 2022 | | 4.9.4536 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 31 January 2022 | | 4.9.4508 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 6 October 2021 | | 4.9.4500 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 7 September 2021 | | 4.9.4419 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 2 June 2021 | | 4.9.4381 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 4 May 2021 | | 4.9.4326 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 3 March 2021 | | 4.9.4279 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 11 December 2020 | | 4.9.4222 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 7 April 2020 | | 4.9.4122 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 4 March 2020 | | 4.9.3865 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 31 October 2019 | | 4.9.3519 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 18 June 2019 | | 4.9.3429 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 25 April 2019 | | 4.9.3289 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 11 February 2019 | | 4.9.3270 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 22 January 2019 | | 4.9.3230 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 10 January 2019 | | 4.9.3160 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 15 December 2018 | | 4.9.3067 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 8 November 2018 | | 4.9.3034 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 24 October 2018 | | 4.9.2986 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 11 October 2018 | | 4.9.2953 | New version of SSM Agent (2.3.117.0) | 2 October 2018 | | 4.9.2926 | New version of SSM Agent (2.3.68.0) | 18 September 2018 | | 4.9.2905 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 17 September 2018 | | 4.9.2854 | New version of SSM Agent (2.3.13.0) | 17 August 2018 | | 4.9.2831 | New version of SSM Agent (2.2.916.0) | 7 August 2018 | | 4.9.2818 | New version of SSM Agent (2.2.902.0) | 31 July 2018 | | 4.9.2756 | New version of SSM Agent (2.2.800.0) | 27 June 2018 | | 4.9.2688 | New version of SSM Agent (2.2.607.0) | 25 May 2018 | | 4.9.2660 | New version of SSM Agent (2.2.546.0) | 11 May 2018 | | 4.9.2644 | New version of SSM Agent (2.2.493.0) | 26 April 2018 | | 4.9.2586 | New version of SSM Agent (2.2.392.0) | 28 March 2018 | | 4.9.2565 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 13 March 2018 | | 4.9.2549 | New version of SSM Agent (2.2.325.0) | 8 March 2018 | | 4.9.2461 | New version of SSM Agent (2.2.257.0) | 15 February 2018 | | 4.9.2439 | New version of SSM Agent (2.2.191.0) | 6 February 2018 | | 4.9.2400 | New version of SSM Agent (2.2.160.0) | 16 January 2018 | | 4.9.2327 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 2 January 2018 | | 4.9.2294 | New version of SSM Agent (2.2.103.0) | 4 December 2017 | | 4.9.2262 | New version of SSM Agent (2.2.93.0) | 15 November 2017 | | 4.9.2246 | New version of SSM Agent (2.2.82.0) | 11 November 2017 | | 4.9.2218 | New version of SSM Agent (2.2.64.0) | 29 October 2017 | | 4.9.2212 | New version of SSM Agent (2.2.58.0) | 23 October 2017 | | 4.9.2203 | New version of SSM Agent (2.2.45.0) | 19 October 2017 | | 4.9.2188 | New version of SSM Agent (2.2.30.0) | 10 October 2017 | | 4.9.2180 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | 5 October 2017 | | 4.9.2143 | New version of SSM Agent (2.2.16.0) | 1 October 2017 | | 4.9.2140 | New version of SSM Agent (2.1.10.0) | | | 4.9.2130 | New version of SSM Agent (2.1.4.0) | | | 4.9.2106 | New version of SSM Agent (2.0.952.0) | | | 4.9.2061 | New version of SSM Agent (2.0.922.0) | | | 4.9.2047 | New version of SSM Agent (2.0.913.0) | | | 4.9.2031 | New version of SSM Agent (2.0.902.0) | | | 4.9.2016 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1981 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1964 | New version of SSM Agent (2.0.842.0) | | | 4.9.1951 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1925 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1900 | New version of SSM Agent (2.0.805.0) | | | 4.9.1876 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1863 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.9.1791 | New version of SSM Agent (2.0.767.0) | | | 4.9.1775 | New version of SSM Agent (2.0.761.0) | | | 4.9.1752 | New version of SSM Agent (2.0.755.0) | | | 4.9.1711 | New version of SSM Agent (2.0.730.0) | | | 4.8.1676 | New version of SSM Agent (2.0.716.0) | | | 4.7.1631 | New version of SSM Agent (2.0.682.0) | | | 4.6.1579 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 4.5.1534 | New version of SSM Agent (2.0.645.1) | | | 4.4.1503 | New version of SSM Agent (2.0.633.0) | | | 4.3.1472 | New version of SSM Agent (2.0.617.1) | | | 4.2.1442 | New version of SSM Agent (2.0.599.0) | | | 4.1.1378 | New version of SSM Agent (2.0.558.0) | | | 4.0.1343 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 3.19.1153 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 3.18.1118 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 3.17.1032 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2config-version-details.html) | | | 3.16.930 | Added support to log "Window is Ready to use" event to Windows Event Log on start. | | | 3.15.880 | Fix to allow uploading Systems Manager Run Command output to S3 bucket names with '.' character. | | | 3.14.786 | Added support to override InitializeDisks plugin settings. For example: To speed up SSD disk initialize, you can temporarily disable TRIM by specifying this in userdata: FormatWithoutTRIM