API Gateway 403 with IAM authorization enabled

Question

I've created an API on API Gateway and without authentication I'm able to access the API without any issues.

I then enabled IAM authentication and now I get 403 on Postman and this message:

{
    "message": "Forbidden"
}

On Postman I'm sending the authorization as AWS Signature and still get the same error.

On AWS I'm have full access to API Gateway since I have AdminFullAccess permissions.

Any ideas?

Thanks

When using AWS Signature, did you populated `AccessKey` , `SecretKey` and potentially `SessionToken` ? — brushtakopo, Mar 02 '23 at 16:52
Are you sure the Path is valid? You deployed the API from API Gateway Console? — brushtakopo, Mar 02 '23 at 17:01
what about the region and service in postman for AWS Signature? — brushtakopo, Mar 02 '23 at 17:02
The path is valid. If I remove the authentication it works fine. Yes deployed via the console. Yes it's filled as well. Region `eu-west-2` and service `execute-api`. — TheSQLGoat, Mar 02 '23 at 17:03
try using curl: `curl --request GET "your-endpoint" \ --user $AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY \ --aws-sigv4 "aws:amz:region:service"` — brushtakopo, Mar 02 '23 at 17:08
https://stackoverflow.com/questions/59932855/testing-aws-api-gateway-with-curl — brushtakopo, Mar 02 '23 at 17:12

score 0 · Answer 1 · answered Mar 02 '23 at 17:24

0

The request doesn't work on Postman because I have multiple profiles.

I got this working via awscurl and by specifying the profile.

answered Mar 02 '23 at 17:24

TheSQLGoat

1 Answers1