Comments for Test the APIs

RichStone · March 8, 2020, 9:10am

The npx aws-api-gateway-cli-test works out just fine for the dev stage:

{
  status: 200,
  statusText: 'OK',
  data: [
    {
      ProductId: '456d7760-6119-11ea-ba0b-1f24cdb58353',
      UserId: 'eu-central-1:89e011d5-907a-4375-ba19-b7b9d4dca4e0',
      CreatedAt: 1583657175510
    }
  ]
}

but for the prod stage I get an empty data array:

{ status: 200, statusText: 'OK', data: [] }

This is my call to prod:

npx aws-api-gateway-cli-test \
--username='admin@example.com' \
--password='Passw0rd!' \
--user-pool-id='eu-central-1_c8D3g4hxv' \
--app-client-id='7bsormil1soo7e1mpgkrpk4c64' \
--cognito-region='eu-central-1' \
--identity-pool-id='eu-central-1:58e6270f-f45b-4fe0-a876-a6546350d6c5' \
--invoke-url='https://3sj48f1a8d.execute-api.eu-central-1.amazonaws.com/prod' \
--api-gateway-region='eu-central-1' \
--path-template='/products'

And this is my repo:

Appreciate any ideas on what could have happened

EDIT:
I’ve made some changes to the key schema that might have broken the implementation. Still, the discrepancy between the output between the prod and dev stages is a bit weird.

jayair · March 8, 2020, 9:01pm

Appreciate you sharing this!

chrisanderss0n · March 21, 2020, 6:03pm

403: Forbidden - I read the entire thread and tried all of the solutions suggested, and still got this error.

On a hunch based on some JSON issues I saw someone in the thread have I changed this:

--body='{"content":"hello world"}'

to this

--body='{}'

Was able to successfully hit my API with a 200 OK.

I can’t seem to format JSON in a way that the aws-api-gateway-cli-test will accept.

Yangba · March 28, 2020, 9:54am

Had same issue on windows. Fixed it by having body as
–body ‘{ ““content””: ““hello world””, ““attachment””:"“hello.jpg”" }’

rsturim · March 30, 2020, 4:26pm

Over and over I was getting 403s when running the npx aws-api-gateway-cli-test

CognitoIdentityCredentials is not authorized to perform: execute-api:Invoke on resource

I had to go back to the Policy Document and create a new policy with less stringent InvokeFunction Resources for that cognito role like this …

From

    {
        "Effect": "Allow",
        "Action": ["execute-api:Invoke"],
        "Resource": ["arn:aws:execute-api:us-east-1:*:8zXXXXh5/*/*/*"]
    },

to

    {
        "Effect": "Allow",
        "Action": ["execute-api:Invoke"],
        "Resource": ["*"]
    }

Really not happy about having to do this – but after 2 hours, I had no choice. Anyone have similar issues?

rsturim · March 30, 2020, 4:44pm

I found these comments very helpful and it resolved my issues …

https://github.com/AnomalyInnovations/serverless-stack-com/issues/112#issuecomment-317204545

You can check if the IAM Role has been set properly by going to your AWS Console

IAM -> Roles -> Cognito_notesAuth_Role -> oneClick_Cognito_notesAuth_Role_XXXXXXXXX -> Edit Policy -> JSON:

Just had to re-copy/paste of the code from the tutorial with the properly set app values as guided in the tutorial and it worked for me.

jayair · March 30, 2020, 11:20pm

Glad you figure it out. These are super annoying to deal with.

bunkscene · April 5, 2020, 9:33pm

This fixed it for me as well. Somehow my original policy edit did not get saved. Thanks for this tip.

jsumz · April 14, 2020, 12:46pm

Hi, when I run the cli test command, I got this info “Incorrect username or password.” Anyone has same issue? I used the same mock userName and password those mentioned in chapter.

Preben · April 20, 2020, 6:39am

Struggled with a 500 error for quite a while. I used the reserved keyword: name. Finally found the error by looking at the cloudlogs. In the future, I will use the cloudlog a lot more. It’s awesome!

jayair · April 25, 2020, 5:01pm

Can you double-check the Cognito IDs that you are passing in to the test command?

