Beyhan Veli

Additional context for this issue in this Slack thread: https://natsio.slack.com/archives/C069GSYFP/p1563202735013400

@wallyqs thanks for the prompt response! Is there a why to find out, which commands get lost during disconnects?

A hint provided by the `cf enable-ssh ` command will also help a lot here like with `cf bs...` provides. Is this something the CF CLI team will accept? I...

The documented approach with `/tmp/lifecycle/shell` doesn't work for apps deployed with Docker images, because `/tmp/lifecycle/shell` is provided by the buildpacks. What about `diego-sshd` sourcing the env from `/proc//environ`?

Could you check in the AWS Console the state of the instance which BOSH failed to create? Is it possible to `ssh` into that instance and check for logs, e.g....

You could use the option [keep_unreachable_vms](https://bosh.io/jobs/director?source=github.com/cloudfoundry/bosh&version=274.4.0#p%3ddirector.debug.keep_unreachable_vms) to keep the VM for debugging. I'm not aware of any issues with recreated when switching to encrypted volumes.

Hi, it looks like that the VM is preserved only if it was created successfully ([check this](https://github.com/cloudfoundry/bosh/blob/da56d19e30234239582ecfdd6a2da682631f6832/src/bosh-director/lib/bosh/director/deployment_plan/steps/create_vm_step.rb#L38-L50)). If the creation fails then this property doesn't have any effect ([check this](https://github.com/cloudfoundry/bosh/blob/da56d19e30234239582ecfdd6a2da682631f6832/src/bosh-director/lib/bosh/director/deployment_plan/steps/create_vm_step.rb#L167))....

It's not Golang but Ruby. Basically, you need to comment out this line https://github.com/cloudfoundry/bosh/blob/da56d19e30234239582ecfdd6a2da682631f6832/src/bosh-director/lib/bosh/director/deployment_plan/steps/create_vm_step.rb#L167 You can `ssh` into your BOSH Director find the location of `create_vm_step.rb` file. Comment out [line](https://github.com/cloudfoundry/bosh/blob/da56d19e30234239582ecfdd6a2da682631f6832/src/bosh-director/lib/bosh/director/deployment_plan/steps/create_vm_step.rb#L167)...

It is defiantly AWS failing to start the instance because from the logs: ``` I, [2022-11-08T06:00:50.275697 #13125] INFO -- [req_id cpi-636029]: Waiting for instance to exist... D, [2022-11-08T06:00:50.360707 #13125] DEBUG...

Hi @sneal, The first step would be to open a pr for the CFF [community](https://github.com/cloudfoundry/community/blob/main/toc/working-groups/app-runtime-interfaces.md?plain=1#L389-L402) repo which suggest to add this repository to the App Runtime Interfaces WG. Most probably...