A custom application lets users upload images. Uploads invoke a Lambda function that processes and stores images in S3. The application calls the Lambda function by a specific function version ARN. Image processing parameters are provided via environment variables. The team frequently changes environment variables to tune processing, then publishes a new function version and updates the application to call the new version ARN, causing user disruption. How can a solutions architect simplify this workflow with the LEAST operational overhead?

Creating a Lambda function alias is the most efficient solution. Aliases allow you to point to specific function versions. By having the application invoke the alias ARN, you can seamlessly switch the underlying function version without modifying the application code. When new parameters are needed, you publish a new version, test it, and then simply update the alias to point to the new version. This eliminates application redeployments and user disruption. Directly changing environment variables of a published version is not possible; environment variables are immutable for published versions. Creating a DynamoDB table adds unnecessary complexity and latency for simple parameter changes. Hard-coding parameters requires publishing a new version for every change, which is the current disruptive workflow.