AWS CLI not allowing spaces in string passed to flag value #9108
Replies: 1 comment 1 reply
-
|
This is not an AWS CLI limitation — it is a shell parsing issue. The AWS CLI fully supports spaces in flag values, but the shell must pass the value as a single argument. The error you see means the shell is splitting the string before it reaches AWS CLI. Use the quoting rules appropriate for your shell. On Bash / zsh (Linux, macOS, WSL): aws lexv2-models update-intent --description "Hello World" or equivalently: aws lexv2-models update-intent --description 'Hello World' On Windows PowerShell (recommended): aws lexv2-models update-intent --description "Hello World" or: aws lexv2-models update-intent --description 'Hello World' On Windows CMD, make sure you are using straight quotes (not smart quotes) and not escaping incorrectly: aws lexv2-models update-intent --description "Hello World" If the command still fails, double-check that:
In short: AWS CLI accepts spaces just fine — the issue is always how the shell passes the argument, not the CLI itself. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to execute aws cli command with flag --description "Hello World" but it fails because of the white space.
example command am trying:
aws lexv2-models update-intent --description "Hello World"the error I receive
Unknown options: World"Beta Was this translation helpful? Give feedback.
All reactions