Working with Deployments in AWS CodeDeploy
In AWS CodeDeploy, a deployment is the process, and the components involved in the process, of installing content on one or more instances. This content can consist of code, web and configuration files, executables, packages, scripts, and so on. AWS CodeDeploy deploys content that is stored in a source repository, according to the configuration rules you specify.
AWS CodeDeploy provides two deployment type options, in-place deployments and blue/green deployments.
In-place deployment: Instances in a deployment group are taken offline (with or without the use of a load balancer in Elastic Load Balancing), updated with the latest application revision, and then placed back online as part of the same deployment group. For more information about in-place deployments, see Overview of an In-Place Deployment.
Blue/green deployment: The instances in a deployment group (the original environment) are replaced by a different set of instances (the replacement environment) using these steps:
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.
For information about automatically deploying from Amazon S3, see Automatically Deploy from Amazon S3 Using AWS CodeDeploy.