Tracking Deployment – Establishing a Deployment Strategy – SAP-C02 Study Guide

Tracking Deployment

Tracking and monitoring your deployment is of particular importance since the last thing you want is to end up with a broken release in production without even knowing about it until your users or customers start complaining. You want to make sure that whatever strategy and solution you put in place to deploy your workloads on AWS works as expected in the actual deployment. If it doesn’t, you want to be told, preferably sooner rather than later, especially when it comes to releases in production environments. The AWS services previously mentioned in this chapter are integrated with core AWS services, such as CloudWatch and CloudTrail, which are great tools to follow up on the status and progress of things over time. However, be aware that all these services may also behave differently from one another when they encounter failure conditions. For instance, don’t expect that Beanstalk or AppRunner will behave exactly like OpsWorks in such circumstances.

Remember that it is ultimately your responsibility to monitor the progress of your deployment process and to see that it remains effective over time. To do this, you must create alarms in CloudWatch to be notified when any of your deployments go wrong for any reason. Thereafter, you want to take the necessary remediation actions either automatically, if that’s an option, or manually as needed. For instance, upon failure, your deployment process may have left your application environment in an unstable state with a mix of your previous and new application releases. How do you roll back to the last known successful deployment? Your options will vary based on the deployment solution you use. For more details, please refer to the documentation and best practices of the relevant AWS services.

Summary

In this chapter, you examined various deployment strategies and AWS services that can help you determine the most appropriate deployment strategy to meet your business requirements.

Chapter 10, Designing for Cost Efficiency, explores the diverse pricing models available through AWS and provides insights into how you can select the most suitable option based on your specific needs and limitations.

Further Reading

  • Overview of deployment options on AWS: https://packt.link/YLKZe
  • Introduction to DevOps on AWS: https://packt.link/ksioB
  • AWS DevOps blog: https://packt.link/eTs4k
  • Architecture best practices for containers on AWS: https://packt.link/g5CnZ
  • CloudFormation best practices: https://packt.link/AdAQk
  • Share reusable infrastructure as code by using AWS CloudFormation modules and StackSets: https://packt.link/l6kqN
  • EKS best practices: https://packt.link/iHnMW
  • What is AWS Proton? https://packt.link/XXNh4