CodeDeploy Flashcards
Which are the CodeDeploy lifecycle hooks for EC2?
ApplicationStop
DownloadBundle
BeforeInstall
Install
AfterInstall
ApplicationStart
ValidateService
BeforeBlockTraffic
BlockTraffic
AfterBlockTraffic
BeforeAllowTraffic
AllowTraffic
AfterAllowTraffic
What is CodeDeploy In-place deployment?
The application on each instance in the deployment group is stopped, the latest application revision is installed, and the new version of the application is started and validated.
What are the CodeDeploy Blue/green steps on an EC2/On-Premises compute platform
Instances are provisioned for the replacement environment.
The latest application revision is installed on the replacement instances.
An optional wait time occurs for activities such as application testing and system verification.
Instances in the replacement environment are registered with an Elastic Load Balancing load balancer, causing traffic to be rerouted to them.
Instances in the original environment are deregistered and can be terminated or kept running for other uses.
Define CodeDeploy: Blue/green on an AWS Lambda or Amazon ECS compute platform
Traffic is shifted in increments according to a canary, linear, or all-at-once deployment configuration.
How CodeDeploy: Blue/green deployments through AWS CloudFormation are done?
Traffic is shifted from your current resources to your updated resources as part of an AWS CloudFormation stack update.
How CodeDeploy rollbacks a deployment?
CodeDeploy rolls back deployments by redeploying a previously deployed revision of an application as a new deployment. These rolled-back deployments are technically new deployments, with new deployment IDs, rather than restored versions of a previous deployment.
