aws-lambda-function | Simple code for extracting data | Cloud Storage library

This is not possible. When an AWS Lambda function is invoked, it will always invoke the same function, which is configured as the Handler Function.

You would need to add additional logic to the function and pass-across information in the event to help identify what sub-function you would like to call. The AWS Lambda function can then use an if statement to interpret the event and call the appropriate sub-function.

This problem was tricksy because there were two major interlocking problems - a seemingly excessive permissions requirement, and what struck me as a non-standard use of the ENTRYPOINT/CMD systems.

The Dockerfile that works is as follows:

All functions in Terraform starting with file take in the file path, not the contents.

There are 2 issues here:

1. You're using file to read a binary file - it only accepts UTF-8 text

2. You're using file when that is already handled by filebase64sha256 (the file prefix is the hint that this accepts a file path)

The documentation highlights both aspects:

This is similar to base64sha256(file(filename)), but because file accepts only UTF-8 text it cannot be used to create hashes for binary files.

Remove the call to file(...) and it should work:

The revoke_security_group_ingress() and authorize_security_group_ingress() calls in boto3 includes a Return field in the response:

Returns true if the request succeeds; otherwise, returns an error.

However, your code does not seem to be storing a response or examining its contents.

if you want to update lambda with a specific node run time version i think this should help, this uses aws cli ( use updated version of aws cli)

the parent lambda execute before finishing the execution of the child lambda

You are using async handler, so your function finishes before it has a chance to invoke the other function.

To overcome this you can wrap your code in the handler in new Promise as shown in the AWS docs.

First example

can I be sure that url will be defined correctly (i.e. that the second statement will occur after the first)?

Why yes, absolutely. These are just two regular lines of codes, you simply store two strings in two variables; of course they will be executed in order, there's nothing asynchronous here.

Second example

Using Typescript instead of Javascript helped me a lot to understand how async functions work. Here's your example in Typescript :

You can invoke an AWS Lambda function programmatically via the invoke() command:

Invokes a Lambda function. You can invoke a function synchronously (and wait for the response), or asynchronously.

The function can be passed a payload, which will be available to the Lambda function through the event parameter.

What that machines is expecting is wrong. In JSON any newline data inside a value must be escaped, and \n in the string is the correct way to do it. This is the fault of the receiver's expectations.

A "real" newline would result in an invalid JSON document and most parsers will flat-out reject it.

On the receiving end JSON deserializer can deal with \n encoded strings. If your receiver requires newlines it's broken and needs repairing. If you can't repair it then you're committed to sending busted up, malformed JSON-ish data that's not actually JSON and your broker is fully justified in trashing it.