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 🤷

const json = JSON.stringify({
    bucketId: bucket.get()
});
const lambdaResponse = await lambda.invoke({
    FunctionName: containerLambdaFunction.get(),
    Payload: json
}).promise();