Does AWS Lambda charge for time an async .NET Core function is awaiting?

Question

AWS Lambda .NET Core functions have the ability to be defined as async entry point methods.

If I'm using "await" in my functions to wait for IO to respond, am I charged the full amount still?

What is the benefit of writing everything as async await in this scenario vs not using async/await?

Answer 1

Yes, you will be charged for 'awaiting' functions. Lambda will charge you for execution time of your program (e.g. until the function return is called).

From the billing perspective, there is no benefit to using async-await keywords here.

What these would do is potentially (depending on what it is that you are awaiting) fractionally reduce the load on underlying AWS infrastructure while these calls are running.