Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 60 discussion

A. Create an alias for every new deployed version of the Lambda function. Use the AWS CLI update-alias command with the routing-config parameter to distribute the load is the correct answer as it meets the requirement of supporting a canary release. Option B is not correct because while it would allow for a canary release, it would involve deploying the new version of the application into a separate CloudFormation stack, which would be a more complex and time-consuming process compared to creating an alias for a new version of the Lambda function. Option C is not correct because while it would allow for a canary release, it would involve creating a version for every new deployed Lambda function, which would be more complex and time-consuming process compared to creating an alias for a new version of the Lambda function.

https://www.examtopics.com/discussions/amazon/view/28312-exam-aws-certified-solutions-architect-professional-topic-1/

AWS CodeDeploy supports canary releases for Lambda functions, which is what the requirement is aiming for.

A. Create an alias for every new deployed version of the Lambda function. Use the AWS CLI update-alias command with the routing-config parameter to distribute the load

Not D because, the CodeDeployDefault.OneAtATime deployment configuration is primarily designed for EC2 and on-premises instances. For AWS Lambda functions, AWS CodeDeploy provides deployment strategies specific to Lambda, such as Canary, Linear, and All-at-Once.

Using Lambda Aliases for Canary Releases: * Lambda aliases are pointers to specific versions of a Lambda function. * You can use the update-alias command with the routing-config parameter to configure traffic shifting between the current version and the newly deployed version. * This allows a gradual shift of traffic to the new version while maintaining traffic to the current version. AWS CLI Example: * Create a new alias or update an existing alias to shift a portion of the traffic Testing and Monitoring: Gradually increase the percentage of traffic to the new version. Use Amazon CloudWatch metrics to monitor errors, latency, or other performance issues. Roll back traffic to the previous version if any issues are detected. aws lambda update-alias \ --function-name MyFunction \ --name MyAlias \ --routing-config '{"AdditionalVersionWeights": {"2": 0.10}}'

A. Create an alias for every new deployed version of the Lambda function. Use the AWS CLI update-alias command with the routing-config parameter to distribute the load.

A. Create an alias for every new deployed version of the Lambda function. Use the AWS CLI update-alias command with the routing-config parameter to distribute the load.   Explanation: This option provides a granular level of control for canary deployments: Versioning: Creating a new version for each deployment ensures that you have a clear record of changes. Alias: An alias acts as a stable endpoint, allowing you to gradually shift traffic to the new version. Routing configuration: The routing-config parameter provides fine-grained control over traffic distribution between versions. By using this approach, you can gradually increase the percentage of traffic to the new version, monitor its performance, and roll back if necessary, minimizing the impact of potential issues.

Not B. This introduces R53 in the scenario, but we are not sure if R53 fits in the scenario. To combine R53 and Lambda we should use function URL that is not mentioned and we don't know if the app is public. A lot of uncertainty here Not C. routing-config is an Alias specific configuration aka Weighted Alias and it is not available for the update-function-configuration command https://docs.aws.amazon.com/cli/latest/reference/lambda/update-function-configuration.html Not D. CodeDeployDefault.OneAtATime is a CodeDeploy option for EC2/on-premise, while in this scenario we need a canary option for Lambda such as CodeDeployDefault.LambdaCanary10Percent5Minutes A does the job https://docs.aws.amazon.com/cli/latest/reference/lambda/update-alias.html and https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html#configuring-alias-routing

100% A is correct. :) I was confused between D and A. But, this url says Codedeployee.AllatOnce deploy option is not for 'canary release'. https://docs.aws.amazon.com/ko_kr/codedeploy/latest/userguide/deployment-configurations.html

Here's why Option A is suitable: Create an alias: For every new version of your Lambda function, create an alias. Aliases allow you to associate a user-friendly name with a specific version of the function. Routing configuration: AWS Lambda supports routing configurations that allow you to gradually shift traffic from one alias to another. Using the "routing-config" parameter with the AWS CLI "update-alias" command, you can specify how much traffic each alias should receive. Gradual release: By configuring the routing, you can control the percentage of traffic directed to the new version (canary). You can gradually increase the traffic percentage as you gain confidence in the new release. If issues arise, you can quickly roll back by adjusting the routing configuration.

new release-> lambda alias-> update-alias: aws lambda update-alias --function-name my-function --name alias-name --function-version version-number

D would be an optionn if used Lambda-specific config

keyword = alias for every new deployed version is a classic usage for deployment canary for lambdas other option usually is codeDeploy but in this options AllAtOnce then A

Sorry OneAtTime

CodeDeploy: Although CodeDeploy can help but AllAtOnce is not used for canary traffic shifting.

aws update-alias command has routing-config option to route the weighted % traffic As is correct https://aws.amazon.com/blogs/compute/implementing-canary-deployments-of-aws-lambda-functions-with-alias-traffic-shifting/ # Point alias to new version, weighted at 5% (original version at 95% of traffic) aws lambda update-alias --function-name myfunction --name myalias --routing-config '{"AdditionalVersionWeights" : {"2" : 0.05} }'