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.

Pulumi Community

more details:

```   {
      RespMetadata: {
        StatusCode: 409,
        RequestID: "4571dacb-8e3b-42e1-bcc3-3ee762eb560c"
      },
      Message_: "Function already exist: pool-lambda-80a6da40-c917-41c9-90d8-7cef62a40dcc",
      Type: "User"
    }```
409 response is

```ResourceConflictException
The resource already exists, or another operation is in progress.

HTTP Status Code: 409```

That error is coming from AWS - so it seems like somehow you have created a lambda with that same name. 

Are you trying to force this to be replaced on every update? I can’t exactly follow the desired replacement behavior. 

I don’t think it’s actually what you want - but you could try `deleteBeforeReplace.` 

FYI I switched from inline lambda to s3 based lambda - and it worked fine. I suspect that my node_modules was too big (although it was around 5MB)  hence failing weirdly after the upload.