jthomerson

Chris, while I've seen the change in my accounts on regular Lambda, I don't yet see it on Lambda@Edge. I think Lambda@Edge is the place where we'd benefit from this change the most, because many L@E scenarios take single-digit milliseconds, and the cost of L@E is 3x regular Lambda.

Any word on whether we'll also see this change on L@E billing?

Here's an example of the structure of our repos we'd want to document: https://gist.githubusercontent.com/anonymous/f88e2917b5513c2...