Setting Up a Deployment Pipeline

So far, you’ve always executed the build and deployed commands from a single computer, with the same AWS account used for development. If you work alone or in a very small team, that deployment flow is probably good enough. For an even slightly larger group, though, you’ll probably want to set up a deployment pipeline.

Deployment pipelines

The purpose of a pipeline is to reduce errors by making software releases reproducible and reliable. A deployment pipeline does that by orchestrating the work required to convert source code into a fully deployed application, automating repetitive and error-prone tasks. The deployment tasks usually involve downloading a clean version of the source code, running automated tests, producing application binaries or package artefacts, and installing the application in approval or release environments. Some of those steps might also involve manual approval, requiring humans to verify release candidates or perform additional manual tests.