Update AWS configuration to use EC2Launch v2 agent

nservicebus/operations/configuring-aws.md

@@ -1,7 +1,7 @@
 ---
 title: Configuring Amazon EC2 Instances for NServiceBus
 summary: Endpoint naming issues that occur when restarting the server from the AWS Management Console can be prevented using a tool
-reviewed: 2022-10-19
+reviewed: 2025-02-07
 related:
  - nservicebus/operations
 redirects:
@@ -10,12 +10,10 @@ redirects:
 
 Stale endpoint naming issues may occur when shutting down and restarting the server instance from the [AWS Management Console](https://aws.amazon.com/console/) due to AWS changing the hostname of the instance.
 
-It is possible to turn off this server name change feature using the [EC2Config tool](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2config-service.html) which is installed on the server instance:
+It is possible to turn off this server name change feature using the [EC2Launch v2 agent](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-v2.html) which is installed on the server instance:
 
 ![EC2 Config Settings](ec2-config-settings.png)
 
-In this tool, uncheck "Set Computer Name" in the General tab and click OK:
+In this tool, uncheck "Set Computer Name" in the General tab and click Save:
 
 ![](ec2-service-properties.png)
-
-For Windows 2016 Server, EC2Config has been replaced by EC2Launch. Review the [EC2Launch documentation](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch.html) for instructions on how to change the computer name for EC2 instances on Windows 2016 Server.