npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mailbutler/lambda-http-proxy

v1.1.2

Published

Access HTTP endpoints through a lambda proxy when direct access is restricted, e.g. when in a VPC

Downloads

9

Readme

Lamda HTTP Proxy

Simple wrapper function to easily send HTTP requests via a Lambda proxy function

NPM Version Downloads Stats

If you run into the problem of not being able to perform HTTP requests to external resources from a resource within a VPC, e.g. a Lambda function, then performing the HTTP request through a simple Lambda HTTP proxy function could be a solution.

This module provides a simple abstraction to send HTTP requests through a separate AWS Lambda proxy function. The provided interface uses Axios request/response object structures to simplify replacement of existing Axios calls.

Installation

npm install lambda-http-proxy --save

AWS Requirements

Lambda Proxy Function

To perform HTTP requests from within a VPC without paying for more networking resources, such as Elastic IPs and NAT Gateways, you first need to create a separate Lambda function that acts as a HTTP proxy for your requests.

The Lambda proxy function simply performs the actual request via Axios (with the given configuration parameter) and returns the response object back to the caller of the Lambda proxy function:

const axios = require('axios');

exports.handler = function (event, context) {
  axios(event).then((response) => context.succeed(response));
};

VPC Endpoint

To allow calling the new Lambda proxy function from within the VPC, you need to add a VPC Endpoint for Lambda, according to this document: https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc-endpoints.html

Usage example

After having prepared your AWS environment, you can now import the module into your project, e.g. a Lambda function and send external HTTP requests via the Lambda proxy function:

import { lambdaProxyRequest } from '@mailbutler/lambda-http-proxy';

const requestConfig = {
  // name of the Lambda HTTP proxy function (see above)
  lambdaFunctionName: 'lambda-http-proxy',

  // axios request configuration
  url: 'https://jsonplaceholder.typicode.com/todos',
  method: 'get',
};

const httpResponse = await lambdaProxyRequest(requestConfig);

Release History

  • 1.0
    • Initial version

Contributing

  1. Fork it (https://github.com/mailbutler/lambda-http-proxy/fork)
  2. Create your feature branch (git checkout -b feature/fooBar)
  3. Commit your changes (git commit -am 'Add some fooBar')
  4. Push to the branch (git push origin feature/fooBar)
  5. Create a new Pull Request