Introduction to Amazon API Gateway avaliações

Junho L. · Revisado há over 9 years

cool stuff

Gabriel O. · Revisado há over 9 years

Du Y. · Revisado há over 9 years

OK

Nguyen Thu Hien T. · Revisado há over 9 years

Hemavathy B. · Revisado há over 9 years

It would be more helpful to show how to implement the details as well.

LIsa K. · Revisado há over 9 years

Daniel R. · Revisado há over 9 years

Michael S. · Revisado há over 9 years

Yogesh U. · Revisado há over 9 years

Michael C. · Revisado há over 9 years

Konrad P. · Revisado há over 9 years

Point 18: there is no "resource name" on the screen. Point 26 not clear. There is no “Allow” button. Screens not unto date with the current UI flow. Some screens show differently. Function is working fine as per test. But the REST URL is not working. It is giving internal server error. Does not seem I missed any step.

Rakesh K. · Revisado há over 9 years

Felix N. · Revisado há over 9 years

Michelle A. · Revisado há over 9 years

david b. · Revisado há over 9 years

steps are not matching with AWS console screen

sivakumar r. · Revisado há over 9 years

Overall the lab seems well designed. Step 18 was not aligned with the current UI in AWS for lambda. Step 22 was also missing a semicolon after the end of the json variable.

Erik C. · Revisado há over 9 years

Lalit R. · Revisado há over 9 years

Yu Q. · Revisado há over 9 years

The Lamdba code worked when tested in Lambda but When triggered from API Gateway it returned an error: Execution failed due to configuration error: Invalid permissions on Lambda function

Adrian D. · Revisado há over 9 years

Plinio B. · Revisado há over 9 years

Not up to date with current Lambda creation.

Chris S. · Revisado há over 9 years

I keep getting "{"message": "Internal server error"}" and I am not sure why. Instructions are not matching the screen - I couldn't find "Resource Name" , Only Function Name.

Vladimir R. · Revisado há over 9 years

Rich C. · Revisado há over 9 years

James F. · Revisado há over 9 years