Windows console: run AWS CLI command inside shell command error

Question

Hello,

I have installed on Windows 10, the AWS CLI, and try to make a .bat file with this command:

```
for /f "tokens=*" %%a in ('aws s3api list-objects-v2 --bucket pics-repository --query Contents[*].Key --max-items 10') do set _CmdResult=%%a
@echo result : %_CmdResult%
```
While this works when the inner command is a Windows one, in the above case I have the error: `No Windows console found. Are you running cmd.exe?`. I run this version of CLI : `aws-cli/2.11.0 Python/3.11.2 Windows/10 exe/AMD64 prompt/off`

Is this related to some sort of special environment created by CLI in Windows shell ? Can this work, or no AWS CLI can be ran like this (I had also this error with other CLI commands) ?

Thank you,  
Mihai ADAM

Answer

here are some ways i have found on another thread related to this:

use the aws.exe executable directly from the command line. For example, you could run the following command to list the objects in the pics-repository bucket:

aws.exe s3api list-objects-v2 --bucket pics-repository --query Contents[*].Key --max-items 10
Another way to work around this issue is to use the Invoke-Expression cmdlet in PowerShell. For example, you could run the following command to list the objects in the pics-repository bucket:

Invoke-Expression "aws s3api list-objects-v2 --bucket pics-repository --query Contents[*].Key --max-items 10"

Finally, you could also use the aws-cli.exe executable to run your batch file. This executable will create a Windows console and execute your batch file in the context of the AWS CLI. However, this executable is not officially supported by AWS, so you may experience some unexpected behaviour.

Answer

Hello,

After some investigations I found out that the solution would be to add the option `--no-cli-auto-prompt` to the AWS CLI  command:
```
for /f "tokens=*" %%a in ('aws s3api list-objects-v2 --bucket pics-repository --no-cli-auto-prompt --query Contents[*].Key --max-items 10 ') do set _CmdResult=%%a  
```
It seams that the blocking option in the CLI command (that waits for user input) is not well-understood by Windows cmd.  
  
Have a good day,  
Mihai ADAM

Windows console: run AWS CLI command inside shell command error

Relevant content