cfn-lambda | CloudFormation custom resource helper for Lambda Node.js | Cloud Functions library

I have two Cloudformation templates

• one which creates a VPC, ALB and any other shared resources etc.
• one which creates an elastic beanstalk environment and relevant listener rules to direct traffic to this environment using the imported shared load balancer (call this template Environment)

The problem I'm facing is the Environment template creates a AWS::ElasticBeanstalk::Environment which subsequently creates a new CFN stack which contains things such as the ASG, and Target Group (or process as it is known to elastic beanstalk). These resources are not outputs of the AWS owned CFN template used to create the environment.

When setting

Have been trying to setup an AWS pipeline following the tutorial here: https://docs.aws.amazon.com/lambda/latest/dg/build-pipeline.html

But the pipeline continously fails with below error logs:

Here are some of the actions, I tried already:

1. Granted full access of S3 to "cfn-lambda-pipeline" role associated with Cloud Formation and Code Pipeline Service Role.

1. Allowed public ACL access to S3 bucket.

Below is my buildspec.yml

Hello i am planning to run the cloudFormation stack that is preconfigured by aws here. It prompts me to fill out

• NeptuneBulkloadIAMRoleArn
• NeptuneClusterEndpoint
• NeptuneLambdaIAMRoleArn

But i don't know what to fill in there, can you help me out?

I'm looking to connect a Kinesis stream to a Lambda function via event source mapping, want to set the parallelization-factor value to any value between 1- 10 as suggested in the documention:

https://docs.aws.amazon.com/cli/latest/reference/lambda/create-event-source-mapping.html

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-lambda-eventsourcemapping.html#cfn-lambda-eventsourcemapping-startingposition

and an example at https://aws.amazon.com/blogs/compute/new-aws-lambda-scaling-controls-for-kinesis-and-dynamodb-event-sources/

The following command results in an error:

I hope you can help!

Goal

I am trying to configure the following szenario on AWS:

1. In AWC CLI: Call CloudFormation Template to create a new stack.
2. In Template: Call Lambda Function.
3. In Lambda Function: Connect to Aurora PostgreSQL Instance in RDS via pg module.
4. In PostgresSQL: Create a new database.

Short story

As soon as I add my Lambda Function to the default VPC it is not able anymore to send a response back to CloudFormation and the stack gets stuck in CREATE_IN_PROGRESS. It works when I delete the VPC from the configuration of the Lambda function. But then I can not connect to another component like the RDS database instance anymore. How to deal with this?

Long story

To make it work my first step was to manually connect to PostgreSQL and create a new database:

1. Configured the Default Security Group to allow ALL Inbound and ALL Outbound traffic. No worries, only for testing. I will change that later.
2. Added the Security Group to the RDS Instance to accept traffic from and to other components within the same VPC. Necessary for step 3.
3. Created a Cloud9 Environment to have access to a terminal in the VPC. Connecting to the PostgreSQL Database and creating a database works!

Now my goal was to create a new database via a Lambda function:

1. Manually created a new Lambda Function including a new role with basic Lambda authorization. Also added AdministratorAccess to the role. No worries, again only for testing. The Lambda function runs on Node.js 12.x with a 15 seconds timeout.
2. Packed my Lambda script and the pg module in a zip File and uploaded it. The script looks like this: