In this video, explore the functionality and operation of AWS Lambda and its integration into the AWS cloud.
- [Instructor] Lambda is a pretty interesting tool for helping you automate solutions in the AWS cloud and it shows up in a different number of locations inside of AWS. So we'll look at where it sits in the different services and then we'll look at Lambda itself. So under Services, let's go into S3 buckets. Now if I create a bucket, let's give it a name and we'll accept all the parameters and create the bucket. Going into the properties of the bucket, we can then actually look at what we can do with this particular bucket as control or security. Into Properties, let's scroll down and take a look at the option Events. These boxes are really great, big buttons. If I click Events, I can add a notification. Remember, notifications are also the security notification service. So we have some integration here, so we can actually go through and define from different events. Remember events are also CloudWatch. Now let's say I was actually concerned when somebody did something with the content in my bucket, maybe copying that information. What I can do is go through and say, when that happens, I actually want to be notified. I could be notified with the notification service as mentioned but I could bypass that and say call Lambda. When I select the Lambda function, then I would add in the function that I would have to create. The function can do anything that I want it to do. Now let's go over to Lambda and see where it sits under services for AWS and note it's under Compute because Lambda is actually a compute engine. You load the software into the service list compute engine, You don't get to see it. You just say, "Here's my function. "Here's the Ram and CPU and time I need "for the function to execute." Lambda says fine and then you call that function, for example, from say an S3 bucket. So going into Lambda, we have the ability of creating a function. Now I can author from scratch or maybe there's something already built and you can see scrolling down, there's a number of different functions that are created, that you can just grab and use for your particular environment, your particular condition that you want to match. If I'm going to author from scratch, then I'm going to have to give it a name. We'll call it copy S3. Now what's the runtime? What's the programming language that I want to use? Notice that you can even upload a custom runtime. Now if Lambda's going to operate in your account, you have to define permissions and you're going to assign temporary conditions for Lambda to actually execute this task. Now they make it kind of easy creating a role with basic permissions to just carry out what you want to have carried out but you might want to be more precise than that. So you might have an existing role that you've created in identity and access management. For now, we'll use the new role with basic Lambda permissions. Now we say, create function. Really, we're just starting the process. Now I can start deciding what I want to do. I can go through and define the triggers, the destination, whatever I need to do to have this function actually work. I don't want to use the designer. I can just edit the code based on the runtime that I've selected. Down at Basic settings, you can see there are some basic scenarios which we could edit and start defining the amount of memory and the memory and the CPU are joined at the HIP and actually how much time it's going to take the function. So I can do some pretty interesting things in defining this function to actually carry out tasks at AWS. So the purpose of Lambda, creating your custom automation to carry out any task you want of course, with security applied as well.
- Design principals
- Key operational areas
- Key AWS services
- Designing workloads with key managed services
- Using Lambda for operational readiness
- Managing operational health
- Responding to health events