I used API gateway lambda function with proxy integration and used rest sharp to call http endpoints, however it is returning the response by calling the lambda function, but in API gateway getting empty response and status is 200. how to fix this.
@RahulNath
Жыл бұрын
Hard to tell without seeing the code in place Srini. If you have done all the configuration/setting as in this video, it shouldn't differ how you are consuming the API - Did you try from the AWS console invoking the function?
@jagkoth
2 жыл бұрын
Microsoft MVP explaining AWS API… ohhhh the ironyyyyy 😁
@RahulNath
2 жыл бұрын
Last I checked .NET is still Microsoft's 😆Hope you liked the video.
@pardhasaradhivasamsetty7693
Жыл бұрын
Thank you so much. It is helping a log.
@RahulNath
Жыл бұрын
Glad to hear that
@venkkatt23
2 жыл бұрын
Informative. Please upload videos on JWT, cookies and Claims in the .net core series.. I feel only that this is missing.
@RahulNath
2 жыл бұрын
Thank you for the feedback - I have it in my list, but not sure how soon I will get to it. Haven't been working much on those sides recently.
@saravanann1109
2 жыл бұрын
Very informative. Thanks for sharing ❤️
@RahulNath
2 жыл бұрын
You are so welcome. Hope you are enjoying the series bit.ly/aws-net-series
@saravanann1109
2 жыл бұрын
@@RahulNath I am watching all the video in this series. Your videos helps me to learn quickly.
@RahulNath
2 жыл бұрын
@@saravanann1109 Great to hear that. In case you haven’t checked out before www.udemy.com/course/aws-lambda-dotnet/?couponCode=AWS-LAMBDA-JULY
@shenanigans917
Жыл бұрын
Can you please not skip over creating the Dynamo DB tables? I don't know how to do that and now nothing works.
@RahulNath
Жыл бұрын
I cover DynamoDB introduction in detail in this blog post/video here www.rahulpnath.com/blog/aws-dynamodb-net-core/ Hope that helps you understand that part better. Do let me know if you have any questions.
@Owi627
Жыл бұрын
When I test my lambda it keeps saying "Unable to locate property for key attribute ID" how can i fix?
@RahulNath
Жыл бұрын
Hard to tell why without seeing it, hope you were able to resolve it?
@piyalibasak6886
Жыл бұрын
@rahul nath can you please upload websocket api in api gateway using lamda
@RahulNath
Жыл бұрын
Hey Piyali, Can you provide more details on that - What are you trying to achieve?
@piyalibasak6886
Жыл бұрын
@@RahulNath you have uploaded two video regarding api gateway.https api and rest api. I am requesting you please make a video on websocket api using api gateway with lamda
@RahulNath
Жыл бұрын
@@piyalibasak6886 Ah yes, thank you for clarifying! Sure will try and do a video around that.
@chromosome24
Жыл бұрын
I am always impressed at how much effort and time one needs to invest into AWS to implement the simplest goddamn feature. The platform is an insanely over-engineered maze of cluttered bullshit.
@RahulNath
Жыл бұрын
What did you find extra effort in this case? The AWS Function URLs makes it much more simpler (with reduced functionality though) www.rahulpnath.com/blog/function-urls-in-aws-lambda-dotnet/
@chromosome24
Жыл бұрын
@@RahulNath It's AWS's disconnected UX. It's like pulling teeth to do the simplest task. For example, say I want to perform URL rewrites on a redirect to my API gateway. It takes longer for me to setup my api gateway to do something as simple as access query string from within a lamda function than it does for me to just role my own node and have it working out of the box. Why? Well because you have to navigate page after seemingly unrelated page to get to the page to do the thing that allows you to do the thing (I'm looking at you query string mappings); Absolutely no implicit contextual information is given at any stage. They just assume your know their design intent. Piggy packing on the same example, here's how AWS could improve that experience. Ask the question where users will come to the realization that they can't access query params from their lamda function? In the freaking code dialogue on the lamda function page. So, at the very least provide a link in the same view that explicitly indicates "This is were you can add query string mappings so that your can access them with in your lamda code", and including any other task that may be needed to unblock functional development. Simple and clear and doesn't burden the user with having to google, rummage through outdated documentation, or watch an hour long youtube video. Grant it, not all AWS services have such dysfunctional UX, but it's enough to be pain for sure.
@finlaycaven4683
2 жыл бұрын
քʀօʍօֆʍ
@RahulNath
2 жыл бұрын
Not sure what that means Finlay 😀
@vash9197
2 жыл бұрын
Rahul, thank you for your detailed tutorial! All worked fine for me except using environmental variables in Test stage. When I tried to change Lambda function name to $(stageVariables.env)user-service-lambda-rest-api in Integration Request window at video frame 31:17, I had the following error: "1 validation error detected: Value 'arn:aws:lambda:ap-southeast-2:809325108131:function:user-service-lambda-rest-api$(stageVariables.env)' at 'functionName' failed to satisfy constraint: Member must satisfy regular expression pattern: (arn:(aws[a-zA-Z-]*)?:lambda:)?([a-z]{2}((-gov)|(-iso(b?)))?-[a-z]+-\d{1}:)?(\d{12}:)?(function:)?([a-zA-Z0-9-_]+)(:(\$LATEST|[a-zA-Z0-9-_]+))?" BTW, when I was learning your tutorial about HTTP Gateway API (kzitem.info/news/bejne/lWl6t6FoiJSIhoo), I had a similar problem with env variables, when I tried to change Lambda Function name in Edit Integrations window at video frame 36:13: "AWS ARN for integration must contain path or action." I have no idea how to fix these errors. I wonder if you would be able to advise me what I did wrong. Thank you.
@RahulNath
Жыл бұрын
Hope you were able to fix the issue?
@Dunkelseele
Жыл бұрын
@@RahulNath No it seems using stageVariables in API Gateway to substitute or enhance integration paths is currently not supported. I face the exact same error @Va Sh described and could not find a solution to it yet. Most documentation or tutorials are old and it seems something about this was changed recently. Maybe you could check if it still works for you?
@RahulNath
Жыл бұрын
@@Dunkelseele @vash9197 Confirmed just now, this is working fine. To specify the stage variable you need to use {} instead of () . For e.g. myapp-${stageVariables.test} Hope that helps.Here is the relevant docs docs.aws.amazon.com/apigateway/latest/developerguide/amazon-api-gateway-using-stage-variables.html
Пікірлер: 29