A software company utilizes AWS Lambda for deploying a mission-critical application. In their upcoming release, they plan to incorporate a canary release strategy to introduce a new feature incrementally while mitigating risks. Assuming they already have a Lambda alias for their production environment, how should the company configure the alias to slowly route a small percentage of user traffic to the new feature while the majority still accesses the stable version?
Deploy the new feature as a new Lambda function and update the production alias configuration to point solely to the new function, relying on Lambda's inherent traffic shifting capabilities.
Deploy the new version as a separate Lambda function without an alias and manually invoke the new function to represent a percentage of total traffic.
Configure the Lambda alias to immediately redirect 100% of traffic to the new version to test the new feature in live conditions.
Adjust the production alias to serve both the old and the new Lambda versions, and configure the alias routing with a small weight towards the new version, gradually increasing it based on the monitoring results.