SHA256
added deployments
This commit is contained in:
1 parent
8c5a8eaa95
commit
d42b5065c2
2 files changed
+40
No files matched your search
@@ -25,3 +25,19 @@ Contains the deployment actions that CodeDeploy should execute during deployment
|
||||
|
||||
### Revision
|
||||
This is everything required to deploy a new version: AppSpec file, application files, configuration files, executables.
|
||||
|
||||
## Deployments
|
||||
### In-Place
|
||||
- The app on each instance in the deployment group is **stopped**.
|
||||
- The latest app revision is installed, and the new version of the application is started and validated.
|
||||
- You can use a **load balancer** so that each instance is unregistered during its deployment and then restored to service after the deployment is complete.
|
||||
- ==Only deployments that use the EC2/On-Premises compute platform can use in-place deployments.==
|
||||
|
||||
### Blue/Green
|
||||
- Instances are provisioned for the replacement environment.
|
||||
- The latest application version 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 ELB, causing traffic to be rerouted to them.
|
||||
- Instances in the original environment are unregistered and can be terminated or kept running for other uses.
|
||||
|
||||
|
||||
Reference in new issue
Block a user