old Inkdrop Documentation
  • Getting Started
    • 🚀Getting Started
  • FAQ
    • 📃FAQ
  • Core Concepts
    • 🧱Resource
    • 🔗Connector
    • 📦Wrapper
    • 📋Sidebar
    • 👩‍💻Code and Deployment
    • ⚙️Overriding Properties with the Codebox
  • Ressources
    • S3 Bucket
    • Lambda Functions
    • IAM Roles
    • API Endpoint
    • Fargate
    • Dynamo DB
    • RDS
    • SQS
    • SNS
  • Custom Code
    • Validating your cloud architecture
Powered by GitBook
On this page
  • Overview
  • Use Cases
  • Properties
  • Inputs and Outputs
  1. Ressources

Lambda Functions

PreviousS3 BucketNextIAM Roles

Last updated 1 year ago

Overview

AWS Lambda functions allow you to run code without provisioning servers. Lambda automatically scales capacity based on usage. The code runs in response to triggers. (for example HTTP requests)

Use Cases

  • Serverless web APIs

  • Data processing pipelines

  • Automated tasks in response to events like file uploads

Properties

  • Source: Here a docker image or a zipped file can be specified.

Note: if a file is specified a runtime and handler need to be specified.

Note: if a file is specified a runtime and handler need to be specified.

Properties that were left out on purpose.

  • Memory: The amount of memory allocated per invocation. Defaults is 128 MB.

  • Timeout: The max runtime per invocation before Lambda terminates it. Default is 10 seconds.

  • Concurrency: The number of concurrent executions reserved. Default is unlimited.

You can easily override these defaults by entering the desired values in the

Inputs and Outputs

Inputs

  • Invoke: Trigger the Lambda function via an HTTP request or event.

  • IAM Role: Determines which resources your function can access.

Outputs

  • Destination: Send the function's output to a destination like an S3 bucket.

code box