AWS codedeploy deployment types are “in-place deployments” and “blue/green deployments”.

Bobcares provides answers to all queries, big and small, as part of our AWS  support services.

Let’s take a closer look at AWS codedeploy’s various deployment types.

AWS codedeploy and it’s deployment types

AWS codedeploy

CodeDeploy is an application deployment service for Amazon EC2 instances, on-premises instances, serverless Lambda functions, and Amazon ECS services. A deployment in CodeDeploy is the process of installing content on one or more instances, as well as the components involved in the process. Code, web and configuration files, executables, packages, and scripts are all in the content. CodeDeploy distributes content from a source repository based on the configuration rules we specify.

Basically, we can use CodeDeploy to:

• Release new features frequently.
• Update the versions of our AWS Lambda functions.
• During application deployment, avoid any downtime.
• Take on the complexity of updating the applications while avoiding many of the risks that come with manual deployments.

Benefits of AWS CodeDeploy

1. We can use CodeDeploy to deploy both traditional and web applications on servers.
2. We can fully automate our application deployments in development, test, and production environments  with CodeDeploy.
3. CodeDeploy helps us increase the availability of our applications.
4. Moreover, codeDeploy keeps track of application health based on the rules we set up.
5. If there are errors, we can stop and roll back deployments automatically or manually.
6. We can use the CodeDeploy console to launch and monitor our deployments.
7. CodeDeploy works with any application and is platform agnostic. We can reuse our setup code easily.

CodeDeploy deployment types overview

There are two deployment types available in CodeDeploy:

In-place deployment:

The application is stopped on each deployment group instance. Then install the most recent application revision. Finally, start the new application version and validate. We can use a load balancer to deregister each instance during deployment and then restore service once the deployment is complete. Overall, In-place deployments are only available for EC2/On-Premises compute platforms.

Blue/green deployment:

Depending on which compute platform we use, our deployment will behave differently:

Blue/green on an EC2/On-Premises compute platform:

Use these steps to replace the instances in a deployment group (the original environment) with a different set of instances (the replacement environment):

• Firstly, for the replacement environment, provision the instances.
• Then, in the replacement instances, Install the most recent application revision.
• For activities like application testing and system verification, there is an optional wait time.
• Then, route the traffic to instances in the replacement environment with an Elastic Load Balancing load balancer.
• Finally, terminate the de-registered instances in the original environment or kept running for other purposes.

Blue/green on an AWS Lambda or Amazon ECS compute platform:

Traffic is shifted in steps depending on whether the deployment is canary, linear, or all-at-once.

Blue/green deployments through AWS CloudFormation:

As part of an AWS CloudFormation stack update, traffic is redirected from our current resources to our updated resources. Only ECS blue/green deployments are supported at the moment.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, we learned about AWS codedeploy and its deployment types.