And another one from me, on a completely different topic. It looks like Prefect has good support for AWS Lambda, which is awesome. However, I couldn’t see a way to specify the AWS endpoint to use, only the credentials etc. Am I wrong? Our use case for Prefect is to string a series of Lambdas together, and we’re using serverless framework (serverless offline) in our local development environment to run Lambdas on a localhost endpoint. It would be great if I could get Prefect local talking to my local Lambdas.

Hi @Joseph Ellis! Welcome to the community 👋 It sounds like you’re using Prefect Tasks to orchestrate Lambda function in a particular order and you’ve got that working nicely. Are you now trying to change what endpoint your Tasks attempt to communicate with depending on some sort of environment? (Dev vs. Prod, for example)

Hi Dylan, thanks for your response. My use-case at the moment is focussed on our local development environment.

Gotcha

I’m just trying to work out if there’s something I can do with the LambdaInvoke class that Prefect provides to allow me to point to this local endpoint.

So you’re looking for a way to configure the endpoint based on the context?

Correct

You can use Parameters (https://docs.prefect.io/core/concepts/parameters.html) to pass a value into your Flow Run

Apologies Dylan, this is specifically about over-riding the default endpoint_url that is passed to the lambda_client created here: https://github.com/PrefectHQ/prefect/blob/master/src/prefect/tasks/aws/lambda_function.py

Ahh okay

It’s alright, I’ve cracked it 🙂

Excellent!