For a high-risk utility billing Lambda, the team wants only ten percent of API traffic on the new version for fifteen minutes before a full shift. Which deployment strategy should they configure?
Select an answer to reveal the explanation.
Short Explanation
Canary is a taste-test: ten percent of citizens hit the new Lambda for a bit while you watch the meters. If the taste is bad, you never serve the whole city. All-at-once is the opposite of that sip.
Full Explanation
Canary deployments gradually shift a defined percentage of traffic to a new Lambda version (often via aliases and weighted routing or CodeDeploy canary configs) before completing promotion, limiting blast radius. Immediate full shifts and unrelated EC2 rolling refreshes do not implement that partial-traffic validation window.