unable to create execute session with task that has multiple containers

Hello,

Issue description: Im unable to create sessions or exec in different containers on the same task (even after terminating the session with the other container).

Issue replication: Let's say I have 2 containers (A and B) running on the same task. When I create an exec session with Container A, I can login to with out any issue and I do log out (I can see the session terminated message) from the session. Now If i try to login to a different container (say B) this time - I'm getting the below mentioned error, and we can see the same phenomenon if I do login to Container B first and terminate the session and try to login to Container A

"The Session Manager plugin was installed successfully. Use the AWS CLI to start a session.
An error occurred (TargetNotConnectedException) when calling the ExecuteCommand operation: The execute command failed due to an internal error. Try again later."

Thanks.
Eran Ovadia.

Start by reproducing the AWS CLI ExecuteCommand failure with two containers in one task, logging into one container, terminating the session, and then trying the other. No repository file or test is named; done would mean execute sessions can be created successfully for both containers in either order.

Written by the indexing model from the issue text.