aws-lambda-functions | AWS lambda functions - utilities | Cloud Functions library

I'm looking for a way to associate flow logs to the originating Lambda.
Since the new networking model for Lambdas' networking (announcing-improved-vpc-networking-for-aws) it seems this isn't possible anymore (since multiple Lambdas use the same ENI).
Is there a way to overcome this?

I've got this sample code below extracted from here to do recursion in Lambda.

In line 22 (return New Promise...), the function returns a promise back to Lambda to call the function itself (lambda-func). My question is if the first function still needs to wait for the promise to complete why the executions stops?

It's probably a beginners question, but I just don't understand well how Lambda can return and promise and complete at the same time. Shouldn't the first run have to wait for the recursive calls to finish its execution?

Any explanation would be a great help to understand this one :)

I am just getting started with Clojurescript. I wrote some clojurescript code to use the shared aws credentials file to initialize S3 client and list buckets . However my code does not work.

I have the following error message when my deployment script runs to deploy to aws lambda. I've updated the node version as shown in the screen shot below, it confirms I've changed node to version 12.x.

Not sure why I'm still getting this error message? :-(

error message

Error: deploying: eu-west-1: updating function config: InvalidParameterValueException: The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions.

deployment script

I want to test my lambda functions locally with Serverless Application Model (SAM) In the AWS docs they write :

SAM Local leverages the docker-lambda Docker images to run your code in a sandbox that simulates the Lambda execution environment.

I pulled the docker image on my computer. I could successfully run a simple Hello World Lambda Function.

Command to run Lambda function locally:

I have Lambda which was deployed to VPC.

This deploymens has next configs:

• VPC (192.168.0.0/16)
• Public Subnet A (192.168.32.0/20) has NAT Gateway and Route 0.0.0.0/0 to Internet Gateway
• Private Subnet A (192.168.48.0/20) has Route 0.0.0.0/0 to NAT Gateway
• Private Subnet B (192.168.64.0/20)

Lambda has own Securiy Group and references to "Private Subnet A" and "Private Subnet B"

I have strange problem: time to time Lambda doesn't have Internet Access. 3rd party service works normal.

One more strange thing that Lambda gets IP's like 127.0.0.1, 169.254.76.13, 169.254.79.1 instead of IP's from Subnets (192.168.48.0/20 and 192.168.64.0/20).

Error:

Im trying to follow the tutorial AWS Lambda Functions Made Easy - codeburst.

However I don't understand this code snippet:

I am completely new to AWS and serverless etc. To speed up development I would like the ability to debug my application locally.

Following this article Running and Debugging AWS Lambda functions locally I have attempted to achieve just that.

In Visual Studio Code when I run the debug configuration, the application exits instantly without error (A break-point is set on the declaration and initialisation of the 'content' variable). I am not sure I have the function name correct. I am trying to enter at the main 'handler' function defined in 'index.js' as:

I've created an empty AWS Lambda project with .net CORE :

Which basically all it yields is a .net core empty lambda function project :

But as it is now - it doesn't support Injection (DI) , since there is no startup file etc ...So basically it is ia .net core project without all its benefits.

However , Tony wrote about it: Add .NET Core DI and Config Goodness to AWS Lambda Functions" :

Basically what he did is to manually make the project support DI.

So I've created a ConfigurationService class :

ConfigureServices.cs