How to deploy Express applications to AWS Lambda

By: (plus.google.com) +David Herron; Date: May 19, 2018

Tags: Node.JS » AWS Lambda

AWS Lambda and the AWS API Gateway is a powerful combination for deploying Node.js application code on an automagically scaling deployment platform. Out of the box you do not have the Express API. This webinar shows how to setup API Gateway and Lambda to support Express applications.

With AWS API Gateway, the developer benefits are

  • The ability to define a unified consistent API
  • Automatic DDOS protection
  • Authentication and authorization at the API Gateway layer -- The backend can trust authorization has been accomplished

With AWS Lambda, the programmer focuses on their code, and does not get caught up with DevOps drama. The Lambda function handles scaling the service to meet the request volume, and you pay only for the requests handled. An idle API service does not incur any cost. Write code, deploy code, and write a check to Amazon AWS.

Migrating an existing service to the combination of API Gateway with AWS Lambda. The organization may have an existing API implemented with a traditional deployment to a regular server. The first step of the transition is using API Gateway as a front end to the existing service. The next step is implementing Lambda functions for each of the service methods, flipping each API endpoint to use the Lambda function as the Lambda functions become complete.

An opportunity is available during that API migration process to rearchitect the API.

Some API Gateway features simplify the migration process:

  • "Catch-all" resource paths -- meaning, that in API Gateway one specifies a URL pattern matching a URL prefix, and all requests starting with that prefix are sent to the same Lambda function. That Lambda one function can handle a large swath of request URL's. The advantage in migrating an existing service, is to match all the URL's from that existing service into the same service module.
  • The "ANY" HTTP method -- Lets API Gateway route every HTTP method on a given URL pattern to the same Lambda function. This simplifies the service definition in the API Gateway, allowing the Lambda function to define the service.
  • Proxy integrations -- Simplifies sending parameters from the HTTP request on to the service function, whether it is an AWS Lambda function, or another HTTP service. For the AWS Lambda case, it automatically configures a request mapping template to capture the all request parameters into an object sent to the Lambda function.

The downside of all these simplifications is that the Swagger/OpenAPI definition in the API Gateway does not have the complete API definition. In theory it is best for the API definition to be written with OpenAPI, so you can then generate complete API documentation from the OpenAPI specification. But if some of the API is defined in the Lambda function, the OpenAPI specification does not have the entire API.

The AWS API Gateway supports some OpenAPI/Swagger extensions to aid defining these things. Alternately, you can piece-by-piece migrate the entire API structure into the OpenAPI specification. You are not required to migrate the entire API all at once, and can do it as you have the time.

Hence the simplest possible API is for a Catch-All path for the entire API, using the ANY request type, proxying everything to an Express application.

The aws-serverless-express library "wraps" an Express application to match what's provided by API Gateway and Lambda. It works by automatically spinning up a background Express server each Lambda container instance. The aws-serverless-express library maps the incoming Lambda express into another HTTP request invoked on the background Express server.

The Lambda function implemented using this library looks like:

const awsServerlessExpress = require('aws-serverless-express');
const app = require('./app');
const server = awsServerlessExpress.createServer(app);

exports.handler = function(event, context) {
    awsServerlessExpress.proxy(server, event, context);
}

The code in app.js must initialize the Express service, but not instantiate the HTTP Server object.

While this is an excellent method to quickly migrate Express code into Lambda, it has a higher overhead because it starts a background service. Interoperating with that background service must be passed across process boundaries, adding to execution time, and incurs the memory overhead of a second process.

Github repository: (github.com) https://github.com/awslabs/aws-serverless-express

