AWS Lambda gateway API gives error message

Question

I have created one API endpoint for lambda function, as - https://XXXXXXXXX.execute-api.us-east-1.amazonaws.com/XXXX/XXXXXXXXXXXX/ which is GET method.

While calling that endpoint from postman it is giving me

{ "message": "'XXXXXXXXX3LPDGPBF33Q:XXXXXXXXXXBLh219REWwTsNMyyyfbucW8MuM7' not a valid key=value pair (missing equal-sign) in Authorization header: 'AWS XXXXXXXXX3LPDGPBF33Q:XXXXXXXXXXBLh219REWwTsNMyyyfbucW8MuM7'." }

This is a screenshot of the Amazon Lambda Upload Site: https://i.sstatic.net/mwJ3w.png

I have Access Key Id & Secret Access Key for IAM user. I used it all but no luck. Can anyone suggest tweak about this.

There seems to be a problem with the Sigv4 signature. How are you generating the Authorization header? — RyanG
– RyanG, Commented May 10, 2016 at 19:24
I am able to solve this but got stuck into following problem - "message": "Credential should be scoped to correct service: 'execute-api'." This is a screenshot : i.sstatic.net/J5OvT.png Following is the format I used to create Authoraziation Header - AWS4-HMAC-SHA256 + Credential=AccessKeyId/timezoneArea/iam/aws4_request, SignedHeaders=content-type;host;x-amz-date, Signature=SecretAccessKey — Ashly
– Ashly, Commented May 11, 2016 at 5:55
Do anyone know how to create Authorization header for iam user with aws4_request & timezone us-east-1 — Ashly
– Ashly, Commented May 11, 2016 at 8:13

RyanG · Accepted Answer · 2016-05-11 18:16:26Z

16

If you're using the latest version of Postman, you can generate the SigV4 signature automatically. The region should correspond to your API region (i.e. "us-east-1") and the service name should be "execute-api"

answered May 11, 2016 at 18:16

RyanG

4,15227 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ashly Over a year ago

This actually solves the problem ryan. You have saved my couple of days. Thank you so much.

Vijay Gangatharan Over a year ago

Even after 7 years, still your answer helped me to resolve the issue

Ivaylo Novakov · Accepted Answer · 2018-06-27 09:14:03Z

14

This is not a solution but it has helped me more than once:

Double-check that you are actually hitting an existing endpoint! Especially if you're working with AWS. AWS will return this error if you don't have the correct handler set up in your Lambda or if your API Gateway is not configured to serve this resource/verb/etc.

answered Jun 27, 2018 at 9:14

Ivaylo Novakov

9558 silver badges20 bronze badges

1 Comment

user2779653 Over a year ago

that was it for me!

Collectives™ on Stack Overflow

AWS Lambda gateway API gives error message

2 Answers 2

2 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related