aws-lambda-build | Build AWS Lambda package | AWS library

by Max-Kolodezniy JavaScript Version: 1.0.8 License: MIT

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | aws-lambda-build Summary

aws-lambda-build is a JavaScript library typically used in Cloud, AWS applications. aws-lambda-build has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i aws-lambda-build' or download it from GitHub, npm.

Build AWS Lambda package

Support

Quality

Security

License

Reuse

Support

aws-lambda-build has a low active ecosystem.

It has 7 star(s) with 1 fork(s). There are 2 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 1 have been closed. On average issues are closed in 225 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of aws-lambda-build is 1.0.8

Quality

aws-lambda-build has no bugs reported.

Security

aws-lambda-build has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

aws-lambda-build is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

aws-lambda-build releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of aws-lambda-build

Get all kandi verified functions for this library.

aws-lambda-build Key Features

No Key Features are available at this moment for aws-lambda-build.

aws-lambda-build Examples and Code Snippets

No Code Snippets are available at this moment for aws-lambda-build.

Community Discussions

Trending Discussions on aws-lambda-build

Cannot get AWS SAM CLI to work with Python 3.5.x

Unable to switch from AWS Layer to specifying locally built editable pip3 packages when executing function

`sam local invoke`error 'NameError: name 'NpipeHTTPAdapter' is not defined'

aws sam build not able to build packages which require paramiko due to "Error: PythonPipBuilder:ResolveDependencies"

Building a node module for aws lambda

QUESTION

Cannot get AWS SAM CLI to work with Python 3.5.x

Asked 2021-Apr-13 at 03:51

I am certain that this issue is down to my own ignorance of Python and pip, however, I have scoured the net and tried many things to get this to work, so far, to no avail.

I have a docker image based on the Bitbucket pipelines default image (version 2): atlassian/default-image:2, which uses Python 2.7.x. And SAM doesn't work with that, I looked at AWS' documentation and this said that the SAM CLI no longer supports Python 2.7.x, so I removed all Python installations from the docker container (debugging the Bitbucket pipeline locally) and attempted to make sure that there was only Python3 and pip3 installed (I even setup symlinks from /usr/bin/python to /usr/bin/python3 and from /usr/bin/pip to /usr/bin/pip3 - although, that seems like such a dumb thing to have to do).

I also tried doing the above with Python 3.6, as the error message (shown below) seemed to show a Python 'f-String' syntax, which according to Python's docs was introduced in 3.6.

Nothing I do seems to work and the more I look at this, the more I get tied up in an seemingly never ending web of Python versions and linux packages!

The error (and python versions) can be seen here:

...

ANSWER

Answered 2021-Apr-13 at 03:51

In most cases, instead of modifying the python installation in an existing image or installing a new one, I would recommend just using a docker image that already has python 3 installed. This bitbucket page talks about using different base images.

There's also a page about using a python base image spectifically.

Aside from this, depending on how you want to use SAM, you may be able to use the builtin Bitbucket "pipe" for deploying to SAM instead. Here is some info on pipes.. I think this would bypass the need to install SAM in your build.

I haven't used that particular pipe myself but the way I think it works is you build your deploy artifact file in your pipeline, caching it so it's available in future steps, then you set that file as the input for the SAM pipe to deploy it. The SAM pipe runs in a separate container, so it's already installed in that container. You just pass in the file.

Finally, I have never used SAM, so take this with a grain of salt, but I don't see a reference to installing the CLI with pip either on the official AWS Linux installation docs or on the github page. I did find this issue, from which I glean the following:

pip installation is possible but not recommended
Python 3.5 is not supported by aws sam cli
If you use the installer in the instructions, it sounds like it will take care of the python versioning for you.
They would like to target a single version of Python, so if you use pip, maybe the latest or 2nd latest Python version will work. Just a guess...

Source https://stackoverflow.com/questions/67068093

QUESTION

Unable to switch from AWS Layer to specifying locally built editable pip3 packages when executing function

Asked 2020-Feb-13 at 08:34

I'm both learning python and attempting to build multiple lambdas that will both store and process Spotify listening history. I originally wrote one lambda with all dependencies packaged in the same directory and imported using relative paths.

Once creating similar functions which use the same dependencies, I've split the dependencies from the function and built them using pip3 and setup.py. When running pip3 list I can see the packages as expected. To execute the function locally using sam build && sam local invoke SpotifyPlayHistoryListener --env-vars env.json --event events/event.json and verify success, I'm specifying a layer I've built - this works!

To avoid having to rebuild the layer and modifying my function, I'd like to be able to revert to using a requirements.txt file and removing the specified layer.

Steps to reproduce the issue:

...

ANSWER

Answered 2020-Feb-13 at 08:34

As my dependencies weren't published to pypi, I needed to modify the entries in requirement.txt to use the actual file path to the package.

Source https://stackoverflow.com/questions/60187201

QUESTION

`sam local invoke`error 'NameError: name 'NpipeHTTPAdapter' is not defined'

Asked 2019-Dec-02 at 19:58

I am writing a lambda function just to get some data from an AWS RDS table. I am able to successfully run sam package and sam deploy to deploy the function to AWS.

When I run sam build it successfully builds and then I run sam local invoke to test the lambda locally, but I get the following error output

...

ANSWER

Answered 2019-Dec-02 at 19:58

I ended up needing to uninstall the version of sam-cli I installed via pip and use the Windows MSI installer instead. Apparently using the MSI is the required installation method for Windows. And then use 'sam.cmd' to invoke the sam cli.

Source https://stackoverflow.com/questions/59058770

QUESTION

aws sam build not able to build packages which require paramiko due to "Error: PythonPipBuilder:ResolveDependencies"

Asked 2019-Aug-29 at 12:01

I've been learning the ropes with AWS SAM and have successfully deployed a number of lambdas together with dependencies and other AWS services. However, I seem to have run into a problem when trying to deploy a lambda which relies on some specific dependencies.

Here is my requirements.txt file:

...

ANSWER

Answered 2019-Aug-29 at 12:01

I've managed to get a workaround to build and deploy lambdas that need the paramiko library using a docker container in interactive mode. Anyone having the same problem have a look here

Source https://stackoverflow.com/questions/57672859

QUESTION

Building a node module for aws lambda

Asked 2019-Mar-03 at 20:44

I'm trying to use the Sharp library in AWS Lambda but it requires the module be compiled for the lambda environment. The instructions say to create an ec2 instance and compile it on there - but I noticed that there are a few tools to help with that but they are all at least a year old with no maintenance. Is there a package that comes with Serverless, or something that's considered the standard way now?

I've found these but they are all at least a year old since a commit

https://github.com/node-hocus-pocus/thaumaturgy

https://github.com/Max-Kolodezniy/aws-lambda-build

https://github.com/tomdale/lambda-packager

Maybe there is a directory somewhere where I can just download a precompiled Sharp library for AWS lambda?

...

ANSWER

Answered 2017-Apr-26 at 08:18

I made it work using sharp-0.17.3-aws-linux-x64-node-6.10.1.tar.gz tarball, that was created on AWS EC2 instance running Nodejs 6.10.1. The tarball contains node_modules/ directory with sharp system binaries (libvips library) specific to the Lambda execution environment.

Project structure

To avoid conflicts between my local node_modules/ (Nodejs 7.5 on Mac) and node_modules/ inside the tarball (Nodejs 6.10 on Linux), I'm creating my Lambda service under a subdirectory.
Project structure looks as follows:

Source https://stackoverflow.com/questions/42950758

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install aws-lambda-build

You can install using 'npm i aws-lambda-build' or download it from GitHub, npm.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: