aws cli too few arguments error

[jhackGC]

Hi, when running this Orb command (setup), I'm getting this error:

aws configure set aws_access_key_id
$AWS_ACCESS_KEY_ID
--profile default
usage: aws [options] [ ...] [parameters]
To see help text, you can run:

aws help
aws help
aws help
aws: error: too few arguments

Thanks !

[s4ros]

did you provide the proper ENV variables within your CircleCI project's settings?

[lokst]

@jhackGC Could you check if AWS_ACCESS_KEY_ID is defined?

[jhackGC]

Hi, sorry the late response, The key and secret key were set yes, let me take a few screenshots and show it. I took a turnaround and I'm doing the connection manually, but If I can use an Orb, better. Thanks heaps for the answer <img width="1279" alt="Screen Shot 2019-09-17 at 11 28 52 am" src="https://user-images.githubusercontent.com/6415589/65057893-b55b2480-d949-11e9-9c3e-21305be7c8f3.png">

…

On Tue, 17 Sep 2019 at 11:24, Stella Lok ***@***.***> wrote: @jhackGC <https://github.com/jhackGC> Could you check if AWS_ACCESS_KEY_ID is defined? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#24?email_source=notifications&email_token=ABQ6JZPDSJAFU3QVZWSPUHTQKDSBLA5CNFSM4IWRIAGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64WQ2A#issuecomment-532244584>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQ6JZKIJ6IL4VH2UNMB4WDQKDSBLANCNFSM4IWRIAGA> .

[lokst]

@jhackGC Apologies for the late response!

Is this the command that is giving you the error? Would you mind rerunning the job with SSH and then running the same command in your SSH session to check the output?

aws configure set aws_access_key_id $AWS_ACCESS_KEY_ID --profile default

I recommend checking what the value of $AWS_ACCESS_KEY_ID is too. You could do that by running set -x before the above command.

[lokst]

Closing this due to inactivity.

[patsa]

@lokst
I can confirm this issue but not while using CircleCi. Instead I'm trying to implement an automated deployment through GitlabCI.
I'm currently using a Node 12.x image and install the aws cli through the following commands.

- apt install -y software-properties-common
- apt install -y python-dev
- apt install -y python-pip
- apt install -y groff
- apt install -y less
- pip install awscli
- aws configure set aws_access_key_id $live_id --profile default
- aws configure set aws_secret_access_key $live_key --profile default
- aws configure set region $region --profile default

When executing the last three commands I get the error message aws: error: too few arguments.
I can confirm that the variables are set. I used echo to display them and they were correct.

Any ideas what could be the issue here?

[patsa]

It seems to be because of the dollar notation.
If I try to execute the same command with a normal string, the command succeeds without any problems.

Any idea how to escape the dollar sign in a way to make the aws cli accept it?

[lokst]

@patsa Could you try adding set -x before the aws commands run so that you can confirm the actual command run?

[patsa]

@lokst
The output looks like this now:

++ echo '�[32;1m$ aws configure set aws_access_key_id "${live_id}"�[0;m'
�[32;1m$ aws configure set aws_access_key_id "${live_id}"�[0;m
++ aws configure set aws_access_key_id ''

and like this when written like in my original post:

 ++ echo '$ aws configure set aws_access_key_id $live_id --profile default'
 $ aws configure set aws_access_key_id $live_id --profile default
 ++ aws configure set aws_access_key_id --profile default

But the correct value is definitely set within the variable $live_id, as I confirmed by executing echo $live_id.

[lokst]

@patsa I'd recommend trying something like echo "live_id is $live_id" && aws configure set aws_access_key_id $live_id --profile default to be sure that the variable is set at the point the aws command is run

[deeptechs]

@lokst
I can confirm this issue but not while using CircleCi. Instead I'm trying to implement an automated deployment through GitlabCI.
I'm currently using a Node 12.x image and install the aws cli through the following commands.

- apt install -y software-properties-common
- apt install -y python-dev
- apt install -y python-pip
- apt install -y groff
- apt install -y less
- pip install awscli
- aws configure set aws_access_key_id $live_id --profile default
- aws configure set aws_secret_access_key $live_key --profile default
- aws configure set region $region --profile default

When executing the last three commands I get the error message aws: error: too few arguments.
I can confirm that the variables are set. I used echo to display them and they were correct.

Any ideas what could be the issue here?

@patsa maybe you can check the protected variables / protected branches in gitlab CI.
You can't use protected variables in unprotected branches. So maybe you don't really have your env variables.

[patsa]

@deeptechs That was actually the culprit. Thanks for mentioning it!