Elasticbean environment issue - Timeout error

Hi,

When running the eb deploy command, since it was taking too long, I aborted it. After that, when I try to clone an existing elasticbean environment, I am getting a Timeout error.

When I create a new Elasticbean env and upload code that is already working in another elasticbean env, the new env is also not coming up, throwing the below error:

eb deploy Creating application version archive "app-802e-230515_202312481785". Uploading: [##################################################] 100% Done... 2023-05-16 01:26:09 INFO Environment update is starting.
2023-05-16 01:27:00 INFO Deploying new version to instance(s). 2023-05-16 01:27:02 INFO Batch 1: Starting application deployment on instance(s) [i-xxx]. 2023-05-16 01:27:03 INFO Batch 1: Starting application deployment command execution. -- Events -- (safe to Ctrl+C) Use "eb abort" to cancel the command.

ERROR: TimeoutError - The EB CLI timed out after 10 minute(s). The operation might still be running. To keep viewing events, run 'eb events -f'. To set timeout duration, use '--timeout MINUTES'.

These are the event logs in the ElasticBean console:

May 16, 2023 07:39:35 (UTC+5:30) ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version. May 16, 2023 07:39:35 (UTC+5:30) ERROR Failed to deploy application. May 16, 2023 07:39:35 (UTC+5:30) WARN User initiated abort was received. Canceling the current operation. May 16, 2023 07:39:34 (UTC+5:30) INFO Command execution completed on 1 of 2 instances in environment. May 16, 2023 07:39:34 (UTC+5:30) INFO Batch 1: Completed application deployment command execution. May 16, 2023 07:39:34 (UTC+5:30) WARN The following instances have not responded in the allowed command timeout time (they might still finish eventually on their own): [i-xxxx]. May 16, 2023 07:27:10 (UTC+5:30) WARN User initiated abort was received, however the current step of the operation in progress is not cancellable. The current operation will be aborted as soon as the non-cancellable step(s) complete. May 16, 2023 07:25:30 (UTC+5:30) INFO Batch 1: Starting application deployment command execution. May 16, 2023 07:25:29 (UTC+5:30) INFO Batch 1: Starting application deployment on instance(s) [i-xxxx]. May 16, 2023 07:25:28 (UTC+5:30) INFO Deploying new version to instance(s). May 16, 2023 07:24:40 (UTC+5:30) INFO Environment update is starting.

We do not want to reboot as we do not have a backup of the production environment. Any pointers on how to resolve this issue?

Thanks.