Plugin with name InteractiveCommands not found

[flipmokid]

Hi,

Most likely user/installation error but I've been using execute-command using the aws cli for a few months. I've not used it for a month or two and coming back to it I get the error below.

aws ecs execute-command  \
    --region eu-west-1 \
    --cluster ***** \
    --task ****************** \
    --container xray-daemon \
    --command "/bin/bash" \
    --interactive


The Session Manager plugin was installed successfully. Use the AWS CLI to start a session.


Starting session with SessionId: ecs-execute-command-0228164ca8ff6e2c1


SessionId: ecs-execute-command-0228164ca8ff6e2c1 : Plugin with name InteractiveCommands not found. Step name: InteractiveCommands

I've upgrade my aws-cli to aws-cli/2.7.22 Python/3.10.6 Darwin/21.3.0 source/arm64 prompt/off and session-manager-plugin to 1.2.339.0 but the problem persists.

Is there anything I need to do to get InteractiveCommands plugin added?

[flipmokid]

Killing the container and deploying a new one seemed to get around this issue.

[danstewart]

Sorry for commenting on an old and closed issue but this was the only result I found when I had this issue.
I'm not 100% sure but I think the issue might be related to the /tmp directory being full in the container.

I was trying to connect to clear some space in /tmp, got the error so restarted the container instead and now I can connect without issue.

[oiekjr]

@danstewart
I recently encountered this as well.
However, the only information about this is in this issue.

If you don't mind, could you tell me a bit about it?
Does "restarted" refer to the force-new-deployment of the service?

[danstewart]

@oiekjr I killed the task, and the autoscaling recreated it, with a fresh /tmp directory.

[oiekjr]

@danstewart It did not seem to solve my case. Thank you for your response!

[Burekasim]

In my case the ephemeral storage was full, that's what caused this message.

[filiprem-clickup]

To whom it may concern, I captured this error in the wild right now (Sep 2024) but it seems to be transient and auto-recover after a short time.

~ $ aws ssm start-session --profile prod --region $REGION --target $INSTANCE --document-name AWS-StartInteractiveCommand --parameters {"command": ["sudo -iu ubuntu bash -l"]}

Starting session with SessionId: my@id-rpji5kgwvw2dihh4mx3t5uqq2m

SessionId: my@id-rpji5kgwvw2dihh4mx3t5uqq2m : Plugin with name InteractiveCommands not found. Step name: InteractiveCommands
~ $ 
~ $ aws --version
aws-cli/2.13.34 Python/3.11.6 Darwin/23.6.0 exe/x86_64 prompt/off
~ $ session-manager-plugin --version
1.2.497.0

[yui-har]

In my case, I have 3 services in my cluster. I can connect to one of them, but not the other two.

[yui-har]

Around July 10, I changed the EC2 architecture and the ECR Docker images from x86_64 to arm64. I think it was around that time that I was unable to connect.