A company has a serverless application on AWS that uses a fleet of AWS Lambda functions that have aliases. The company regularly publishes new Lambda function by using an in-house deployment solution. The company wants to improve the release process and to use traffic shifting. A newly published function version should initially make available only to a fixed percentage of production users.
Which solution will meet these requirements?
To meet the requirement of making a newly published function version initially available to a fixed percentage of production users, you can configure routing on the alias of the new function by using a weighted alias. Weighted aliases in AWS Lambda allow you to control the percentage of traffic that is sent to different versions of a Lambda function. This setup is essential for implementing a canary deployment where a small, predefined percentage of traffic is gradually routed to the new version while the old version continues handling the majority of the traffic. This approach effectively minimizes risk while exposing the new function version to real-world conditions.
The correct answer is (A). Weighted aliases allow you to route traffic to different versions of a function based on weights that you assign. This allows you to implement a canary deployment, where you initially route a small percentage of your traffic to the new version of the function, and then gradually increase the percentage as you gain confidence in the new version.
If we need Canary deployment, then why not B ? How you will use A in automated deployment?
AAAAAAAAAAA
Answer is A. weighted aliases offer fixed, predefined percentages
https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html#configuring-alias-routing:~:text=function%20version.%20For%20example%2C%20you%20can%20reduce%20the%20risk%20of%20deploying%20a%20new%20version%20by%20configuring%20the%20alias%20to%20send%20most%20of%20the%20traffic%20to%20the%20existing%20version%2C%20and%20only%20a%20small%20percentage%20of%20traffic%20to%20the%20new%20version.
I am struggling to see how the correct answer isn't canary. please feel free to enlighten me as I am at a loss how this question description is anything but canary
is this question a case of what naming convention is used within Lambda service. i.e. Canary deployments via Weighted Aliases.
Still very on the fence with this one. My key take aways are that the question says an in house deployment solution and not "codedeploy." By using weighted aliases we are in fact performing a canary deployments. Bitch of a question.
My thought process is this. They can't use Canary Deployment because that is specifically for AWS CodeDeploy: https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-configurations.html They are using an in-house deployment method, so AWS canary deployments aren't applicable. They can, however, use routing configuration on an alias to send a portion of traffic to a second function version. For example, you can reduce the risk of deploying a new version by configuring the alias to send most of the traffic to the existing version, and only a small percentage of traffic to the new version. https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html#configuring-alias-routing
A is the correct answer.