JMAWS · April 27, 2020, 5:50pm

Getting below error related to --body
Please help…

JMAWS · April 27, 2020, 6:05pm

Resolve by changing command
strong text --body “{"content":"hello world","attachment":"hello.jpg"}”

sriver7 · May 31, 2020, 6:47pm

I’ve been following the tutorial and am getting the following error:

    {
  status: 403,
  statusText: 'Forbidden',
  data: {
    message: 'User: arn:aws:sts::499676075121:assumed-role/Cognito_notesidentitypoolAuth_Role/CognitoIdentityCredentials is not authorized to perform: execute-api:Invoke on resource: arn:aws:execute-api:us-east-1:********5121:mn5osswo0a/prod/POST/notes'
  }
}

However, I am getting an ‘allowed’ permission when I test through the policy simulator.

Has anybody ran across the same issues or have any suggestions for me?
Thanks!

EDIT:
I was able to solve my issue. I had removed by accident :*: in the JSON that is provided at this step.

jayair · May 31, 2020, 8:31pm

Glad you figure it out!

tkim · May 31, 2020, 10:30pm

Just in case this helps anyone:

I had an issue where running the aws command (ex. aws cognito-idp sign-up...) was making the request hang (I could tell because i added the --debug option, which logs everything).

Solution: My VPN was blocking any requests to AWS. Turning off my VPN made it work.

antonioscardovi · June 3, 2020, 2:53pm

I’m getting the 500 error and I don’t think it’s the indentation. Here’s my repo, maybe I’m missing something?

antonioscardovi · June 4, 2020, 11:15am

I had to add admin access to lambda role. I don’t understand why it’s not working…

xioneks · June 10, 2020, 8:20am

Hi I’ve found a solution to the syntax problem for Windows 10 Powershell (this solution doesn’t work on cmd for some reason)

npx aws-api-gateway-cli-test --username admin@example.com --password Passw0rd! --user-pool-id YOUR_COGNITO_USER_POOL_ID --app-client-id YOUR_COGNITO_APP_CLIENT_ID --cognito-region YOUR_COGNITO_REGION --identity-pool-id YOUR_IDENTITY_POOL_ID --invoke-url YOUR_API_GATEWAY_URL --api-gateway-region YOUR_API_GATEWAY_REGION --path-template /notes --method POST --body '{\"content\":\"helloworld\",\"attachment\":\"hello.jpg\"}'

-The starting and ending quotation marks of {\"content\":\"helloworld\",\"attachment\":\"hello.jpg\"} needs to be closed with a single quote (') instead of (")
-There can be NO space in the content so it needs to be removed or replaced with an underscore (_)

Here’s the original from the guide for Windows for comparison:-

npx aws-api-gateway-cli-test --username admin@example.com --password Passw0rd! --user-pool-id YOUR_COGNITO_USER_POOL_ID --app-client-id YOUR_COGNITO_APP_CLIENT_ID --cognito-region YOUR_COGNITO_REGION --identity-pool-id YOUR_IDENTITY_POOL_ID --invoke-url YOUR_API_GATEWAY_URL --api-gateway-region YOUR_API_GATEWAY_REGION --path-template /notes --method POST --body "{\"content\":\"hello world\",\"attachment\":\"hello.jpg\"}"

P.S. why Microsoft, why?

chris-t · June 11, 2020, 4:39am

Hey! I’m getting this kind of error:
Authenticating with User Pool
Getting temporary credentials
Invalid identity pool configuration. Check assigned IAM roles for this pool.

If anyone has an insight, do let me know. I checked my IAM role and I’m pretty sure my YAML is perfect; I saw the posts above. I’m supposed to have my UnAuth and Auth role as the same thing, right?

Topic		Replies	Views
Deploy the APIs Chapter Comments	117	10565	May 15, 2021
Create a Cognito Identity Pool Chapter Comments	67	4376	January 3, 2021
Configure AWS Amplify Chapter Comments	29	5525	October 4, 2023
Debugging Serverless API Issues Chapter Comments	34	5011	August 8, 2018
Add a Create Note API Chapter Comments	251	17479	May 15, 2021

Comments for Test the APIs

Related topics