A developer needs to deploy an updated version of a Lambda function for integration testing while ensuring traffic continues to flow uninterrupted to the current production version. The developer wants to gradually shift a small percentage of traffic to the new version to monitor the update before a full rollout. Which deployment strategy should the developer use to meet these requirements?
Use Lambda aliases with weighted traffic shifting to direct a percentage of traffic to the new function version
Update the Lambda function code directly and send all traffic to the new version
Deploy the new Lambda function version to a separate AWS account and test with mirror traffic
Create a new Lambda function for the new version and route traffic manually