`aws ecs execute-command` keeps asking to use AWS CLI

[amw]

Describe the bug

Every time I use aws ecs execute-command (successfully) one of the messages it prints is:

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

This is confusing, because:

• it tells me to use AWS CLI while I am already using it
• it sounds as if it was installed in the process of running this command, but it was installed all the time

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

I would prefer this message to be skipped entirely. It is already followed by:

Starting session with SessionId: ecs-execute-command-XXXX"

If a message is necessary maybe it could be reworded to something like:

Found an installed Session Manager plugin.

Current Behavior

A rather confusing and chatty log is printed.

Reproduction Steps

exec aws ecs execute-command ...

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.24.26 Python/3.12.9 Darwin/24.4.0 source/arm64

Environment details (OS name and version, etc.)

macOS Sequoia

[RyanFitzSimmonsAK]

Hi @amw, thanks for reaching out.

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

This is the output of running session-manager-plugin to check for a successful installation. ecs execute-command runs this command to verify the plugin is installed before making the request. The explanation can be found here.

        # making an execute-command call to connect to an
        # active session on a container would require
        # session-manager-plugin to be installed on the client machine.
        # Hence, making this empty session-manager-plugin call
        # before calling execute-command to ensure that
        # session-manager-plugin is installed
        # before execute-command-command is made

If a message is necessary maybe it could be reworded to something like Found an installed Session Manager plugin.

Since this message is coming directly from the output of session-manager-plugin, rather than being CLI output, you'd probably have to cut an issue to https://github.com/aws/session-manager-plugin if you want this message changed.

Please let me know if you have any follow-up questions. Thanks!

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.