Copyright 2016 by Alan Smith - All rights reserved.
This document is geared towards providing exact and reliable information in regards to the topic and issue covered. The publication is sold with the
idea that the publisher is not required to render accounting, officially permitted, or otherwise, qualified services. If advice is necessary, legal or
professional, a practiced individual in the profession should be ordered.
- From a Declaration of Principles which was accepted and approved equally by a Committee of the American Bar Association and a Committee of
Publishers and Associations.
In no way is it legal to reproduce, duplicate, or transmit any part of this document in either electronic means or in printed format. Recording of this
publication is strictly prohibited and any storage of this document is not allowed unless with written permission from the publisher. All rights reserved.
The information provided herein is stated to be truthful and consistent, in that any liability, in terms of inattention or otherwise, by any usage or abuse
of any policies, processes, or directions contained within is the solitary and utter responsibility of the recipient reader. Under no circumstances will any
legal responsibility or blame be held against the publisher for any reparation, damages, or monetary loss due to the information herein, either directly
or indirectly.
Respective authors own all copyrights not held by the publisher.
The information herein is offered for informational purposes solely, and is universal as so. The presentation of the information is without contract or
any type of guarantee assurance.
The trademarks that are used are without any consent, and the publication of the trademark is without permission or backing by the trademark owner.
All trademarks and brands within this book are for clarifying purposes only and are the owned by the owners themselves, not affiliated with this
document.
Introduction
I want to thank you and congratulate you for downloading this book!
All the best insights on AWS Lambda are in this book.
Alan Smith
Fact #1: What AWS Lambda Is
The AWS Lambda allows you to run your code without the need for personally
provisioning or managing the servers. The AWS Lambda will be the one to provision and
manage the servers for you after you upload your code into it and create a Lambda
function. The Lambda will use its AWS infrastructure to run the code that you will upload
into it. As for the payment, you will only spend money for the compute time that you will
consume. If the code is not running, then, you do not have to pay anything at all. Zero
administration is actually a benefit of the AWS Lambda.
Fact #2: Kinds of Codes That can Run on
Lambda
AWS Lambda can run various types or kinds of codes in its system. With AWS Lambda,
you can audit and report API calls that were made to an Amazon Web service. You can
also build mobile back-ends in retrieving and transforming data from the Amazon
DynamoDB. Most importantly, it can also process data streaming with the use of Amazon
Kinesis without the need for servers.
Fact #3: Supported Programming
Languages
There are several programming languages that AWS Lambda can support. Some of these
are codes that are written in Java, Python, and Node.js. You can actually include existing
libraries in your code as well as the native ones. In this case, you will have an assurance
that your program will work properly as it will be running on a fully functional platform.
Fact #4: Isolation and Security of Your Code
Each function from AWS Lambda runs in its own environment and has its own resources
as well as file system views. For this matter, there is an assurance that your code is
isolated from other codes. Aside from that, the code is stored by AWS Lambda in Amazon
S3. It also encrypts the code when at rest. It also performs further integrity checks while
you are using the code. In this case, you can be sure that the code is in a secured platform.
The AWS Lambda utilizes similar techniques as the Amazon EC2.
Fact #5: AWS Lambda Function
When you upload a code that you have written, it becomes an AWS Lambda function.
Such function has configuration information associated with it. Some of these information
include resource requirements, entry point, the description, and the name. However, you
must write the code in a stateless style. This means that it should assume that there is no
affinity to an underlying compute infrastructure. However, you cannot access such
infrastructure.
Fact #6: Creating an AWS Lambda Function
through the Lambda Console
When creating the function using the Lambda console, you can author your code using the
available inline editor. You may also package the code as a ZIP file and upload it through
the console from the Amazon S3 location or a local environment. You must make sure that
you will upload a ZIP file size that does not exceed 50MB.
Fact #7: Creating an AWS Lambda Function
through the Lambda CLI
In this case, you can package your code and compress it to a ZIP file. Afterwards, you can
upload it through the Lambda CLI from a specific Amazon S3 location or from your local
environment. This step is pretty much the same as when you will be using the Lambda
console. You should also remember that the compressed file that you will be uploading to
the system should not be more than 50MB in file size, as well.
Fact #8: Monitoring the AWS Lambda
Function
Automatic monitoring is actually a feature of AWS Lambda. It provides you with metrics
in real time through the Amazon CloudWatch. Some of these metrics include throttle
requests, error rates, latency, and total requests. You will have to pay a certain amount as
standard charges usually apply if you will use the metrics that are built into Lambda.
Fact #9: Troubleshooting Failures
Since AWS Lambda integrates with the Amazon CloudWatch logs automatically, you can
insert additional logging statements easily into your code. You may also be calling third-
party logging API in the Lambda function. However, standard charges may apply for the
Amazon
Conclusion
Thank you again for downloading this book!
