serverless-app | Using AWS Lambda with API Gateway | AWS library

Firehose uses lambda function to transform records before they are being delivered to the destination in your case OpenSearch(ES) so they are only used to modify the structure of the data but can't be used to influence CRUD actions. Firehose can only insert records into a specific index. If you need a simple option to remove records from ES index after a certain period of time have a look at "Index rotation" option when specifying destination for your Firehose stream.

If you want to use CRUD actions with ES and keep using Firehose I would suggest to send records to S3 bucket in the raw format and then trigger a lambda function on object upload event that will perform a CRUD action depending on fields in your payload.

A good example of performing CRUD actions against ES from lambda https://github.com/chankh/ddb-elasticsearch/blob/master/src/lambda_function.py

This particular example is built to send data from DynamoDB streams into ES but it should be a good starting point for you

Comments (and blank lines are treated as comments), in ruamel.yaml are currently (0.17) associated with a node that comes before it. In this case of a mapping comment occuring in a mapping is associated with the key.

So what you need to do is reassociate the comment with the new key. Doing

Lambda standalone from console

The event that you get in your lambda function from API, and the one used when you run the function from the console are different. The event from api passed to your function will have a fixed known format. But when you run the function from console, you are passing the event in the incorrect format, thus it all breaks.

You have to ensure that your event structure used when you run the code in console matches the event structure from the API format.

Lambda proxy integrations should only use POST, not GET. So it should be:

Yes, it can be done: what you need are sourcemaps

In my case I had my lambdas being compiled and bundled into 1 single index.js file under the dist folder. I shipped this along with a single .map file using webpack as a bundler.

Configuration is not proper for API creation in API-Gateway in the AWS SAM template. because SAM deployment uses lambda proxy integration by default that's why in method response, there are few values required which can not be set automatically using the above configuration. So I use open API specification where I defined Rest API configuration and it is working fine without any manual intervention after deployment.

Following configuration is fine.

What you seek is the "Mapping template" functionality of API Gateway. Unfortunately, there is no direct way to do it in the AWS SAM.

But there is a way you can achieve this by leveraging the Open API support inside the AWS SAM which has a subset of API Gateway extensions. (x-amazon-API gateway-integration.requestTemplates object)

This code is just a snippet from a CloudFormation template. CognitoUserPoolName and CognitoUserPoolClientName are strings which should be specified by you. One way of doing this is by passing them as parameters:

Accessing Storage is not supported with token obtained using B2C user flow or custom policy Reference: As u not able to create Storage account in your azure ad b2c tenant .you need to create storage in azure and You need to add the user in your B2C AAD to your current ADD as the guest to access the blob storage .

For example :the email of my B2C user is bowman@testbowmanb2c.onmicrosoft.com.

And for the operation of data, the user need this role:

For more details refer this SO Thread