So if I want to hook into each 4 parts of the lifecycle, I configure that and it gets executed once?
Can I maintain state between inbound request->origin request->origin response->inbound response?
My understanding was you can’t and it got called 4 times with different events, workers solves this by you being responsible for making the origin request (there is a simple mode where it does it for you to) with promises to manage origin response and inbound response logic.. I thought lambda@edge didn’t work like that?