Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AWS Lambda


Published on

Slides for a short presentation I gave on AWS Lambda, which "lets you run code without provisioning or managing servers". Lambda is to running code as Amazon S3 is to storing objects.

Published in: Software
  • Be the first to comment

AWS Lambda

  1. 1. AWS Lambda λ Scott Leberknight 12/01/2016
  2. 2. "AWS Lambda lets you run code without provisioning or managing servers…"
  3. 3. "there is no charge when your code is not running"
  4. 4. "run code for virtually any type of application or backend service…"
  5. 5. "…with zero administration"
  6. 6. Lambda is to running code… …as S3 is to storing objects
  7. 7. S3 vs. Lambda
  8. 8. Provide objects to S3 S3 stores those objects transparently S3 You don't know how or where objects are stored No servers, drives, or disk space to manage Charged only by amount stored
  9. 9. Provide function code to Lambda Lambda executes code on demand Lambda You don't know how or where code is executed No servers or VMs to manage Charged only for execution time
  10. 10. What is a Lambda function? Code Dependencies (e.g. libraries, modules, binaries) Configuration
  11. 11. Let's create a really simple function…
  12. 12. 1. Create new function
  13. 13. 2. Select blueprint (optional)
  14. 14. 3. Configure trigger (optional)
  15. 15. 4. Basic function info
  16. 16. 5a. Enter function code
  17. 17. 5b. Completed code
  18. 18. 6a. Configure function
  19. 19. 6b. More configuration
  20. 20. 7. Review
  21. 21. 8. Function created
  22. 22. 9a. Configure test event
  23. 23. 9b. Edit test event
  24. 24. 10. Execution results
  25. 25. 11. View CloudWatch Logs
  26. 26. 12. Basic CloudWatch Metrics
  27. 27. 13. Execute via AWS CLI
  28. 28. Supported Platforms JavaScript (Node.js 4.3) Python 2.7 Java8
  29. 29. What about costs? First million requests per month are free Plus duration of execution (GB-seconds) rounded up to nearest 100 milliseconds ($0.00001667 per GB-sec) Charged 20¢ per million requests… (information as of November 30, 2016) First 400,000 GB-seconds per month are free
  30. 30. Pricing Example One function, 128MB allocated, executed 30 million times, ran for 200ms each time… Compute charges (GB-sec): $5.83 Request charges: $5.80 Total charges (month): $11.63
  31. 31. How can a λ be executed? Manually in AWS Lambda console Using AWS SDK to call Lambda API HTTP requests via API Gateway Events raised in AWS (e.g. an object created in S3, new data in Kinesis stream
  32. 32. Ways to invoke λ functions RequestResponse (synchronous) Event (asynchronous)
  33. 33. RequestResponse Invocation When a λ function is: Invoked via the AWS console Invoked using the AWS CLI Executed via the Amazon API Gateway
  34. 34. Event Invocations When an AWS event triggers a λ function: An object is created in S3 An Amazon SNS notification A Kinesis or DynamoDB stream
  35. 35. Event Models: Push vs. Pull Push - A service (e.g. S3) publishes an event to Lambda and invokes the function Pull - Lambda polls streaming event source (Kinesis, DynamoDB) and invokes the function when new data arrives
  36. 36. Programming Model Handler Context Object Logging Exceptions
  37. 37. The following programming model examples are for Node.js… The Python 2.7 and Java8 models are similar
  38. 38. Handler exports.handler = (event, context, callback) => { // code... } event contains input data context contains metadata about the executing λ function callback (Node.Js only) returns error or successful result to caller
  39. 39. Handler exports.myHandler = (event, context, callback) => { console.log("Event: ", JSON.stringify(event, null, 2)); var result = { "product": event.x * event.y }; callback(null /* error*/, result); } multiply.js Handler name: multiply.myHandler multiply.js exports.myHandler
  40. 40. Context Object contains metadata about a λ function version name ARN (Amazon Resource Name) memory (MB) AWS request ID log group log stream Cognito identity client context (mobile) remaining time (ms)
  41. 41. Logging Logs are stored in AWS CloudWatch Available via AWS console or CloudWatch API"Event: ", JSON.stringify(event, null, 2));
  42. 42. Exceptions exports.myHandler = (event, context, callback) => { // code to compute the sum... if (sum > 42) { var error = new Error( "Sum cannot be more than the ultimate answer!"); callback(error); } else { callback(null, result); } } CloudWatch
  43. 43. Monitoring λ functions Logs and metrics in CloudWatch Setup alarms Create dashboards
  44. 44. What about permissions? Functions execute with a role
  45. 45. Permissions: Role Attach policies to roles
  46. 46. Permissions: Policy
  47. 47. Multiple Policies Read/write S3 objects Write to DynamoDB Write CloudWatch logs
  48. 48. Custom Policy
  49. 49. Deploying λ functions Edit code in AWS console Upload deployment package as a zip file Upload deployment package from S3 AWS CloudFormation
  50. 50. Deployment Package Contains function code and dependencies myfunction.js node_modules/ node_modules/async node_modules/async/lib node_modules/async/lib/async.js ...
  51. 51. Manual Upload (not repeatable)
  52. 52. Create via CLI $ aws lambda create-function --function-name simple-deploy-test --description "deployment test function" --handler myfunction.myHandler --memory-size 128 --runtime nodejs4.3 --role arn:aws:iam::269911013159:role/deploy-test-role (repeatable, easily to automate)
  53. 53. Versioning λ functions Publishing a function creates a new version $LATEST is the current, editable version Previous versions are immutable Publish via AWS console, CLI, or Lambda SDK
  54. 54. Editing $LATEST
  55. 55. Publish new version
  56. 56. New Version
  57. 57. Version History
  58. 58. Function Aliases Use aliases to point to the proper version Multiple aliases for separate deployment environments (e.g. dev, staging, production) Refer to aliases, not specific versions
  59. 59. Multiple Aliases
  60. 60. When things go wrong… Automatic retry for stream-based event sources (e.g. Kinesis, Dynamo) Automatic retry for asynchronous events from non-stream-based sources (e.g. S3) Manual retry for synchronous invocations
  61. 61. Container re-use Functions run in an isolated container (sandbox) Lambda may or may not re-use same container across different invocations Be aware that files written to /tmp may still exist from previous invocations!
  62. 62. Testing λ functions lambda-local (Node.js, GitHub) Mocking, e.g. context object & AWS SDKs lambda-test-harness blueprint aws-lambda-python-local (GitHub)
  63. 63. Here come the frameworks… Chalice - Python micro-framework by AWS dev tools team Apex - build, deploy, manage λ functions Serverless - build web, mobile, IoT apps powered by Lambda & API Gateway
  64. 64. Resource Limits Resources are not infinite - λ imposes limits Examples: 300 seconds (5 minutes) max execution time Maximum 50MB deployment package 100 concurrent executions See developer guide for details…
  65. 65. It's a wrap! Lambda is to code as S3 is to storage No servers, no VMs, no administration Charged only when functions run Synchronous or async Many ways to invoke (events,API gateway,AWS SDK calls,AWS CLI,AWS console, etc.)
  66. 66. References AWS Lambda in Action Serverless Architectures on AWS AWS Lambda Lambda Developer Guide
  67. 67. My Info sleberknight at @sleberknight scott.leberknight at gmail