Which deployment configuration will meet these requirements with the LEAST deployment time?
Use the AWS CodeDeploy in-place deployment configuration for the Lambda functions. Shift all traffic immediately after deployment.
Use the AWS CodeDeploy linear deployment configuration to shift 10% of the traffic every minute.
Use the AWS CodeDeploy all-at-once deployment configuration to shift all traffic to the updated versions immediately.
Use the AWS CodeDeploy predefined canary deployment configuration to shift 10% of the traffic immediately and shift the remaining traffic after 5 minutes.
Explanations:
The in-place deployment configuration shifts all traffic immediately after deployment, which can expose end users to potential errors without any validation period. This does not minimize exposure or ensure no downtime during the specified maintenance window.
The linear deployment configuration shifts 10% of the traffic every minute. While this allows for gradual deployment and monitoring, it could potentially extend deployment time significantly and does not guarantee zero downtime during the maintenance window if issues arise.
The all-at-once deployment configuration shifts all traffic to the updated version immediately. This approach carries a high risk of downtime and exposure to errors as there is no gradual rollout or validation step, which is against the requirement for minimizing user impact.
The predefined canary deployment configuration shifts 10% of the traffic immediately, allowing for monitoring of the new version’s performance before fully deploying. If issues are detected, the deployment can be halted before affecting all users, thus minimizing exposure and ensuring no downtime during the maintenance window.
I value that the answer is:
Use the AWS CodeDeploy predefined canary deployment configuration to shift 10% of the traffic immediately and shift the remaining traffic after 5 minutes.