SessionManagerPlugin is not found while session-manager-plugin --version is successful

[matthieudesprez]

Hello,

I'm trying to automate a few aws cli commands through a raycast extension, but when running commands through nodejs execSync I get a weird behaviour.

For instance, if I try to run the following:

const commands = [
    `session-manager-plugin --version`,
    `which session-manager-plugin`,
    `which aws`,
    `aws ssm start-session --target i-xxx`,
]

const options = {
    shell: "zsh",
    encoding: 'utf8',
}

for (const command of commands) {
    console.log(command);
    const result = execSync(command, options as ExecSyncOptions);
    console.log(result);
}

It returns the following

11:44:26.907 session-manager-plugin --version
11:44:26.907 1.2.553.0
11:44:26.911 which session-manager-plugin
11:44:26.911 /usr/local/bin/session-manager-plugin
11:44:26.915 which aws
11:44:26.915 /usr/local/bin/aws
11:44:28.817 aws ssm start-session --target i-xxx
11:44:28.817 Error: Command failed: aws ssm start-session --target i-xxx

SessionManagerPlugin is not found. Please refer to SessionManager Documentation here: http://docs.aws.amazon.com/console/systems-manager/session-manager-plugin-not-found

So I'm a bit puzzled here why running aws ssm start-session would fail if session-manager-plugin is successful

I only have this outcome using execSync but I'd really like to understand how it's possible for this to happen

Thanks