With traditional deployment, new versions of an application are released using various tools to pull the code from a repository and push it to a production server. Once the code has been pushed, each application process is restarted manually. While this process works, it is by no means an easy process to switch from running in the development environment to the production environment.
There are various issues with this traditional deployment process, for example different environments (development work and production server), application configuration management, and replication of an application environment.
Every software deployment involves processes and practices for successful execution & deployment of the deployment. The complications also increase in an exponential manner based on the project size. The organization should build an automated pipeline to develop, test, and release the software in a manner so that the release is done in an incremental manner thereby having minimal or no impact to the project deployment.
With CI/CD pipeline, it helps the organizations automate steps in your software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment. Some of the benefits of CI/CD Pipeline are cost effective, easy to make real time decision, early bug recognition remove manual errors, provide standardized development feedback loops and enable fast product iterations.
In this below diagram, lets have a look at how automated AWS Code pipeline with Code Commit, Code Build and Code Deploy integrated with AWS Landing Zone for “maker” and “approver” process along with creation of workload application account using Account Vending Machine from child member account.
Code Commit is to securely store the source codes to make easier for the teams to collaborate on code in a secure and highly scalable ecosystem. CodeBuild compiles your source code, runs unit tests, and produces artifacts that are ready to deploy. CodeBuild eliminates the need to provision, manage, and scale your own build servers. S3 bucket for artifacts is also setup with the first AWS CodeCommit repository and shared across all other AWS CodeCommit and AWS CodePipeline resources. For the AWS CodeCommit, CodePipeline, and CodeBuild it’s a best practice to use CloudFormation templates that allow organizations to automate the creation of accounts and resources.
With strong expertise in Automation, Cloud Comrade has proven examples offering their clients an Automated Account Creation with AWS Service Catalog and Cloud Development Toolkit to enhance the organization’s current Landing Zone.
