How to Deploy RESTful API with .net framework 4.5 in AWS Lambda

0 votes
I have been trying to anticipate the issues I may face when trying to migrate an existing API developed in .NET framework 4.5 and deployed in an IIS to a serverless architecture based on AWS Lambda.

Currently, the API is divided in: Controller (entry point), service (buz logic) and repository (basically LINQ), and of course some DTO and DAO's, nothing fancy. In addition, I have got some dependencies to external libraries but I don't know if that really matters.

Here is the thing: As I could see when configuring my Lambda, it only accepts .Net Core applications. Ouch! Then, is it necessary to migrate to .Net Core? If it is, can anyone tell me how much development that requires considering my set up?
Sep 4, 2018 in AWS by bug_seeker
• 15,350 points
68 views

1 answer to this question.

0 votes

Is it necessary to migrate to .Net Core?

Yes, as Lambda runs on Linux.

If it is, can anyone tell me how much development that requires considering my set up?

You will need to pay specific attention to the dependencies to external libraries, as they need to support .NET core and might add a substantial load time to your lambda function.

If you have an existing .NET API developed in 4.5, I would strongly advise against trying to migrate the whole API. Lambda's pay-for-what-you-use model is very attractive, but largely incompatible with ASP.NET MVC/WebApi's server model.

answered Sep 4, 2018 by Priyaj
• 56,920 points

Related Questions In AWS

0 votes
1 answer

how to access AWS S3 from Lambda in VPC

With boto3, the S3 urls are virtual by default, ...READ MORE

answered Sep 28, 2018 in AWS by Priyaj
• 56,920 points
2,110 views
0 votes
1 answer

How to find out current region with AWS Lambda?

You can read the AWS_DEFAULT_REGION environment variable and use ...READ MORE

answered Dec 20, 2018 in AWS by Archana
• 5,560 points
498 views
0 votes
1 answer
0 votes
1 answer
0 votes
1 answer
0 votes
1 answer