AWS Lambda: Difference between revisions

Revision as of 05:59, 1 December 2024

Revision as of 00:57, 2 December 2024

Line 12:

==Specification==

Each AWS Lambda instance is a [[OS-level_virtualisation|container]] created from [[Amazon Machine Image|Amazon Linux AMI]]s (a Linux distribution related to [[RHEL]]) and a configurable execution time. [[Node.js]], [[Python (programming language)|Python]], [[Java (programming language)|Java]], [[Go (programming language)|Go]],<ref>{{cite web |last=Munns |first=Chris |date=January 15, 2018 |title=Announcing Go Support for AWS Lambda |url=https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/ |access-date=December 10, 2019 |website=Amazon Web Services |archive-date=October 15, 2019 |archive-url=https://web.archive.org/web/20191015132051/https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/ |url-status=live }}</ref> [[Ruby (programming language)|Ruby]],<ref>{{cite web |last=Munns |first=Chris |date=November 29, 2018 |title=Announcing Ruby Support for AWS Lambda |url=https://aws.amazon.com/blogs/compute/announcing-ruby-support-for-aws-lambda/ |access-date=December 10, 2019 |website=Amazon Web Services |archive-date=October 15, 2019 |archive-url=https://web.archive.org/web/20191015132019/https://aws.amazon.com/blogs/compute/announcing-ruby-support-for-aws-lambda/ |url-status=live }}</ref> and [[C Sharp (programming language)|C#]] (through [[.NET]]) are all officially supported {{as of|2018|lc=1}}. In late 2018, custom runtime support<ref>{{cite web |date=November 29, 2018 |title=AWS Lambda Now Supports Custom Runtimes and Enables Sharing Common Code Between Functions |url=https://aws.amazon.com/about-aws/whats-new/2018/11/aws-lambda-now-supports-custom-runtimes-and-layers/ |access-date=December 10, 2019 |website=Amazon Web Services |archive-date=October 17, 2019 |archive-url=https://web.archive.org/web/20191017111944/https://aws.amazon.com/about-aws/whats-new/2018/11/aws-lambda-now-supports-custom-runtimes-and-layers/ |url-status=live }}</ref> was added to AWS Lambda.

In 2019, at the AWS annual cloud computing conference (AWS re:Invent), the AWS Lambda team announced "Provisioned Concurrency", a feature that "keeps functions initialized and hyper-ready to respond in double-digit milliseconds."<ref>{{cite web |date=3 December 2019 |title=New – Provisioned Concurrency for Lambda Functions |url=https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/ |access-date=2020-10-12 |website=aws.amazon.com |archive-date=2020-10-18 |archive-url=https://web.archive.org/web/20201018033719/https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/ |url-status=live }}</ref> The Lambda team described Provisioned Concurrency as "ideal for implementing interactive services, such as web and mobile backends, latency-sensitive [[microservices]], or synchronous APIs."<ref>{{Cite web |date=2019-12-03 |title=New – Provisioned Concurrency for Lambda Functions |url=https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/ |access-date=2020-02-03 |website=Amazon Web Services |language=en-US |archive-date=2020-02-03 |archive-url=https://web.archive.org/web/20200203223548/https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/ |url-status=live }}</ref>

The Lambda Function URL gives Lambda a unique and permanent [[URL]] which can be accessed by [[authenticated]] and non-authenticated users alike.<ref name=":0">{{Cite web |title=Lambda function URLs - AWS Lambda |url=https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html |access-date=2024-03-01 |website=docs.aws.amazon.com |archive-date=2024-03-01 |archive-url=https://web.archive.org/web/20240301105416/https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html |url-status=live }}</ref>

==Lambda layer==

AWS Lambda layer is a ZIP archive containing libraries, frameworks or custom code that can be added to AWS Lambda functions. <ref>{{Cite web |title=Managing Lambda dependencies with layers |url=https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html |url-status=live |access-date=2024-02-02 |archive-date=2024-02-04 |archive-url=https://web.archive.org/web/20240204142231/https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html }}</ref> As of December 2024, AWS Lambda layers have significant limitations: <ref>{{Cite book |last=Sbarski |first=Peter |title=Serverless Architectures on AWS: With examples using AWS Lambda |isbn=9781638351146}}</ref><ref>{{Cite book |title=Data Engineering with AWS: Learn how to design and build cloud-based data transformation pipelines using AWS |isbn=9781800569041}}</ref>

* No semantic versioning support.

Line 32:

==Portability==

Migration from AWS Lambda to other AWS compute services (e.g., Amazon ECS) can be challenging due to tight integrations with the service provider, a phenomenon known as service lock-in. Tools like [https://github.com/awslabs/aws-lambda-web-adapter AWS Lambda Web Adapter] can facilitate [[Software portability|portability]] by enabling developers to build web applications using familiar frameworks, employing the Lambdalith or [https://docs.aws.amazon.com/lambda/latest/dg/monolith.html Lambda monolith] pattern. <ref>{{Cite web |title=AWS Lambda Web Adapter |url=https://github.com/awslabs/aws-lambda-web-adapter |url-status=live |access-date=2024-11-29 |archive-date=2024-11-28 |archive-url=https://web.archive.org/web/20241128211006/https://github.com/awslabs/aws-lambda-web-adapter }}</ref><ref>{{Cite web |title=The Lambda monolith |url=https://docs.aws.amazon.com/lambda/latest/dg/monolith.html |url-status=live |access-date=2024-11-29 |archive-date=2024-11-26 |archive-url=https://web.archive.org/web/20241126020340/https://docs.aws.amazon.com/lambda/latest/dg/monolith.html }}</ref> However, this approach has some limitations:

* Coarser-grained alerting and access controls compared to single-purpose functions.

Line 47:

==Helper Tools==

[https://www.lldebugger.com/ Lambda Live Debugger] is an [[Open source|open-source]] tools that helps you debug your AWS Lambda functions from your computer, while they are deployed in the cloud. It supports [[AWS Cloud Development Kit|AWS CDK]] v2, [[Serverless Framework]] v3, AWS Serverless Application Model (SAM) and [[Terraform (software)|Terraform]]. <ref>{{Cite web |title=Lambda Live Debugger |website=[[GitHub]] |url=https://github.com/ServerlessLife/lambda-live-debugger |access-date=2024-10-04 |archive-date=2024-10-07 |archive-url=https://web.archive.org/web/20241007091757/https://github.com/ServerlessLife/lambda-live-debugger |url-status=live }}</ref>

== Security ==

In April 2022, researchers found cryptomining malware targeting AWS Lambda named "Denonia".<ref>{{Cite web |url=https://www.cadosecurity.com/blog/cado-discovers-denonia-the-first-malware-specifically-targeting-lambda |title=Archived copy |access-date=2024-11-04 |archive-date=2024-11-15 |archive-url=https://web.archive.org/web/20241115021350/https://www.cadosecurity.com/blog/cado-discovers-denonia-the-first-malware-specifically-targeting-lambda |url-status=live }}</ref><ref>{{Cite web |url=https://indianexpress.com/article/technology/crypto/cryptocurrency-mining-malware-used-to-target-aws-lambda-research-7859739/ |title=Archived copy |access-date=2024-11-04 |archive-date=2024-03-15 |archive-url=https://web.archive.org/web/20240315230202/https://indianexpress.com/article/technology/crypto/cryptocurrency-mining-malware-used-to-target-aws-lambda-research-7859739/ |url-status=live }}</ref><ref>{{Cite web |url=https://therecord.media/researcher-finds-cryptomining-malware-targeting-aws-lambda |title=Archived copy |access-date=2024-11-04 |archive-date=2024-04-05 |archive-url=https://web.archive.org/web/20240405092229/https://therecord.media/researcher-finds-cryptomining-malware-targeting-aws-lambda |url-status=live }}</ref>

==See also==