This document discusses running Python code on AWS Lambda. It provides an overview of Lambda's event-driven architecture and how it allows Python code to be executed in response to events. It also covers how the Python runtime is pre-installed on Lambda and how the Lambda execution context provides metadata about the execution environment. Examples are given of creating Lambda functions from the console and using the context object to access execution details.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Markku Lepistö - Principal Technology Evangelist
Python on Lambda

3. User Application
Application Service
Middleware Service
Language Interpreter
Operating System
Host
Focus on Your Application

4. Move Up the Stack

5. Application
Architecture

11. Adrian Cockcroft, Technology Fellow at Battery Ventures
http://www.slideshare.net/adriancockcroft/goto-berlin

12. Amazon Web Services

14. Containers Docker launched in 2013
Cloud EC2 launched in 2006
Virtualization Since late 1990s
Bare Metal Since 1960s

15. Lambda Launched in 2015
Containers Docker launched in 2013
Cloud EC2 launched in 2006
Virtualization Since late 1990s
Bare Metal Since 1960s

16. Event driven, fully managed compute
All you need is code™

19. Fast
events trigger code execution
in milliseconds – at any scale

20. Cost & Resource Efficient
100ms billing granularity
of compute chunks

23. Highly Requested by Customers Since Launch

24. Running Python on Lambda

26. Where can I use the AWS Python SDK ?
Your dev environment Amazon EC2 VM / Container AWS Lambda
(install) (install) (pre-installed)

27. Programming model

28. Asynchronous Synchronous

29. handler_name event context

30. • Print
• Logger
AWS CloudWatch Logs

31. New Python lambda function from blueprint
• Lambda console
• Asynchronous – triggered by S3 event
• Debug & logs in Cloudwatch
• Identity and Access Management
• Exceptions handling

32. New Python ‘Hello World’ Lambda function
• Unit tests in Lambda console
• Synchronous – called by us

33. • Request ID (useful for troubleshooting)
• Time remaining (before ‘timed out’ function is killed)
• Memory available
• Info on calling client i.e Mobile app
• etc

34. context
context.log_stream_name
context.log_group_name
context.aws_request_id
context.memory_limit_in_mb
context.get_remaining_time_in_millis()

35. Let’s run the previous slide Context example

37. aws lambda create-function

38. • pip install zip
setup.cfg
[install]
prefix=

39. aws.amazon.com/lambda
@markkulepisto