AWS Lambda Getting Started: Deploy Your First Function

published on 02 March 2024

Getting started with AWS Lambda allows you to run code without managing servers, focusing on your code while AWS handles the rest. Here's a quick guide to deploy your first function:

  • No Server Management: AWS manages server capacity, maintenance, and scalability.
  • Cost-Effective: Pay only for the compute time you consume.
  • Automatic Scaling: Handles few requests to millions without any manual intervention.
  • High Availability: Functions are run across multiple locations for resilience.


  • An AWS account and a basic understanding of JavaScript or Python.

Steps to Deploy Your First AWS Lambda Function:

  • Set Up AWS Environment: Sign into AWS Console, create an IAM role.
  • Create Your First Lambda Function: Choose a runtime, author function code, configure execution role, and deploy.
  • Test The Function: Create a test event, invoke the function, and review the results.
  • Monitor Metrics: Use CloudWatch to monitor function invocations, errors, and performance.
  • Clean Up: Delete the function, log group, and IAM role to avoid unnecessary charges.

This guide offers a straightforward path to deploying and managing a serverless 'Hello World' function with AWS Lambda, suitable for beginners.

Sign up for an AWS account

If you don't have an AWS account yet, you'll need to make one. Here's how:

  • Visit and click Create an AWS Account.
  • Just follow the steps on the screen. You'll have to confirm your phone number as part of the process.

Your new AWS account might take up to 24 hours to get ready. You'll get an email once everything is set up and you're good to go.

AWS Free Tier

This tutorial mostly uses services that are free under the AWS Free Tier. This means you can try things out without paying, up to a certain point each month.

If you go over those limits, you'll start getting charged, but we'll stay within the free limits for this guide. Just something to keep in mind if you find yourself using AWS a lot.

Now that we've got the basics out of the way, let's move on to making your first Lambda function!

Step 1 - Set Up AWS Environment

Getting started with AWS Lambda is straightforward. Here's how to dive in:

  • Head over to and sign in with your AWS details.
  • At the top of the page, there's a search bar. Type in "Lambda" and press enter.
  • You'll see "Lambda" pop up in the search results. Click on it to go to the Lambda section.

This area lets you create and manage your Lambda functions. It's pretty user-friendly and even has a built-in editor for writing your code.

Create IAM Role

Your Lambda function needs a special kind of permission to run, which is where IAM roles come in. Think of an IAM role as a set of rules that tells AWS what your function can and can't do.

Here's how to set one up:

  1. On the Lambda page, look for "Roles" in the menu on the left and click it.

  2. Hit the "Create role" button.

  3. Choose "Lambda" from the list of services that can use this role.

  4. Click "Next".

  5. Now, find and select "AWSLambdaBasicExecutionRole". This gives your function the basic permissions it needs.

  6. Name your role something like "my-lambda-role" and click "Create role".

Now you've got an IAM role ready for your Lambda functions. This is all about making sure your function has the right access without giving it too much power, which keeps things secure.

Step 2 - Create Your First Lambda Function

Choose Runtime

AWS Lambda lets you write your functions in many programming languages. Here are a few:

  • Node.js - This is JavaScript for server-side stuff. You can use versions from 6.10 up to 18.x.
