https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
c
Another option is if the .zip file is larger than 50 MB, upload it to the function from an Amazon Simple Storage Service (Amazon S3) bucket.
It also looks like utilizing the s3 bucket for CallbackFunction's does not work either https://github.com/pulumi/pulumi-aws/issues/137
My solution was to create a Dockerfile and have my CallbackFunction invoke the Function used in the container. Basically using an extra Lambda function as a workaround. Seems to work well, and going forward for any larger deployments (or Lambda handlers) this is what I'm going to do
To "call" AWS functions inside of the Docker container, you can just use the aws-sdk and pass in the ID's of the resources you're trying to use in the 
Payload
. Not really that elegant of a solution but it works 🤷
Copy code
const json = JSON.stringify({
    bucketId: bucket.get()
});
const lambdaResponse = await lambda.invoke({
    FunctionName: containerLambdaFunction.get(),
    Payload: json
}).promise();
g
A little late, but I use esbuild to package all my functions, it is fast and has some tree-shaking. I also use layers for aws-sdk and other large packages
7 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by