Building a Serverless ASP.NET Core Web API using AWS Lambda and Amazon API Gateway REST API
HTML-код
- Опубликовано: 30 мар 2023
- In this video, you will learn how to build a Serverless ASP.NET Core API using AWS Lambda and Amazon API Gateway.
Notion link - resonant-cement-f3c.notion.si...
Fixing CORS issue in .NET 6 - nodogmablog.bryanhogan.net/20...
Additional Watch
📺Building Serverless .NET APIs using AWS Lambda, Amazon API Gateway, and Amazon Cognito • Building Serverless .N... 
Наука
![Sean Rii, Karyon, Sharzkii - Taungule [My Love] (Official Music Video)](http://i.ytimg.com/vi/eJoMuypbSzQ/mqdefault.jpg)
This was super helpful and easy to follow. I made a couple mistakes that I think mostly revolved around not updating the handler name to reference my project name when deploying it, which took me down a deep rabbit hole of errors and posts (which also helped me discover a hidden authorization error with my user setup). But in the end, that helped me understand the configuration stuff quite a bit better.
This is an excellent tutorial. Very well done!
Great work, very very helpful. Thanks
Glad to hear that!
I found it a very nice tutorial, thank you
I found it very nice tutorial, very neat and simple.
Mr, thanks for share, helped me a lot.
Glad to hear that it helped you!
Very nice demo. It's cleared the concept in first attempt about api gateway and lambda integration. Thanks
Glad the video helped you!
Great tutorial. Works excellent with .NET Core8
Glad the video was helpful!
Great explanation, it's really very helpful to start 🙂
excellent 👌
Good Job
thankyou very much
thanks🤘
Very helpful! Can you go over how source control would fit in here? I want to record changes to my web apis in a repository but this video skips over that step.
Great video, one question, is it recommendable to convert your api madre with EF to lambda?
It all depends on how many requests you expect from your Lambda. If it is only a few hundreds a day, it is fine; however, if you have a big number of requests to Lambda, you will eventually have a high number of requests to Database. Because Lambda compute terminates after a certain period of idle time, connection pooling is not done, resulting in a large number of open database connections. This may cause timeouts, and the database might reach its maximum connection limit. So, either use EC2/ECS or RDS Proxy in such case.
so, if i only need integration with API Gatwey, does the deployment work?
Thank you. This is a great video introducing Lambda and API Gateway to .NET Web API developers. However, it is not quite clear to me why I would need the API Gateway if my APIs are working fine as a Lambda function over a function URL. What added benefits does API Gateway bring into play?
API Gateway provides a considerably broader set of functionality and is specifically designed to expose APIs. Furthermore, refer to this post to understand more -www.antstack.com/blog/aws-lambda-function-urls-vs-amazon-api-gateway/
i followed all the steps but still getting the Internal server exception when i run the API, please suggest
i did all the same process but still i am getting internal server exception, please suggest
can you make another video for post API?
You can create a POST action in the same .NET 6 API, it will work the same way as we are using proxy integration with proxy resources.
if the API is or will be a private API, can I use only URL Lambda? I mean, it is Ok to use this approach?
If you want to use the Lambda function publicly, then you can setup a new API Gateway and use the same Lambda function in backend. But, If you want to use Function URL feature along with private API Gateway with the same Lambda function in backend, then this doesn't seem easily doable because REST API uses LambdaEventSource.RestApi, while Function URL uses LambdaEventSource.HttpApi.
Publish to AWS lambda option is not showing in my .net 6 . I already used nudget but still getting problem please help me out.
You have to update csproj for that. May be you missed that part in the video. Please watch it again carefully.
I've followed every step and I still can't see the button to 'publish to aws lambda'
Did you update csproj file as instructed in the video?
Hellow friend,
i did all the steps and facing the "message": "Internal server error" in after integrating with API Gateway. how to solve this error. I am struggling with this error whole day. Can you help me to solve this?
Hello, here are some troubleshooting hints:
- In the following code, make sure you use HttpApi for Function URL and RestApi when using API Gateway: "builder.Services.AddAWSLambdaHosting(LambdaEventSource.HttpApi);"
- Make sure you provide your assembly name as Function Handler name.
- Verify that the API endpoint works locally before testing it on AWS.
Hope this should help!
same@@coderjony9694
if its serverless why uploading VS Solution?
We’re not uploading the solution. We are just uploading compiled binaries. That’s how .NET code works.
you failed to mention that i needed to install AWS Toolkit extension so that "Publish to AWS lambda..." shows up
I forgot, not failed 😀
@@coderjony9694 you should put a caption somewhere saying you need to install that toolkit and then create a video on how to set that up and connect your was account ;)