Also, some additional Amazon EventBridge rules have been added to cater for the test stage. There is now a test stage in the AWS CodePipeline pipeline (green rectangle). The architecture is similar to what was discussed in the previous blog, however there are some new components that have been added. High Level Architectureīelow is the high level architecture for the solution that I will be discussing. If you haven’t read the previous blog (or need a refresher), please read it before continuing. Using the golden AMI pipeline that was discussed in my previous blog, I will walk you through the process of adding a testing stage to it, to ensure that the golden AMIs that are being built, have all the packages that it is meant to have. A possible cause could be that during the build of that golden AMI, the package wasn’t installed due to connectivity issues with the package repository! You do not want to be in a situation where your deployment pipeline fails because a critical package is missing from the golden AMI. You need to have absolute certainty that all the packages that you intended to install have actually been deployed and the configuration changes have actually taken effect.
When you are building a golden AMI, you will be adding more packages to the base AMI and also customising it to suit your requirements. Testing plays a key role when building golden AMIs for the simple reason that if you build an image, you must have confidence that it is ready to be deployed in an environment. This will provide confidence that the deliverables from pipeline align to your requirements. Whenever you use automation pipelines, it is imperative that you incorporate a testing stage.
0 kommentar(er)