« Getting started with asynchronous read/write between Node.js 8 and MongoDB Avoid killing performance with asynchronous ES7 JavaScript async/await functions »
2016 Election 2018 Elections Acer C720 Ad block Air Filters Air Quality Air Quality Monitoring AkashaCMS Amazon Amazon Kindle Amazon Web Services America Amiga and Jon Pertwee Android Anti-Fascism AntiVirus Software Apple Apple Hardware History Apple iPhone Apple iPhone Hardware April 1st Arduino ARM Compilation Artificial Intelligence Astronomy Astrophotography Asynchronous Programming Authoritarianism Automated Social Posting AWS DynamoDB AWS Lambda Ayo.JS Bells Law Big Brother Big Data Big Finish Big Science Bitcoin Mining Black Holes Blade Runner Blockchain Blogger Blogging Books Botnets Cassette Tapes Cellphones China China Manufacturing Christopher Eccleston Chrome Chrome Apps Chromebook Chromebox ChromeOS CIA CitiCards Citizen Journalism Civil Liberties Climate Change Clinton Cluster Computing Command Line Tools Comment Systems Computer Accessories Computer Hardware Computer Repair Computers Conservatives Cross Compilation Crouton Cryptocurrency Curiosity Rover Currencies Cyber Security Cybermen Cybersecurity Daleks Darth Vader Data backup Data Formats Data Storage Database Database Backup Databases David Tenant DDoS Botnet Department of Defense Department of Justice Detect Adblocker Developers Editors Digital Nomad Digital Photography Diskless Booting Disqus DIY DIY Repair DNP3 Do it yourself Docker Docker MAMP Docker Swarm Doctor Who Doctor Who Paradox Doctor Who Review Drobo Drupal Drupal Themes DVD E-Books E-Readers Early Computers eGPU Election Hacks Electric Bicycles Electric Vehicles Electron Eliminating Jobs for Human Emdebian Encabulators Energy Efficiency Enterprise Node EPUB ESP8266 Ethical Curation Eurovision Event Driven Asynchronous Express Face Recognition Facebook Fake News Fedora VirtualBox Fifth Doctor File transfer without iTunes FireFly Flash Flickr Fraud Freedom of Speech Front-end Development G Suite Gallifrey git Github GitKraken Gitlab GMAIL Google Google Chrome Google Gnome Google+ Government Spying Great Britain Green Transportation Hate Speech Heat Loss Hibernate High Technology Hoax Science Home Automation HTTP Security HTTPS Human ID I2C Protocol Image Analysis Image Conversion Image Processing ImageMagick In-memory Computing InfluxDB Infrared Thermometers Insulation Internet Internet Advertising Internet Law Internet of Things Internet Policy Internet Privacy iOS Devices iPad iPhone iPhone hacking Iron Man iShowU Audio Capture iTunes Janet Fielding Java JavaFX JavaScript JavaScript Injection JDBC John Simms Journalism Joyent Kaspersky Labs Kext Kindle Kindle Marketplace Large Hadron Collider Lets Encrypt LibreOffice Linux Linux Hints Linux Single Board Computers Logging Mac Mini Mac OS Mac OS X Machine Learning Machine Readable ID Macintosh macOS macOS High Sierra macOS Kext MacOS X setup Make Money Online March For Our Lives MariaDB Mars Mass Violence Matt Lucas MEADS Anti-Missile Mercurial MERN Stack Michele Gomez Micro Apartments Microsoft Military AI Military Hardware Minification Minimized CSS Minimized HTML Minimized JavaScript Missy Mobile Applications Mobile Computers MODBUS Mondas Monetary System MongoDB Mongoose Monty Python MQTT Music Player Music Streaming MySQL NanoPi Nardole NASA Net Neutrality Network Attached Storage Node Web Development Node.js Node.js Database Node.js Performance Node.js Testing Node.JS Web Development Node.x North Korea npm NVIDIA NY Times Online advertising Online Community Online Fraud Online Journalism Online Photography Online Video Open Media Vault Open Source Open Source and Patents Open Source Governance Open Source Licenses Open Source Software OpenAPI OpenJDK OpenVPN Palmtop PDA Patrick Troughton PayPal Paywalls Personal Flight Peter Capaldi Peter Davison Phishing Photography PHP Plex Plex Media Server Political Protest Politics Postal Service Power Control President Trump Privacy Production use Public Violence Raspberry Pi Raspberry Pi 3 Raspberry Pi Zero ReactJS Recaptcha Recycling Refurbished Computers Remote Desktop Removable Storage Republicans Retro Computing Retro-Technology Reviews RFID Rich Internet Applications Right to Repair River Song Robotics Robots Rocket Ships RSS News Readers rsync Russia Russia Troll Factory Russian Hacking Rust SCADA Scheme Science Fiction SD Cards Search Engine Ranking Season 1 Season 10 Season 11 Security Security Cameras Server-side JavaScript Serverless Framework Servers Shell Scripts Silence Simsimi Skype SmugMug Social Media Social Media Networks Social Media Warfare Social Network Management Social Networks Software Development Software Patents Space Flight Space Ship Reuse Space Ships SpaceX Spear Phishing Spring Spring Boot Spy Satellites SQLite3 SSD Drives SSD upgrade SSH SSH Key SSL Stand For Truth Strange Parts Swagger Synchronizing Files Tegan Jovanka Telescopes Terrorism The Cybermen The Daleks The Master Time-Series Database Tom Baker Torchwood Total Information Awareness Trump Trump Administration Trump Campaign Twitter Ubuntu Udemy UDOO US Department of Defense Virtual Private Networks VirtualBox VLC VNC VOIP Vue.js Walmart Weapons Systems Web Applications Web Developer Resources Web Development Web Development Tools Web Marketing Webpack Website Advertising Weeping Angels WhatsApp William Hartnell Window Insulation Windows Windows Alternatives Wordpress World Wide Web Yahoo YouTube YouTube Monetization