Cold starts and initialization

Cold starts happen when Lambda creates a new execution environment. Code that runs during initialization (imports, client setup, configuration loading) adds to cold-start latency, so it's best to keep that work outside the handler and reuse it across invocations.

In this exercise, you'll make a small edit to your function to see the difference between initialization code and handler code, then answer a question about where initialization work belongs.