Thank sir but one doubt while we add path in Lambda during the edit you made node-api/index.handler ,from where you pick the node-api(path) can you please suggest me
Hi Welcome the node-api is the project root directory and the project is uploaded using same name and inside node-api its have index.handler I hope this will address your concern Thanks
Hi I hope you're doing well. Certainly, you can develop an API using any programming language of your choice. Once you have your API ready, you can upload it to a Lambda Function. To create an endpoint for your API, you can utilize the capabilities of the API Gateway. I will be sharing a new video soon that demonstrates how to create an API from scratch. Thank you!
if we already have an fully NodeJS/Express application developed, with all the routing, How can we upload that using this method, will we have to create a lambda function for each and every route ?
When deploying an existing Express application on AWS Lambda, you typically create a single Lambda function for your entire application, not necessarily one function per route. AWS Lambda functions are designed to handle specific functions or applications, and you can configure your Express application to work within a Lambda function. Here are the general steps: • Set up a new Lambda function in the AWS Management Console or using the AWS CLI. • Configure the function with an appropriate runtime, such as Node.js, since your Express app is likely written in JavaScript. • Bundle your existing Express application along with its dependencies into a deployment package. This package should include your package.json file. • Set up the handler for your Lambda function. The handler is the function that Lambda calls to start execution. In this case, it would be the entry point of your Express app. • If your Express app relies on environment variables, configure them in the Lambda function settings. • You might want to use Amazon API Gateway to manage and expose your routes as HTTP endpoints. This allows you to map API Gateway routes to specific Lambda functions or routes in your Express app. • Test your Lambda function locally using tools like AWS SAM CLI or other serverless development frameworks. • Debug any issues that may arise during the transition to the serverless environment. Remember that AWS Lambda functions handle individual events, so the Lambda function for your Express app should be capable of handling incoming HTTP requests and routing them internally to the appropriate Express route.
Thanks, very very helpful video
top video
Thanks
love you😁
Great video
Thanks!
Thank sir but one doubt while we add path in Lambda during the edit you made node-api/index.handler ,from where you pick the node-api(path) can you please suggest me
Hi
Welcome the node-api is the project root directory and the project is uploaded using same name and inside node-api its have index.handler
I hope this will address your concern
Thanks
Thanks, can we create an api as we do with express?
Hi
I hope you're doing well.
Certainly, you can develop an API using any programming language of your choice. Once you have your API ready, you can upload it to a Lambda Function. To create an endpoint for your API, you can utilize the capabilities of the API Gateway. I will be sharing a new video soon that demonstrates how to create an API from scratch.
Thank you!
@@indrasen715 we have not seen the video
thanks for video
Most welcome
thanks, it is helpful
You're welcome!
if we already have an fully NodeJS/Express application developed, with all the routing,
How can we upload that using this method, will we have to create a lambda function for each and every route ?
When deploying an existing Express application on AWS Lambda, you typically create a single Lambda function for your entire application, not necessarily one function per route. AWS Lambda functions are designed to handle specific functions or applications, and you can configure your Express application to work within a Lambda function.
Here are the general steps:
• Set up a new Lambda function in the AWS Management Console or using the AWS CLI.
• Configure the function with an appropriate runtime, such as Node.js, since your Express app is likely written in JavaScript.
• Bundle your existing Express application along with its dependencies into a deployment package. This package should include your package.json file.
• Set up the handler for your Lambda function. The handler is the function that Lambda calls to start execution. In this case, it would be the entry point of your Express app.
• If your Express app relies on environment variables, configure them in the Lambda function settings.
• You might want to use Amazon API Gateway to manage and expose your routes as HTTP endpoints. This allows you to map API Gateway routes to specific Lambda functions or routes in your Express app.
• Test your Lambda function locally using tools like AWS SAM CLI or other serverless development frameworks.
• Debug any issues that may arise during the transition to the serverless environment.
Remember that AWS Lambda functions handle individual events, so the Lambda function for your Express app should be capable of handling incoming HTTP requests and routing them internally to the appropriate Express route.
I am getting bad request with the same method which you show in the video "Internal server error"