You can deploy multiple environments when you need to run multiple versions of an application. For example, you might have development, integration, and production environments
Use the following AWS CloudFormation templates to set up the elastic beanstalk application and codepipeline to do auto store the artifacts.
aws cloudformation create-stack --template-body file://envcreate.yaml --parameters file://parameters.json --capabilities CAPABILITY_IAM --stack-name gitflow-eb-master
Your stack might take several minutes to create—but you probably don’t want to just sit around waiting. If you’re like us, you’ll want to know how the stack creation is going. Your new stack,
gitflow-eb-master, appears in the list at the top portion of the Cloudformation console. Its status should be
CREATE_IN_PROGRESS. You can see detailed status for a stack by viewing its events. The
CREATE_COMPLETE event is logged when the resource is successfully created.
Once the cloudformation successfully created the stack go to AWS Elastic Beanstalk Environment Management Console. Once the environment health turns green, click on the URL next to the environment name to view view the sample nodejs application you deployed.
AWS CodePipeline is a continuous delivery service you can use to model, visualize, and automate the steps required to release your software. You can quickly model and configure the different stages of a software release process. CodePipeline automates the steps required to release your software changes continuously.
Above cloudformation template will also create and configure a simple AWS CodePipeline with three actions: source, build and deploy.
After your pipeline is created, the pipeline status page appears and the pipeline automatically starts to run. You can view progress as well as success and failure messages as the pipeline performs each action.
To verify your pipeline ran successfully, monitor the progress of the pipeline as it moves through each stage by going to CodePipeline Console. The status of each stage will change from No executions yet to In Progress, and then to either Succeeded or Failed. The pipeline should complete the first run within a few minutes.