exports.handler = async function(event) {
  console.log("Hello world!"); 
  • Python - A beginner-friendly language. AWS Lambda supports Python 2.7 and 3.9.
def handler(event, context):
  print("Hello world!")
  • Java - Good for more complex stuff. You can use Java 8 & 11.

  • .NET - For those who like C# and .NET. It works with .NET Core 3.1 and .NET 6.

We'll go with Node.js 14.x for our example. It's up-to-date with the latest JavaScript features.

Author Function Code

Here's a simple piece of code that says "Hello world!":

exports.handler = async function(event, context) {

  console.log("Hello world!");

  return {
    statusCode: 200,
    body: JSON.stringify({
      message: "Hello world!" 


What's happening here:

  • exports.handler - This is where our function starts.

  • async function - This means our function can do things one step at a time.

  • event - The information sent to the function.

  • context - Details about the function and where it's running.

  • console.log - This writes out "Hello world!" so we can see it in the logs.

  • The function sends back a message saying "Hello world!" with a status of 200, meaning everything's okay.

Configure Execution Role

Let's use the IAM role we created before for our function:

  1. In the Lambda console, find "Existing role" under Permissions.

  2. Choose the role we made, like my-lambda-role.

This lets our function use other AWS services it might need.

Deploy The Code

Now, let's put our code on AWS Lambda:

  1. Click "Deploy" at the top right of the console.

  2. You'll see a message that your code is ready to go!

Our function is now up and running. Let's see how to test it next!

Step 3 - Test The Function

Testing your Lambda function is like giving it a practice run to see if it does what you expect. Let's set up a simple test.

Create a Test Event

  1. Go to your function's page in the Lambda console and find the Test tab.
  2. Click on Create new test event.
  3. Name your test event something like myFirstTest.
  4. Choose the Hello World template for a straightforward JSON example.
  5. Hit Create.

Now, you've got a test ready to go.

Invoke the Function

To see your function in action:

  • Hit the Test button in the Test tab.
  • Look below for the results.

Here's what to expect:

  • Execution result: This tells you if the test worked or not.
  • Function logs: Here, you'll find the output from your function, like the "Hello world!" message.
  • Execution details: This shows how long it took and the resources used.

Seeing your "Hello world!" message means everything's working great!

Check CloudWatch Logs

For a deeper dive into your function's activity, check out CloudWatch Logs.

Here's how:

  • Visit the CloudWatch console.
  • Click on Log groups.
  • Find and select the log group named after your function, like /aws/lambda/your-function-name.
  • Open the most recent log by clicking its name.

These logs provide a detailed record of your function's runs, useful for troubleshooting or understanding its performance.

Now you're all set with running and checking your Lambda function!

Step 4 - Monitor Metrics

CloudWatch is a tool from AWS that helps you keep an eye on how your Lambda functions are doing. It's like having a dashboard that shows you everything from how often your function is used to whether it's running into any problems. Here's a simple breakdown of what CloudWatch can show you:


This is about how many times your function is called. If you see big changes here, it might mean something's up.

  • Errors - Counts when your function doesn't work as expected. It's important to check this.
  • Throttles - Shows if AWS had to slow down your function to keep things stable.
  • Duration - Tells you how long it takes for your function to do its job. Longer times could mean a slowdown.


This tells you how many instances of your function are running at the same time. This info can help you plan better.

  • Provisioned concurrency - These are instances set up in advance, ready to go immediately.


Gives you the lowdown on the tech stuff your function uses, like CPU and memory.

Keeping an eye on these details with CloudWatch helps you:

  • Catch and fix problems early.
  • Understand how much power and space your functions need.
  • Keep your functions running smoothly and efficiently.
  • Make sure your system can handle the work without any hiccups.

For instance, if you start seeing more errors, you might need to look closer at your function's logs or maybe there's something in your code that needs tweaking.

CloudWatch also lets you set up your own dashboards, alarms, and get notifications, so you're always in the know.

Spending a bit of time each day checking on your Lambda functions with CloudWatch can save you a lot of hassle. It's a good way to spot issues before they affect your users and keep everything running smoothly.


Step 5 - Clean Up

After you're done experimenting with your example function, it's a smart move to delete it and any related resources. Doing this helps you avoid any unnecessary costs.

Here's how to tidy up:

Delete the Lambda Function

  • Head over to the Functions page in the Lambda console.
  • Click on the function you made before.
  • Click Actions, then Delete.
  • A box will pop up asking if you're sure. Type in delete and hit Delete.

Delete the Log Group

  • Visit the Log Groups page in the CloudWatch console.
  • Look for the log group for your function (like /aws/lambda/my-function).
  • Click Actions, then Delete log group(s).
  • Say yes to confirm you want to delete it.

Delete the IAM Role

  • Go to the IAM Roles page in the IAM console.
  • Find the execution role you made (something like my-lambda-role).
  • Hit Delete, type the role name to make sure, and choose Delete.

You can also make things easier by using AWS CloudFormation templates and the AWS CLI to set up and remove functions and resources automatically.

Cleaning up after you're done is important to avoid extra charges and keep your workspace neat for new projects.


Great job on setting up your first AWS Lambda function! You've just started using a powerful tool that lets you run applications without worrying about the servers they run on.

Here's what you've done:

  • Got the basics of AWS Lambda and why going serverless is helpful.
  • Set up a role for your function and made your first Lambda function.
  • Ran a simple Node.js function and checked it worked by testing it.
  • Looked at the results in the console and kept an eye on how it's doing with logs and metrics.
  • Removed everything after to avoid extra costs.

Now, you know enough to start using Lambda for different projects like:

  • Handling file uploads
  • Making chatbots and skills for Alexa
  • Setting up serverless schedules
  • Supporting REST APIs
  • Dealing with events
  • Managing tasks that need a lot of computing power
  • Trying out new ideas quickly

What to do next:

  • Learn how to add more code and packages for bigger projects
  • Use S3 and DynamoDB to trigger functions
  • Try building apps with the Serverless Framework
  • Get better at monitoring and fixing issues with Dashbird

Check out the Lambda documentation for more detailed information.

Feel free to play around with these tools through tutorials, examples, and your projects. Practicing is the best way to really get how Lambda works.

If you have questions, just ask in the comments! We're here to help you keep getting better at building things without servers using AWS Lambda.

Additional Resources

If you're looking to dive deeper into AWS Lambda, here are some handy links:

  • AWS Lambda Documentation - This is where you can find all the nitty-gritty details about Lambda. It's packed with info and is the go-to place for anything technical.
  • AWS Lambda FAQs - Got questions? This page probably has the answers, covering everything from what Lambda does, how it's priced, and more.
  • AWS Lambda Best Practices - Here, you'll find useful tips on how to make your Lambda functions run better and smoother.
  • AWS Lambda Tutorials - These step-by-step guides are great for learning how to use Lambda with other AWS services like DynamoDB, S3, and API Gateway.
  • Serverless Architectures with AWS Lambda - This book dives into how to build apps that don't need a server using Lambda. It's full of examples and patterns to learn from.

Next Steps

Ready to get even better with Lambda? Try these ideas:

  • Work on making your Lambda functions run faster, use less money, and be easier to keep an eye on.
  • Build a website without a server using Lambda, API Gateway, DynamoDB, and other AWS tools.
  • Set up a system where Lambda functions sort through data, triggered by updates in S3 or messages in SQS.
  • Use Lambda with AWS Step Functions to manage multiple functions in one go.
  • Get your Lambda functions to update themselves through a CI/CD pipeline.
  • Move an existing app or API over to a serverless setup with AWS.
  • Learn the best ways to check your Lambda functions with different testing methods.
  • Explore advanced Lambda features like setting up ahead of time, connecting to a private network, using Lambda layers, and more.
  • See how Lambda works with other tech like Docker, Kubernetes, and Terraform.

There's so much you can do with Lambda. Start with small projects, learn by doing, and enjoy the process.

What is the first step in getting started with AWS Lambda?

Starting with AWS Lambda is pretty straightforward. Here's what you need to do first:

  • Go to the Lambda console and create a new function.
  • Give your function a name and pick a programming language (like Node.js or Python).
  • Write a simple piece of code that your function will run.
  • Set up any triggers (events that will make your function run) and permissions.
  • Deploy your function to Lambda.
  • Test it right there in the console.

This process lets you quickly get a Lambda function up and running without dealing with server or infrastructure management. The console guides you through the setup.

How do I deploy a function to AWS Lambda?

To get your code onto Lambda, you have a few choices:

  • Use a .zip file: You can zip your code and any libraries it needs, then upload this directly in the console.
  • Use Amazon S3: If you prefer, upload your zip file to an S3 bucket, and Lambda can use it from there.
  • Use the AWS CLI: The Command Line Interface is a tool for managing AWS services from your computer, and you can use it to deploy Lambda functions.
  • Use AWS SDKs: These are tools for programming languages that let you work with AWS services, including deploying Lambda functions.

Basically, you pack your function and its dependencies into a zip file and upload it using one of these methods.

How do I trigger AWS Lambda functions?

Lambda functions can be triggered in several ways:

  • Directly: You can manually trigger a function using the console, AWS CLI, SDKs, or the Invoke API.

  • Event source: Connect your function to another AWS service like S3 or DynamoDB, and it will run automatically when certain events happen.

  • HTTP request: You can make your function respond to web requests by using it with API Gateway.

  • Scheduled events: Use CloudWatch to have your function run on a schedule, like once a day or every hour.

In short, you can trigger Lambda functions manually, through other services, via web requests, or on a schedule.

How long does it take for AWS Lambda function to cold start?

Cold starts in Lambda functions are pretty rare, happening in less than 1% of the time. When they do happen, it might take anywhere from a fraction of a second to a couple of seconds for your function to be ready. The exact time can depend on the programming language, the size of your code, and other factors.

But, you can make cold starts faster by:

  • Making your code smaller and simpler.
  • Using container images for quicker starts.
  • Setting up provisioned concurrency to have instances ready to go.
  • Keeping functions warm by invoking them regularly.

While cold starts can add a bit of delay, there are ways to make them less of an issue.

Related posts

Read more