AWS Lambda: Difference between revisions

Revision as of 14:35, 30 April 2024

Revision as of 16:06, 7 May 2024

Line 17:

AWS Lambda was primarily designed for tasks such as handling image and object [[upload]]s to [[Amazon S3]], updating [[DynamoDB]] tables, responding to website clicks and reacting to sensor readings from [[Internet of Things|IoT]] connected devices. AWS Lambda can also be used to automatically provision back-end services triggered by custom [[HTTP request]]s, and "spin down" such services when not in use to save resources. These custom HTTP requests are configured in AWS API Gateway, which can also handle [[authentication]] and [[authorization]] in conjunction with [[Amazon Cognito|AWS Cognito]].

Unlike Amazon EC2, which is pricedbilled by the hoursecond but(with metereda byminimum theof second60 seconds), AWS Lambda is meteredbilled by rounding up to the nearest millisecond with no minimum execution time.

AWS Lambda functions are often used in association with [[Amazon Simple Queue Service|AWS SQS queues]] to process asynchronous tasks in distributed architectures.