A company is running a web application on AWS Elastic Beanstalk.

Elastic Beanstalk traffic splitting is the best operationally efficient deployment option for testing a new application version with a controlled portion of live traffic. Traffic splitting is effectively a canary-style deployment that routes a defined percentage of production traffic to the new version while monitoring health before full rollout. This minimizes disruption because Elastic Beanstalk manages much of the deployment orchestration, health evaluation, and rollback behavior. Manually changing ALB listener rules adds unnecessary operational work and increases the chance of routing mistakes. Replacing all EC2 instances in the Auto Scaling group risks broader production impact. Lambda weighted aliases apply to Lambda functions and are not the correct deployment mechanism for an Elastic Beanstalk application running on EC2 behind an ALB.