Confusion over security tokens during make deploy

Open timcollie opened this issue 8 years ago • 1 comments

Am I right in my view that the keys needed for a make deploy to complete need to be a user with full access to lambda? I can't seem to get past the following error during the make deploy -

TracingConfig: { Mode: null } } The security token included in the request is invalid. => Retrying { [UnrecognizedClientException: The security token included in the request is invalid.] message: 'The security token included in the request is invalid.', code: 'UnrecognizedClientException', time: Wed Jan 03 2018 17:08:09 GMT+0000 (GMT), requestId: 'abf21363-f0a8-11e7-a226-4b1e45b4187b', statusCode: 403, retryable: false, retryDelay: 40.62163548078388 } Makefile:38: recipe for target 'deploy' failed make: *** [deploy] Error 1

I have tried various combinations of .aws entries, exported commandline variables and values within Makefile with no joy.

Jan 03 '18 17:01 timcollie

Yes, the tokens need to have full access to lambda.

One thing that comes to mind is to check that your credentials also support the AWS_REGION you are deploying to. How did you create and configure your aws cli?

https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html

Jan 03 '18 17:01 creichert