I've run through the sample to get an

onPut

action in an S3 bucket to trigger a lambda using this code:

// A storage bucket
const bucket = new cloud.Bucket("eshamay-test-bucket");
const bucketName = bucket.bucket.id;

// Trigger a Lamda function when something is added
bucket.onPut("onNewObject", (bucketArgs: any) => {
    console.log(`*** New Item in Bucket`);
    console.log(bucketArgs);
});

However, I plan to trigger the lambda from multiple buckets and will create/update some DynamoDB items to index the contents of the various bucket objects across multiple regions. Currently, the lambda above outputs something like this (taken directly from CloudWatch logs:

2018-11-29T12:52:08.159-08:00[onNewObject] { key: 'some/foo/path/myfile.ts',  size: 384,  eventTime: '2018-11-29T20:52:07.166Z' }

However, my indexing will need to create a couple extra attributes to track region, bucket name, and perhaps some other info of the

put

such as the Principle ID, IP address, etc. I know that S3 events emit something like this: https://docs.aws.amazon.com/lambda/latest/dg/eventsources.html#eventsources-s3-put Is there a way to get access to that original event object? Also, is there a way to create a single lambda to do the DynamoDB update, and then create several buckets across regions that trigger that single lambda

onPut

?

Hi @early-musician-41645

great! Now the follow-up, what would it look like to trigger a lambda with each

onObjectCreated

? I'm assuming the code would be something like

// Create a lambda

// Create the bucket

// Set up the bucket onObjectCreated
    // Trigger the lambda somehow from in here using the... lambda.arn?

is it an existing lambda you have?

In this case, no, it will be created as part of the same project. The S3 buckets are pre-existing, though, which is a separate issue

oh. if it's created in the same project, it's trivial

👍 Can you confirm: will the

event

pass through as the arg to the

handler

? Or, what's the signature for the handler? I'm assuming it takes a single arg.

in this case, we aren't really doing anything in pulumi

Okay, one more question - I have pre-created S3 buckets that are managed by a separate team. I'd like to attach this same lambda/handler to each of those buckets. I know the bucket names, regions, arns, etc. How can I load them as objects in Pulumi for use in the same way as if I'd created them?

aws.s3.Bucket.get(..., arn, ...)

very cool. I'll go try all this out. Thanks for the help!!

.get is how you say: this already exists, go fetch it and 'hydrate hte info about it' on the pulumi side

One more thing - will Pulumi create all the needed IAM resources and policies for the bucket events to trigger the lambda if the buckets are pre-created?

here's what we do:

Okay, looks straightforward - very much like if I'd created the object instead of imported via

.get

If you needmore than the permission set, you'd have to do it yourself currently. If there were additional things you wanted us to do, def let us know

thanks again!

Definitely!

I'm trying out the

.get

but the buckets I need are in multiple regions. I tried this with no luck:

const bucket = aws.s3.Bucket.get('prod-us-west-1', 'sdp-tsm-prod-eu1-artifacts', { region: 'us-west-1' });

Diagnostics:
  aws:s3:Bucket (prod-us-west-1):
    error: Preview failed: refreshing urn:pulumi:s3-object-indexer-dev::s3-object-indexer::aws:s3/bucket:Bucket::prod-us-west-1: error reading S3 Bucket (sdp-tsm-prod-eu1-artifacts): BucketRegionError: incorrect region, the bucket is not in 'us-west-2' region
        status code: 301, request id: , host id:

I don't know enough about this. i don't believe pulumi would let you use things from different regions. which i believe is a bit of an aws limitation as well. i.e. i don't think you could set up a bucket to invoke a lambda in a different region.

Settled this in a different thread

interesting.

No clue

Oh, that's something I hadn't considered - can lambdas get called across regions? I'll do some reading