In this video, we are going to do our hands on lab, which is the using animals on the trigger to invoke
a lambda function and persist on Dynamo db.
So a double Islam that integrates with other services to invoke functions or take other actions.
So as you remember that we will using the animals in history to trigger invoke lambda function and persist
on dynamic DB.
Here you can find the architecture that we will implement in this section.
So basically we will follow these steps.
We will upload object into bucket and after that these will be asynchronous to invoke our lambda function
in response to resource lifecycle events.
And after that you will save uploaded file metadata in Dynamo DB.
Also, you can follow the slide in here.
In the client application, we will upload object in Amazon S3 bucket and bucket will be load V to objects
and when we upload object into the bucket, this will be file and even to the lambda function which
is the object uploaded event and this event trigger and invoke lambda function asynchronously.
And in the lambda function code we will perform our business logic.
This will be saved into the uploaded file metadata into the Dynamo DB database and response back to
the lambda.
Since it is a asynchronous flow, there is no synchronous response to the client application.
We will check the uploaded event stored in Dynamo DB or not from the management console.
Okay.
As you know that when we implement any architecture on a place, we have two main steps.
The first part is create infrastructure on a cloud, and the second part is develop the actual code
for interacting S3 and dynamic DB.
So we will start with the first step.
Let's create these architecture infrastructure on the cloud, and after that we will write lambda function
code.