Aws Lambda Functions

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Create and deploy serverless functions using AWS Lambda with event sources, permissions, layers, and environment configuration. Use for event-driven computing without managing servers.

Includes scriptsDevOps & Cloud
AI-generated overview

Guides creating and deploying AWS Lambda serverless functions with CLI, Node.js, SAM, Terraform, and layers.

What it does
This skill provides reference guides and templates for building and deploying AWS Lambda serverless functions. It covers basic AWS CLI creation, Node.js handlers, Lambda Layers for shared code, SAM and Terraform deployment, plus permissions, event sources, and environment configuration. It also ships a validation script and an API scaffold template.
When to use it
Use it when you need to create, configure, or deploy AWS Lambda functions for event-driven workloads such as API endpoints, scheduled jobs, file processing, or microservices. It suits teams working with AWS CLI, SAM, or Terraform who want practical deployment patterns.
Requirements
Requires an AWS account with credentials and the AWS CLI; some guides also need Node.js, Terraform, or the AWS SAM CLI. Network access to AWS is needed, and the skill ships an executable validation script plus a YAML template.

AWS Lambda Functions

Table of Contents

Overview

AWS Lambda enables you to run code without provisioning or managing servers. Build serverless applications using event-driven triggers, pay only for compute time consumed, and scale automatically with workload.

When to Use

  • API endpoints and webhooks
  • Scheduled batch jobs and data processing
  • Real-time file processing (S3 uploads)
  • Event-driven workflows (SNS, SQS)
  • Microservices and backend APIs
  • Data transformations and ETL jobs
  • IoT and sensor data processing
  • WebSocket connections

Quick Start

Minimal working example:

bash
# Create Lambda execution roleaws iam create-role \  --role-name lambda-execution-role \  --assume-role-policy-document '{    "Version": "2012-10-17",    "Statement": [{      "Effect": "Allow",      "Principal": {"Service": "lambda.amazonaws.com"},      "Action": "sts:AssumeRole"    }]  }'
# Attach basic execution policyaws iam attach-role-policy \  --role-name lambda-execution-role \  --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole
# Create function from ZIPzip function.zip index.jsaws lambda create-function \  --function-name my-function \  --runtime nodejs18.x \  --role arn:aws:iam::ACCOUNT:role/lambda-execution-role \  --handler index.handler \  --zip-file fileb://function.zip \// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Basic Lambda Function with AWS CLI [blocked]Basic Lambda Function with AWS CLI
Lambda Function with Node.js [blocked]Lambda Function with Node.js
Terraform Lambda Deployment [blocked]Terraform Lambda Deployment
Lambda with SAM (Serverless Application Model) [blocked]Lambda with SAM (Serverless Application Model)
Lambda Layers for Code Sharing [blocked]Lambda Layers for Code Sharing

Best Practices

✅ DO

  • Use environment variables for configuration
  • Implement proper error handling and logging
  • Optimize package size and dependencies
  • Set appropriate timeout and memory
  • Use Lambda Layers for shared code
  • Implement concurrency limits
  • Enable X-Ray tracing for debugging
  • Use reserved concurrency for critical functions

❌ DON'T

  • Store sensitive data in code
  • Create long-running operations (>15 min)
  • Ignore cold start optimization
  • Forget to handle concurrent executions
  • Ignore CloudWatch metrics
  • Use too much memory unnecessarily

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/aws-lambda-functionsat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal