Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't seem to authenticate #91

Open
thestumonkey opened this issue Oct 23, 2016 · 5 comments
Open

Can't seem to authenticate #91

thestumonkey opened this issue Oct 23, 2016 · 5 comments

Comments

@thestumonkey
Copy link

When running grunt deploy it says
Warning: AWS API request failed, check your AWS credentials, region and permissions are correct. Use --force to continue.

Now I have correct .aws credentials as I can get my list of lambda functions via the aws cli. Can this message be more accurate? is there a way to debug the request to find out what's wrong? What else can I check?

@Tim-B
Copy link
Owner

Tim-B commented Oct 23, 2016

Is there anything more to the message? It should also display the status code and error message: https://github.com/Tim-B/grunt-aws-lambda/blob/master/utils/deploy_task.js#L130

@thestumonkey
Copy link
Author

screen shot 2016-10-25 at 16 29 05

@Tim-B
Copy link
Owner

Tim-B commented Oct 29, 2016

Try running it with the --verbose flag, I think it will display the other log which is there then.

@thestumonkey
Copy link
Author

screen shot 2016-11-08 at 13 15 44

@bsheen
Copy link

bsheen commented May 1, 2017

@thestumonkey Did you get anywhere with this? aws cli is seeing the credentials and returning data from "aws lambda list-functions". However, when I try to deploy using lambda_deploy I get the same error you were seeing. What am I missing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants