关于“Introduction to Amazon API Gateway”的评价

Junho L. · 已于 over 9 years前审核

cool stuff

Gabriel O. · 已于 over 9 years前审核

Du Y. · 已于 over 9 years前审核

OK

Nguyen Thu Hien T. · 已于 over 9 years前审核

Hemavathy B. · 已于 over 9 years前审核

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

LIsa K. · 已于 over 9 years前审核

Daniel R. · 已于 over 9 years前审核

Michael S. · 已于 over 9 years前审核

Yogesh U. · 已于 over 9 years前审核

Michael C. · 已于 over 9 years前审核

Konrad P. · 已于 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. · 已于 over 9 years前审核

Felix N. · 已于 over 9 years前审核

Michelle A. · 已于 over 9 years前审核

david b. · 已于 over 9 years前审核

steps are not matching with AWS console screen

sivakumar r. · 已于 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. · 已于 over 9 years前审核

Lalit R. · 已于 over 9 years前审核

Yu Q. · 已于 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. · 已于 over 9 years前审核

Plinio B. · 已于 over 9 years前审核

Not up to date with current Lambda creation.

Chris S. · 已于 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. · 已于 over 9 years前审核

Rich C. · 已于 over 9 years前审核

James F. · 已于 over 9 years前审核