Answer - B.
This is mentioned in the AWS Documentation.
AWS Lambda is a compute service that lets you run code without provisioning or managing servers.
AWS Lambda executes your code only when needed and scales automatically, from a few requests per day to thousands per second.
You pay only for the compute time you consume - there is no charge when your code is not running.
With AWS Lambda, you can run code for virtually any type of application or backend service - all with zero administration.
AWS Lambda runs your code on a high-availability compute infrastructure and performs all of the compute resources administration, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring and logging.
All you need to do is supply your code in one of the languages that AWS Lambda supports (currently Node.js, Java, C#, Go and Python).
Option A is incorrect since this is used to manage API.
Option C is incorrect since this would incur a higher cost for hosting.
Option D is incorrect since this is a messaging service.
For more information on AWS Lambda, please refer to the below URL-
https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
Based on the requirements mentioned in the question, the most appropriate service to use would be AWS Lambda.
AWS Lambda is a compute service that allows developers to run code without provisioning or managing servers. It is a serverless service, meaning you don't have to worry about managing the infrastructure required to run your code.
Node.js is one of the many programming languages supported by AWS Lambda, so porting the code onto AWS Lambda should be relatively straightforward.
Using AWS Lambda also ensures that cost is minimized since you only pay for the actual compute time used by your code, and not for any idle time when the code is not running. This is in contrast to services like AWS EC2, where you have to pay for the entire server instance regardless of how much of it you are using.
AWS API Gateway is a service that allows you to create, publish, and manage APIs for your backend services, and AWS SQS is a message queue service. While both of these services could be used in conjunction with AWS Lambda, they are not directly relevant to the requirement of porting Node.js code to AWS with the least amount of administrative headache and minimizing costs.
Therefore, the correct answer is B. AWS Lambda.
