← Back to context Comment by easton 1 month ago At least it’s not S3 triggers for lambdas, just about gave me a heart attack. 3 comments easton Reply honopu 1 month ago oh maybe thats what were using. Made it months ago and im not 100% sure. Lambda on putObject JohnMakin 1 month ago That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level. honopu 1 month ago Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
honopu 1 month ago oh maybe thats what were using. Made it months ago and im not 100% sure. Lambda on putObject JohnMakin 1 month ago That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level. honopu 1 month ago Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
JohnMakin 1 month ago That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level. honopu 1 month ago Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
honopu 1 month ago Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!
oh maybe thats what were using. Made it months ago and im not 100% sure. Lambda on putObject
That sounds like it might be a lambda trigger to me. The feature being deprecated is lambdas that operate at the s3 API level.
Yeah it's an Event Notification that triggers lambda that acts on the bucket, i had to give it permissions to the bucket so i guess it's outside it :). We'll see!