Docs: #3236

Author: BornToBeRoot

Website/docs/application/aws-session-manager.md

@@ -4,10 +4,20 @@ sidebar_position: 11
 
 # AWS Session Manager
 
+:::danger
+
+This feature has been removed! NETworkManager **2025.10.18.0** will be the last version to support the **AWS Session Manager** feature.
+
+The [AWS Session Manager Plugin](https://github.com/aws/session-manager-plugin) is not actively maintained and contains several bugs (e.g. German / Spain keyboard layout issues). The current code base was also difficult to maintain and extend, and I currently have no test environment.
+
+You can still use AWS Session Manager within NETworkManager with the [PowerShell](./powershell.md) feature by using the `aws ssm start-session --target <instance-id>` command.
+
+:::
+
 With **AWS** (Systems Manager) **Session Manager**, you can connect to and manage an EC2 instance without opening inbound ports, running a bastion host, or managing SSH keys. The integration of AWS Session Manager with NETworkManger supports tabs and profiles for hosts. The connection can be established via a profile (double-click, Enter key or right-click `Connect`) or directly via the [connection](#connect) dialog. You can also synchronize your EC2 instances from AWS. To connect to the instances a PowerShell console is used with the AWS CLI and the AWS Session Manager plugin. The connection to the instances is established via the following command:
 
 ```PowerShell
-aws ssm start-session --target <INSTANCE_ID>
+aws ssm start-session --target <instance-id>
 ```
 
 :::note
@@ -281,7 +291,7 @@ Sensitive data like the API keys are stored in plain text in the file `~\.aws\cr
 You can verify the connection to the EC2 instance through AWS Systems Manager Session Manager by opening a PowerShell and connecting to the instance through AWS CLI:
 
 ```
-aws ssm start-session --target instance-id <INSTANCE_ID>
+aws ssm start-session --target instance-id <instance-id>
 ```
 
 ## Connect

Website/docs/application/powershell.md

@@ -4,7 +4,7 @@ sidebar_position: 9
 
 # PowerShell
 
-With **PowerShell** you can launch PowerShell consoles locally or connect to remote computers using [PowerShell Remoting](https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/08-powershell-remoting). You can also execute command-line applications such as `wsl`, `k9s`, or any other tools typically accessible from a PowerShell session. In addition, you can run PowerShell scripts directly within the console.
+With **PowerShell** you can launch PowerShell consoles locally or connect to remote computers using [PowerShell Remoting](https://learn.microsoft.com/en-us/powershell/scripting/learn/ps101/08-powershell-remoting). You can also execute command-line applications such as `wsl`, `aws ssm`, `k9s`, or any other tools typically accessible from a PowerShell session. In addition, you can run PowerShell scripts directly within the console.
 
 The integration of PowerShell with NETworkManger supports tabs and profiles for hosts (and tools). You can launch the console / establish a connection via a profile (double-click, Enter key or right-click `Connect`) or directly via the [connection](#connect) dialog.
 
@@ -22,12 +22,15 @@ Windows PowerShell and PowerShell are supported. Indructions for installing Powe
 
 :::tip
 
-Launching a command-line application such as `wsl` or `k9s` can be done by passing the [command](#command) to the PowerShell console.
+Launching a command-line application such as `wsl`, `aws ssm` or `k9s` can be done by passing the [command](#command) to the PowerShell console.
 
 ```powershell
 # Connect to WSL
 wsl -d <DISTRIBUTION>
 
+# Connect to an EC2 instance via AWS Session Manager
+aws ssm start-session --target <instance-id>
+
 # Connect to Kubernetes
 k9s --readonly
 ```

Website/docs/changelog/next-release.md

@@ -20,6 +20,15 @@ Release date: **xx.xx.2025**
 - Migrated from .NET 8.0 (LTS) to .NET 10.0 (LTS).
   Upgrade your [.NET Desktop Runtime to version 10.0 (LTS) - x64](https://dotnet.microsoft.com/en-us/download/dotnet/10.0/runtime) before you install this version. [#3229](https://github.com/BornToBeRoot/NETworkManager/pull/3229)
 
+- `AWS Session Manager` feature has been removed. The [AWS Session Manager Plugin](https://github.com/aws/session-manager-plugin) is not actively maintained and contains several bugs (e.g. German / Spain keyboard layout issues). The current code base was also difficult to maintain and extend, and I currently have no test environment.
+  The Sync feature (EC2 instances -> Profiles) has been removed as well, because it was limited to AWS Session Manager only. This will be re-introduced in a future release to support multiple proividers (`AWS`, `Azure`, etc.) and more features like `Ping Monitor`, `PuTTY` or `Remote Desktop`.
+
+  :::note
+
+  You can still use AWS Session Manager within NETworkManager with the PowerShell feature by using the `aws ssm start-session --target <instance-id>` command.
+
+  :::
+
 ## What's new?
 
 **Remote Desktop**

Website/docs/faq/powershell-cmd-apps.md

@@ -9,13 +9,18 @@ Create a new connection or profile with the following settings:
   # Connect to WSL
   wsl -d <DISTRIBUTION>
 
+  # Connect to an EC2 instance via AWS Session Manager
+  aws ssm start-session --target <instance-id>
+
   # Connect to Kubernetes
   k9s --readonly
   ```
 
 :::note
 
-Windows Subsystem for Linux (WSL) must be installed and enabled on your system to use this feature.
+Windows Subsystem for Linux (WSL) must be installed and enabled on your system to use WSL.
+
+AWS CLI and AWS Session Manager Plugin must be installed and configured to connect to EC2 instances.
 
 :::
 

Website/docs/faq/settings-priority.md

@@ -1,21 +1,21 @@
-# Setting priority
+# Settings Priority
 
-## In which priority are settings applied?
+## How does NETworkManager prioritize settings across different levels (global, group, profile)?
 
-There are three levels of settings:
+NETworkManager uses a clear hierarchy to apply settings, allowing you to configure profiles with flexibility and precision. Settings are prioritized across three levels, from broadest to most specific:
 
-- **Global settings**
+1. **Global Settings**  
+   Default settings applied across all profiles in NETworkManager unless overridden.  
+   _Example_: A default SSH key file used for all network devices.
 
-  Global settings are the default settings of the application. They are used if no other settings are available.
+2. **Group Settings**  
+   Applied to all profiles within a specific group, overriding global settings. Use these to customize settings for a set of devices.  
+   _Example_: A unique SSH key file for a group of servers in a data center.
 
-- **Group settings**
+3. **Profile Settings**  
+   Specific to an individual profile, overriding both group and global settings. Use these for fine-tuned configurations on a single device.  
+   _Example_: A custom SSH key file for a critical server.
 
-  Group settings are applied to all profiles in a group. They overwrite global settings. E.g. for a specific group of servers to overwrite the SSH key file or Windows credentials.
+Settings are applied in this order:
 
-- **Profile settings**
-
-  Profile settings are applied to a specific profile. They overwrite group settings. E.g. for a specific server to overwrite the SSH key file or Windows credentials.
-
-The priority is as follows:
-
-`Global settings (default) → Group settings (overwrites global) → Profile settings (overwrites group)`
+**Global Settings (default) → Group Settings (overrides Global) → Profile Settings (overrides Group)**