[JENKINS-69457] Reconnect after init.sh script runs

Sometimes it's necessary to make changes in the init script that can't be represented in the current session - e.g. goup changes. To allow these kind of changes it would be necessary that a new session will be opened before the agent will be started.

---
Originally reported by fgosse_truffls, imported from: Reconnect after init.sh script runs

• assignee: thoulen
  
• status: Open
  
• priority: Minor
  
• component(s): ec2-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-06
  

Sometimes it's necessary to make changes in the init script that can't be represented in the current session - e.g. goup changes. To allow these kind of changes it would be necessary that a new session will be opened before the agent will be started.

environment

```
Jenkins: 2.346.3

Amazon EC2 plugin: 2.0.0
```

Start by tracing the ec2-plugin flow that runs init.sh and starts the agent, then identify where the current session is established. Confirm how a new session could be opened before agent startup and verify that changes made by init.sh are visible to the agent. The issue names no files or tests, so the repository's startup and connection flow will need to be located first.

Written by the indexing model from the issue text.